Timeline for How to help a dev, who is otherwise good, improve the speed at which they work?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23, 2022 at 18:21 | comment | added | JeffThompson | I wonder if the issue is the dev isn't recalling the solution from a previous similar issue, or if they aren't connecting that they're similar? Perhaps the same solution, but a conversation with them might lead to more productive help | |
| Oct 21, 2022 at 13:35 | comment | added | JMac | @cjs For me, the process of writing notes is typically far more key to my learning and remembering than actually having the notes is. I know I've talked to others who are similar. | |
| Oct 21, 2022 at 7:59 | comment | added | cjs | Writing things down has been working so well for me that the technical notes repo I've been keeping since 2017 is now at 250k words. But these notes can go anywhere; for notes on how a program works, I'd keep them header comments in the code or Markdown files right beside the code. Reviewing these together can make sure that individuals and the team understand what they're doing and share that understanding. Remind everyone that the result often isn't always used later, but the process of writing and editing such documentation is usually what produces the most benefit. | |
| Oct 21, 2022 at 6:40 | comment | added | stanri | Writing stuff down is what kept me productive when I was pregnant and post-partum and had really bad "brain fog". My mind felt like a sieve. I like this answer because it doesn't assume the reason for the brain for, rather just a general solution. | |
| Oct 20, 2022 at 20:08 | comment | added | Jeremy Fisher | That's a good point, learning how to learn - and even how to problem solve - is a super valuable skill | |
| Oct 20, 2022 at 20:05 | comment | added | jwh20 | I think this is a side-effect of the way students are taught in universities these days. My college years were spent learning how to learn things. I didn't realize it at the time but it's very clear now especially after working with others who were simply taught things. They know what they know and really struggle with learning new things. In any technology field this is a big problem. So the onus is now on employers to see to it that juniors learn how to learn or they will end up with a relatively useless employee. | |
| Oct 20, 2022 at 16:05 | comment | added | Jeremy Fisher | I like this, it would be awesome if more senior engineers jumped in on guidance and observed how junior devs problem solved and helped to correct things early on constructively. Unfortunately, it seems like that kind of culture is very company/team dependent. | |
| Oct 20, 2022 at 12:25 | history | answered | jwh20 | CC BY-SA 4.0 |