3 ms·
I currently work with a bunch of people who are "business majors" or whatever and are similarly self-taught in the Tech/IT/Programming space. It's interesting
by grecy 12y ago
I currently work with a bunch of people who are "business majors" or whatever and are similarly self-taught in the Tech/IT/Programming space.
It's interesting to watch how they work and the kinds of outputs they produce. Quite a lot of the stuff works... mostly...
It's entirely untestable, not repeatable, undocumented and just stuck together with flaky glue code.
Sure, if you aiming to "make it work" you can do that. If you're aiming to do well... I suggest learning proper technique.
- bdcravens 12y agoI think it's a mindset thing; either you have the mind of a developer or you don't, degree or not. I'm self-taught, and early on I had a inferiority complex when it came to those with CS degrees. Didn't take long for that to wear off as reality exposed gaps in their ability/knowledge.
- grecy 12y agoFair enough. I have a Software Engineering degree (certified Engineer), so I already have a superiority complex anyway ;)
- okepi 12y agoAbsolutely. I think it's important to learn how to write proper code. I think my biggest hurdles were thinking that I wasn't good enough to even try, and being unable to acknowledge that my school had given me a solid background in CS.
- 7Figures2Commas 12y ago> It's entirely untestable, not repeatable, undocumented and just stuck together with flaky glue code. Code that's testable, repeatable, well-documented and elegant doesn't guarantee that an application will actually meet anyone's needs in a commercially sufficient manner. The WordPress code base is frequently criticized, and the Facebook index.php code from 2007[1] will probably make some people cringe, but these are just two of many examples demonstrating that if you want to "do well", building applications that work and meet the needs of their users is initially a lot more important than "proper technique." [1] https://gist.github.com/nikcub/3833406 https://gist.github.com/nikcub/3833406
- Wilya 12y agoIf the Facebook code had stayed untestable and undocumented, it would never have worked at their current scale. Testing and documentation make a difference in the long term. Unless your business model is "build a shiny tower and sell it before it crumbles", at some point, you'll have to fix the mess you made in the early days of the application.
- emsy 12y agoI once worked on a project that was started by two construction engineers. It was a Java web app. It worked well enough, but many customers complained about the ammount of crashes and errors the app produced. But it had nothing to do with them being construction engineers. It was their mindset that they thought they now knew enough and don't need to become better anymore. When the complexity grew, the app was above their competency. Even when faced with their failures their were unwilling to admit that they need to learn more about professional software engineering. I have talked with some developers about my observations and almost all of them had a similar anecdote to tell. Some of them included CS grads with a similar "good enough" mindset. These anectodes are in no way a representable study, but for me, it put the radical professionalism movement of Uncle Bob in a whole new context.
- enraged_camel 12y agoThis is a false dichotomy. I'm a self-taught programmer and the software I develop has full test coverage as well as thorough documentation. Proper technique and best practices are definitely important. They can, however, be a part of the self-learning process, just like learning how to write the program itself.