6 ms·
> Amazingly quickly he would suss out the problem and get things running -- making the customer happy and rescuing the SLA Probably skills they learned reading
by flukus 10y ago
> Amazingly quickly he would suss out the problem and get things running -- making the customer happy and rescuing the SLA
Probably skills they learned reading their own code. I've noticed it with other people, the ones he can quickly debug spaghetti are the ones that will create more of it. It's why they stick around, management likes them because the can solve problems, they just don't see the creation of yet more problems.
- joeguilmette 10y agoIt's a balance you need to run. But as a PM, spaghetti fixers are indeed very nice to have around. Keeping an eye on technical debt is important though.
- flukus 10y agoThe hardest part isn't the technical debt, it's detecting when spaghetti fixers are actually adding features to the product.
- joeguilmette 10y agoThis is another great point. Our support team is directly linked to a spaghetti fixer, this is great bc bugs are squished instantly. But sometimes a new checkbox appears and that is a real problem.
- firebones 10y agoOn the surface, I think you're describing fire-fighters (who are loved for solving high-visibility problems), but in retrospect, I think these are also developers with very high reading comprehension and reasoning abilities. That may not make them great designers and architects (though some are), but they can see code for what it is and fix it, as in "The Big Lebowski", "in the parlance of our times" (in other words, in a way that fits the code as it was originally written).
- Aeolun 10y agoI mean, if you understand spaghetti code just as easily as any other code, why wouldn't you write it? It would make no difference to them.
- MAGZine 10y agoWhat is this reasoning? If you know the right way and wrong way to build a bridge, you'd build it wrong, because it makes no difference?
- di4na 10y agoThe other way around. If you can get out with doing it the wrong way, why even care about there being a good way ?
- falsedan 10y agoMore like, if you know English and Latin, why not blog in Latin, since it makes no difference to your ability to enjoy your posts.
- user5994461 10y agoSo, the question that makes the difference should whether he writes blog for himself or for his readers? [replace "blog" by "code"]
- falsedan 10y agoAnyone can read their blog! Since anyone can learn Latin, if they feel like it. (Yes, I know I'm representing a terrible argument.)
- flukus 10y agoIt's a lack of reasoning, if it's not causing any issue's why change? The rest of us write good code because we're to dumb to read bad code.
- jerguismi 10y ago> management likes them because the can solve problems, they just don't see the creation of yet more problems. In fire-fighting situations at least to my experience it is usually about fixing things fast and under stress. Not many devs are interested in doing that. These hotfixers probably know their code sucks, but I don't think they need to feel bad for solving the urgent problems in their own way - in my experience it is not a job that many are that willing to take. Majority like to solve the problems properly in a slow-paced less stressful way.
- stevedonovan 10y agoIt was my job for a while to work with scientists and their spaghetti Fortran codebases. One esteemed fellow still stuck to the FORTRAN IV of his youth (the original pasta language). It was amazing how much they could do with such old technology. The overriding impression ultimately was: "Never keep intellectual property just in code"
- walrus1066 10y agoI feel your pain. Scientists & data scientists are notorious for spaghetti code. Refactoring scientists code was how I got into software engineering. I used to be a scientist, and I found restructuring/modularizing the analysis code more fulfilling than the actual analysis.
- MereInterest 10y agoAs someone who is currently in that exact situation, and is considering switching away from science, how did the actual switch from science to software go?
- dfgasfjhjhsdojj 10y agoReally well. Dev work is way more fun than science! If you want some advice then: - Take some time to learn some CS fundamentals. - Make sure you know a language that someone that might employ you knows (just so they have a point of reference). - Write some toy applications in the field you want to move to.
- MereInterest 10y agoThank you, and it is very good that the path I'm looking towards is possible. I've been brushing up on algorithms, mostly as I run into them in things that I have been writing on nights and weekends. Primarily C++ and Python, with a smattering of C, bash, javascript, and php. I have probably about 6-9 months before graduation, so I've been starting to look at fields in more detail, rather than the nebulous concept of "industry" that you typically hear about in academia.
- toast0 10y agoI might be one of these people. I've worked with enough underdocumented code/systems, I don't expect, look for, or provide documentation.(Exception: I provide documentation where there's a clear and stable boundary/interface another team will use)
- majewsky 10y agoI had this with the OpenStack API. It's so hilariously underdocumented that I've reverse-engineered it by poking at a Devstack and checking the HTTP requests in mitmproxy. After some time, even when I had to work with a new part of the API, I didn't even bother to check for documentation because just poking around was faster (and more reliable: one never knows how close the documentation is to the real deal).