Earlier quoted context omitted.
I write better non-trivial code when I get up and get away from the screen for a while. Go do something else to get my mind off it. Even sleep on it. Then the insights creep in. Hammering away at a hard problem usually makes a big mess. Sometimes three quarters of my time is spent understanding the requirements, negotiating the solution, researching, talking through the design.
Same here! Sometimes I’ve spent weeks thinking through a problem fully, talking to everyone involved (including myself) only to code whatever it was in a couple hours. It’s amazing what our brains can process subconsciously.
Ask HN: Why aren't you coding?
151–160 of 316 posts
Re: Ask HN: Why aren't you coding?
#152> The revised bill arrived: $1.00 for turning the screw; $9,999.00 for knowing which screw to turn.
is preferable to
> $10,000 for building a new printing press system from scratch.
Re: Ask HN: Why aren't you coding?
#153The unfortunate reality is that developing roadmaps/managing stakeholders/building team collaboration takes a large amount of time.
Arguably 90% of this effort could be eliminated if the number of stakeholders was reduced, or the company exercised more trust that their engineers were working on the right things. There is a tremendous amount of waste introduced by the endless tracking of engineering deliverables.
Re: Ask HN: Why aren't you coding?
#154Re: Ask HN: Why aren't you coding?
#155Earlier quoted context omitted.
I’ve worked with 0.1x engineers, where the whole team is slowed down. It becomes very draining. This is why I’ve retired and am just doing my own projects
If you work with 0.1x engineers, and you are 1x, does that make you a 10x within the organization?
Re: Ask HN: Why aren't you coding?
#156Mainly because I’m helping other people be able to code. One of the interesting things about the 10x engineer meme is that they’re 10x because they improve the productivity of their team. Well extend that to DevRel and that’s maybe another order of magnitude or two of effect again. Extend that to the average person looking to build and it’s another order or perhaps two again. Hopefully the stuff I’m doing now will ge…
I’ve worked with 0.1x engineers, where the whole team is slowed down. It becomes very draining. This is why I’ve retired and am just doing my own projects
Literally every project they were involved in would get slower as people needed to stop everything to deal with them.
This isn't Mythical Man Month stuff either - no matter the size of the new project, adding specific engineers to the project made progress not just halt, but actually go backwards, as all the stuff that worked before was now broken.
EDIT: And yes, bad management was a major issue with the team but some engineers seem to be negative sum, even taking management into account.
Re: Ask HN: Why aren't you coding?
#157Re: Ask HN: Why aren't you coding?
#158Earlier quoted context omitted.
And arguably it's best when it's done as little as possible.
I write better non-trivial code when I get up and get away from the screen for a while. Go do something else to get my mind off it. Even sleep on it. Then the insights creep in. Hammering away at a hard problem usually makes a big mess. Sometimes three quarters of my time is spent understanding the requirements, negotiating the solution, researching, talking through the design.
How can this be? Did you never learn how to use source control? Coding is the best way to explore the solution space, doesn't mean you use whatever you write right now.
Re: Ask HN: Why aren't you coding?
#159Earlier quoted context omitted.
I write better non-trivial code when I get up and get away from the screen for a while. Go do something else to get my mind off it. Even sleep on it. Then the insights creep in. Hammering away at a hard problem usually makes a big mess. Sometimes three quarters of my time is spent understanding the requirements, negotiating the solution, researching, talking through the design.
Same here! Sometimes I’ve spent weeks thinking through a problem fully, talking to everyone involved (including myself) only to code whatever it was in a couple hours. It’s amazing what our brains can process subconsciously.
Re: Ask HN: Why aren't you coding?
#160Earlier quoted context omitted.
I’ve worked with 0.1x engineers, where the whole team is slowed down. It becomes very draining. This is why I’ve retired and am just doing my own projects
If you work with 0.1x engineers, and you are 1x, does that make you a 10x within the organization?