4 ms·
Younger does not necessarily mean faster. I’ve done process improvement in the past and it boils down to three things people, tools and process. Take a look
by pettycashstash2 5y ago
Younger does not necessarily mean faster. I’ve done process improvement in the past and it boils down to three things people, tools and process. Take a look at YouR tollchain (ex do you have any code suggestion ai in there?) and the delivery process end to end. If you’ve exhausted those two take at look at how you approach problems. Make an list of changes and start with the simple improvements. Rule of thumb is you will gain. 80% speed improvement with 20% extra or 0 effort depending on what process area was changed ( people , process, tool)
- touristworker 5y agoYes, I am looking for ALL possible ways to simplify my work. I use WebStorm which is really good about auto-suggesting, refactoring and renaming variables or functions. I really love it. As what relates to the 80/20 rule, I will have to review it again, even though I hoped I did all the possible optimisations, may be there are more.
- UglyToad 5y agoYou mention webstorm and while I'm not familiar with it are you by any chance working on JS or other dynamic codebases? I've tried a few dynamic languages and I Just. Can't. Do. It. Everything seems so painful and slow. The way my brain works is I scope out the types and then use intellisense to fill in the gaps. I can absolutely fly through code when I'm not keeping a bunch of useless context in my head but put me in a language without a strong IDE and type system and I'd produce little.