8 ms·
It's usually the lack of breadth that hurts you. IT is a fast-moving field. Solving business problems takes understanding which good ways to do that are curre
by nine_k 7y ago
It's usually the lack of breadth that hurts you.
IT is a fast-moving field. Solving business problems takes understanding which good ways to do that are currently available, what limitations and dangers each approach brings, how would it interact with other things, etc.
You still need deep knowledge, but the most efficient knowledge is that of key principles, general approaches and ideas. A specific technology does not matter much, and can be mastered quickly enough, if you already are acquainted with the principles behind it. E.g. learn about FRP, and you will see how React, Elm, and Excel all work along the same lines.
What you end up with after some time is like a normal distribution: deeper knowledge around some area and various levels of acquaintance with a wide range of other things.
There are still areas where you can polish the mastery of one narrow thing to utter perfection: making pizza or coffee, sports like running or weightlifting, etc. You can keep practicing them to counterweight the feeling from the view of the sheer and constantly moving IT landscape.
- Rerarom 7y agoWhat would be a good example of a slow-moving field?
- amelius 7y agoPhysics.
- kps 7y agoManagement. Kay's list includes The Mythical Man Month, which, except for the technical details, could have been written yesterday.
- pjmlp 7y agoI feel that if there is a millennia old book or tablet from early days of mankind regarding management, many advices would still apply.
- ghaff 7y agoIt is very waterfall-y as someone I know said in a talk and therefore you probably need to be a little careful what "rules" you take away from it. That said, the "mythical man month" discussion itself as well as the idea of a 9x difference in effort between a program and a programming system product are worth the price of admission. The latter arguably runs somewhat counter to a lot of MVP, etc. approaches but recognizing the difference is still useful.
- rhizome 7y agoI've heard an observation that Agile as practiced in the real world is often basically "tiny waterfalls."
- ghaff 7y agoThere's probably some truth to that. That's what a sprint basically is, right?
- kthejoker2 7y agoIf you run your sprints right then no, nothing's set in stone. If something comes up in the middle of the sprint that takes priority, you address it. You don't mindlessly stick to the schedule set (that would be a "tiny waterfall.")
- ghaff 7y agoFair enough. Although waterfalls usually weren't really set in stone either in my experience. Which had both good and bad points. (It's good to be adaptable but changing requirements all the time is also a good way to make a project late.)
- rhizome 7y agoThis sounds is/ought-y? What is the prevalence of running sprints right in the real world? "As practiced" was the important part of my question/observation.
- 7y ago
- Roritharr 7y ago> There are still areas where you can polish the mastery of one narrow thing to utter perfection: making pizza or coffee, sports like running or weightlifting, etc. You can keep practicing them to counterweight the feeling from the view of the sheer and constantly moving IT landscape. Hear Hear! When talking to Junior Devs i always point out that they should take into account the Lindy Effect and invest some of their learning time into things that were here for atleast a century so they can get enjoyment out of their accomplishment for the rest of their lives. You don't want to die without making at least ONE perfect pizza.