I'm a web sysop and support engineer. My skills are mainly in back-end: Java, Linux, Python, PostgreSQL, Git, and GitLab. Currently I'm learning front-end skills: JavaScript, and Ruby.
Haha Iâm also guilty of that. My solution is making a bunch of small changes and commit all of those as âminor improvementsâ. This solution is probably worse than the problem itself, though.
Computer & social scientist merging both worlds to build interactive software. Working as web dev focusing on front end engineering, interaction design, information architecture & data visualization.
The fact my personal site has taken 6 complete reworks, almost 4 years and still has never actually had more than a coming soon message.
Its just never perfect...
For my actual work, I play the game of bouncing it off testers when I feel its about there. This goes on till they accept it. It stops me over thinking and over working on things.
About a year ago I started my first version of my website. I used Wordpress so it was up and running in no time, and most of the content was ready. Then a few weeks ago, with new knowledge and tools, I started to remake it from scratch. I had to âstart overâ from zero 3 times, but now itâs a lot better than it was before and itâs pretty much ready. Not that I wonât keep working on it indefinitely, though.
I like to think, âis this code I have right here better that whatâs online? Yesâship it.â And in my opinion, almost anything is better than a coming soon page! đ
Good luck on your projects! In case you want to take a look, my site is at cecilelebleu.com. Although itâs not perfect, itâs better than it was yesterday!
It's hard to have self awareness of this, but if you found yourself trying to cover every scenario around the task in hand and make sure you've covered it, it's a sign that you might have fallen in that trap.
I always tell people:
Start small, then iterate and don't overthink your solution
Depth-first versus Breadth-first development.
With depth first you would make things feature complete before moving on the next part, instead of first getting to a minimal product. Depth first has little YAGNI and a lot of bike shedding.
Oldest comments (28)
It starts to take (time & effort) way more than expected.
I'm not sure that works in all scenarios. I find frequently with legacy code even hacky changes can take a lot longer than expected.
If it's not worth the extra time and effort, then it lies within the perfection boundaries.
Ah there we go. It takes more time/effort than expected AND it is not worth it :)
When people spend longer telling you why something won't work, than making it actually just work would have taken!
The GitLense heat map shows more edits in comments than in code?
But more seriously, if you have a lot of small commits, could indicate obsessive compulsive edits. I'm guilty of that
Haha Iâm also guilty of that. My solution is making a bunch of small changes and commit all of those as âminor improvementsâ. This solution is probably worse than the problem itself, though.
Not shipping anything. đ
Yeah ;-)
Simple but true! đ #guiltyAsCharged
I'm in this comment and I don't like it
big oof
The fact my personal site has taken 6 complete reworks, almost 4 years and still has never actually had more than a coming soon message.
Its just never perfect...
For my actual work, I play the game of bouncing it off testers when I feel its about there. This goes on till they accept it. It stops me over thinking and over working on things.
About a year ago I started my first version of my website. I used Wordpress so it was up and running in no time, and most of the content was ready. Then a few weeks ago, with new knowledge and tools, I started to remake it from scratch. I had to âstart overâ from zero 3 times, but now itâs a lot better than it was before and itâs pretty much ready. Not that I wonât keep working on it indefinitely, though.
I like to think, âis this code I have right here better that whatâs online? Yesâship it.â And in my opinion, almost anything is better than a coming soon page! đ
Good luck on your projects! In case you want to take a look, my site is at cecilelebleu.com. Although itâs not perfect, itâs better than it was yesterday!
It's not bad actually, I like it
I think too many premature performance optimizations, which might not even be optizimations, due to maybe not even Profiling...
It's hard to have self awareness of this, but if you found yourself trying to cover every scenario around the task in hand and make sure you've covered it, it's a sign that you might have fallen in that trap.
I always tell people:
Still plan, but not so far you go out of scope.
Depth-first versus Breadth-first development.
With depth first you would make things feature complete before moving on the next part, instead of first getting to a minimal product. Depth first has little YAGNI and a lot of bike shedding.
Be careful to not let the opposite mentality take over,
With this mentality you will create a codebase that is not flexible, difficult to maintain, and doesn't stand the test of time.
Someone constantly fixed on a scarcity mindset. Always looking for what's missing.