25 ms·
I'll add one that even after 200 comments I don't see: Failure to explain the reason why. Coming down to their developer with a list of tasks without explaining
by jerf 9y ago
I'll add one that even after 200 comments I don't see: Failure to explain the reason why. Coming down to their developer with a list of tasks without explaining why those tasks are the most important and will lead to company success.
You might think startups are small enough that this couldn't happen but that was actually where my worst experience was. The founders are visibly in a meeting with a couple people, maybe "suits", maybe not. They come out of the meeting and the next day your priorities are rewritten. Cool beans, that's a thing that can happen and that's not my issue. My issue is, why? What are the goals we are trying to hit now? What's the plan? Why is that better than the old plan?
This is especially important IMHO for more senior engineers responsible for architecture and stuff, because those matters can greatly affect the architecture. Telling me why lets me start getting a grasp on what parts of the code are long term and what can be considered a short term hack, what the scaling levels I need to shoot for, and all sorts of other things that are very hard to determine if you just come to me with "And actually, our customers need a new widget to frozzle the frobazz now more than they need to dopple the dipple now."
Not necessarily the biggest issue, there's a lot of other suggestions here that are probably bigger in most places, but this is one that has frustrated me.
(I'll also say this is one you may be able to help fix yourself, simply by asking. If you are in that senior role I think you pretty much have a professional obligation to ask, and I would not be shy about working that into the conversation one way or another.)
- Boothroid 9y agoAgreed. Sometimes though I suspect this falls into the deliberate siloing of information category - though God knows how anyone thinks that keeping people uninformed is a good way to write software.
- noxToken 9y ago> This is especially important IMHO for more senior engineers responsible for architecture and stuff, because those matters can greatly affect the architecture. Telling me why lets me start getting a grasp on what parts of the code are long term and what can be considered a short term hack, what the scaling levels I need to shoot for... This right here has been the biggest problem in my experience. We'll have unforeseen issues arise in production, and the business side will come up with methods to fix the issue. Without context, all of these fixes to our products have been fine, but they never take the future into consideration. It makes me paranoid. I used to adhere pretty well to the adage "Write code for what you have now and not some mystical thing that may arise in the future" while still maintaining enough abstractness to extend things. New requirements would come in, we would implement them, and everyone is happy. 3 months later, a new set of requirements that destroys how we wrote something else. If we knew a road map before we started designing and implementing, we could have saved everyone time and money by designing for X + Y instead of X alone. I get that you can't know everything that is going to happen. I get that there will be times where you must refactor the code. That's fine. However, tell me where the product is going. It may seem like a trivial change to you as a business person, and the only way we devs can keep the change trivial is by proper design.
- jerf 9y agoI think of YAGNI as a very important principle, and encourage young developers to practice it rigorously, but as you grow in your arts you should eventually be able to reliably predict some elements of the future, and as you approach the middle of your career you should be able to start successfully heading such things off at the pass. I think it is important while young to be very aggressive with the YAGNI because otherwise you will have a much harder time developing that prediction skill, as the data set will be much noisier.
- noxToken 9y agoThis is something that I struggled with at first. I kept gravitating towards abstract solutions, and returning to that code was always annoying. Too many layers for so little payoff.
- thehardsphere 9y ago>You might think startups are small enough that this couldn't happen but that was actually where my worst experience was. Start ups are merely new businesses. New businesses can be poorly run just like any other business can. If anything, start ups are probably more likely to be poorly run merely because the genuinely awful ones haven't gone out of business yet.
- hobofan 9y agoIf people (even if they have a special position in the company) can just come to your developers with a list of tasks, without going through a process, that is a much bigger problem.
- nashashmi 9y agoYou remind me of Simon Sinek: How leaders inspire action TED Talk.
- tomjen3 9y agolink: https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action/up-next https://www.ted.com/talks/simon_sinek_how_great_leaders_insp...
- justin_oaks 9y agoBoth managers and co-workers come to me asking me to perform a task. If I don't know why they're asking, then I immediately ask: What is the problem you're trying to solve? This is just a different way of asking "Why?" More often than not, this changes the entire conversation. Often this leads to us determining that the task is unnecessary. Sometimes it's that a different approach would be better. Sometimes I do the task with a small modification. Rarely, I perform the task exactly as described.