3 ms·
I forget where I heard this the first time but it shows up now and then and it's held true for me since the first time I heard it. If you have a big work/produ
by pc86 6y ago
I forget where I heard this the first time but it shows up now and then and it's held true for me since the first time I heard it.
If you have a big work/production project, go with what you know, whatever that is. When there's a deadline or someone will lose money with a delay, it's irresponsible to use that project to add another line to your resume or play around with $NEW_TECH.
If you want to learn a new technology, do it on a project where you can afford to throw your hands up at some point and scrap the whole thing, because you very well may end up in that position.
- sukilot 6y agoYou probably heard that at every successful operation you spoke with. Research and Development are two different activities. Both are lovely. Know which one you are getting paid to do.
- AnimalMuppet 6y ago> If you want to learn a new technology, do it on a project where you can afford to throw your hands up at some point and scrap the whole thing, because you very well may end up in that position. Think of it as having two goals for the project: learning $NEW_TECH, and writing a program to do $TASK. Don't use $NEW_TECH unless the goal of learning $NEW_TECH is at least as important (or valuable) as the goal of writing a program to do $TASK. This implies that you want to experiment with smaller programs. But when you do, recognize that you may not be seeing all the problems and limitations of $NEW_TECH.
- pc86 6y agoExactly this. I want to play around with kubernetes but I know a big part of it's benefit is for big projects. I also just haven't gotten around to it yet.