56 ms·
Organizational Skills Beat Algorithmic Wizardry (2015)
- wolco 9y agoThe most important skill I've learned is how to collect money. Everything falls apart at the end if you can't collect.
- EGreg 9y agoCan you share the takeaways and strategies you have amassed?
- da02 9y agoDo you mean setting up a payment system for customers? Or getting the adequate funding for a project?
- icebraining 9y agoI think wolco is talking about payments that are charged after the service is (at least partially) performed, which is common in the B2B world.
- lstamour 9y agoPreviously: https://news.ycombinator.com/item?id=9757892 https://news.ycombinator.com/item?id=9757892
- jmartrican 9y agoThis reminds me of the PHD in the office, who was hired because of some mathematical related skill they specialize in, is never getting their hands dirty. They are off somewhere looking smart and protecting their allure, while us grunts are keeping the lights on. Broad stereotype here, but it is what I have experienced. To be very honest, being on Google searching constantly has been the most important skill. In this face paced IT environment, if you stay too long becoming an expert on something, it's replacement is coming right around the corner.... even within the same framework. As I was finally getting a hang off Spring 4 and Spring Boot 1.x, then comes Spring 5 and Spring Boot 2 with their new WebFlux architecture.
- sidlls 9y agoMaybe they're doing some analysis ("data science", statistics, etc.) that is important and you just aren't aware of it.
- ggm 9y agoA lot of the awesome I see people smarter than me doing, is not getting bogged down in nitty gritty but instead thinking about how to DTRT. Then, when they do it, the apparent effort is low: you've discounted the french metric tonne of thinking time that led up to it. Equally, they should get their hands a little dirty. Best is to be a great chef but spend some time with the bottle washers relating to being a dishpig. Nobody really likes Gordon Ramsay as much as the chefs who invest in staff development.
- racer-v 9y agoI think the massive amount of churn in the web world is the exception rather than the rule. If you learned C programming 40 years ago it would still be relevant today. Even Android is almost 10 years old now.
- prewett 9y agoIf you learned Ada, Modula-2, Pascal, or BASIC, though, it might not be so relevant. COBOL, FORTRAN, Smalltalk, and Perl 5 are somewhat useful, akin to, maybe, jQuery in the web world.
- lopmotr 9y agoI work on math-heavy engineering software where it can take a month to learn how some clever algorithm works and I'd say organizing the code is still equally as important as that. I've thrown away big clever algorithms when I found libraries that did it for me and did it better than I could.
- nafey 9y agoBut most people are not doing that in their careers. It's mostly CRUD applications that they are building
- oblio 9y agoI think he's agreeing with you on the overarching theme. If I'm reading his comment correctly, he's saying that despite him writing math heavy stuff, organizational skills are super important and as important as raw algorithmic skills.
- collyw 9y agoI am working on CRUD just now. Its amazing how complex some people manage to make simple things. Keeps me in a somewhat unsatisfying job though.
- paulie_a 9y agoI have seen some incredibly over engineering and it is a wonderful feeling to delete it all and use a simple sane library. On Fridays I typically spend the afternoon deleting as much code as I can
- Raidion 9y agoI mean, CRUD doesn't have to be simple. It can get complexity from the underlying data, or dealing with 100 million users at once, or it having to return results FAST. Just because you don't have to write some novel algorithm doesn't mean you're not solving hard problems.
- 9y ago
- b1daly 9y agoThis is a nicely succinct expression of what I intuit to be almost a universal rule of creating/designing/making. It’s related to what I think of as “coherency” and I’m often surprised at how long it can take. The most recent example is that I was writing up some technical feedback for a reviewer of a product I develop. My first draft was several pages worth of dense prose. I realized I needed to simplify, otherwise it would overwhelm the reader. I worked on it for several hours, and in the end I had it down to about 4-5 paragraphs. So it took me five hours to write what looks like a simple, straightforward email! I’m a music producer by trade, and the principal is very much at work. To create a successful recording requires getting into the small details of the sounds, and working with them, whether your tools are complex or simple.
- SomewhatLikely 9y ago"I would have written a shorter letter, but I did not have the time." - Blaise Pascal
- magwa101 9y agoTimely! I'm on "hiatus" and producing music again after a 10 year break. It's been months of learning. With the new tools I can go so much deeper, so I am. If you want repeatable processes you have to focus on tools and organization. I've integrated github, google docs, Reaper, and bunches of VSTs and I'm just barely starting to see a good organizational approach. This is 1 year later!
- slfnflctd 9y agoI would love to see a more in-depth description of this process you've gone through, in a blog or reddit post or discussion thread somewhere. Like many others, I've been playing with digital recording tools off & on since the 90s as a total amateur (wanted to be in a 'cool band' since middle school, still do), and while I know there are a thousand great guides out there, I always seem to find them overwhelming/paralyzing. Admittedly, I probably don't travel in the right circles for it, but the github and google docs aspects in particular sound like something I haven't read as much about musically inclined people doing before.
- oggyhead 9y agoI don't understand this! Math is a super set of algorithmic wizardry and if you include heuristics in algorithmic wizardry (why would you not?),isn't organizational skills a part of the Algorithmic Wizardry? So he's saying that knowing all skills in the subset is better than knowing all the skills in the set? And that's just the headline
- oggyhead 9y agoOrganization is a mathematical and algorithmic problem regardless of the context. And if you think people go to school so that they mug up algorithms, you're missing the point of school. You go to school to learn how to problem-solve, how to model problems mathematically and incidentally become aware of a repo of solved problems which may help you in your own problem solving adventures.
- oggyhead 9y agoThis is what I read in this article. The author has a problem with people thinking that rote-learnt algorithms is the best thing ever, and proceeds to say nope a stash of the most subjective heuristics to produce 'good code' is wayyyy better. All in all the way I see it, the author is proposing to supplant a shittty misconception with a bs idea that is nice short term solution but a complete disaster in the long term which has inculcated into this idea that programming is an Art and not a discipline.
- rmdashrfroot 9y agoI agree with this argument, please continue explaining.
- snarfy 9y agoWhen it's both, they call it a craft. Good craftsmanship is the art. Knowledge of the trade is the discipline.
- fantispug 9y agoMath is a clean room where you don't need to worry about the concrete representation. Often the details of the representation and how they connect are more to do with human psychology (keeping things understandable) than with algorithmic heuristics.
- bordercases 9y agoI've never found out how to build organizational skills.
- AlexCoventry 9y agoModularization, encapsulation and DRY are good places to start learning to organize code.
- acroback 9y agoWhy the fk do these stupid companies then ask really hard Algorithm puzzles in interviews? This is insane, what is imp? Giving too much info or not, asking more questions or not? Oh man, sometimes I hate this process of interviewing.
- fwdpropaganda 9y agoWhat do you suggest they should ask instead?
- serpix 9y ago- what do you like doing? - how are you as a person, a coworker - are you able to ask for help? - can you hold a conversation? - how do you learn? - describe a failure in your career and how it went from there all this is for the interviewer and the interviewee to get to know each other each other and see if the candidate is a good fit for the company culture and values. If the recruitment lets in a narcissist or toxic person it will poison the well.
- fwdpropaganda 9y agoIsn't that just really vague and easy stuff that requires no knowledge of any kind?
- groby_b 9y agoThese would be perfect questions, if candidates didn't lie. They do. All the time. More often than you'd think about something as trivial as "can you actually write code". And so, you'll need to demonstrate your skills. Find a better way with an extremely low false positive rate, and you can make a fortune consulting and implementing that. It's not like anybody likes doing these interviews.
- rimliu 9y ago> And so, you'll need to demonstrate your skills Alas, the skills you are asked to demonstrate have very little to do with the actual skills required for the job you are interviewing for.
- sriku 9y agoOne sentence summary of the skill and attitude needed for this - "take a sad song, and make it better" .
- foreigner 9y agoI totally agree, so how can we interview for this?
- Madmallard 9y agoIt's basically "what big projects have you done a ton of work on". Have them design something not straight forward or posted online in front of you as well.
- innocentoldguy 9y agoPlease no! Tech interviews are already steaming hours of worthless horse shit as they are.
- droidist2 9y agoI think they meant improving interviews by testing for this instead of algorithmic brain teasers on a whiteboard.
- innocentoldguy 9y agoI did not read that into the original comment, but if the OP's suggestion is to rid the interview process of dumbass brainteasers and whiteboard questions, then I'm all for it.
- codingdave 9y agoYou need to ask questions that let them show off their full understanding of a system. People without organization skills will focus on one area and not explain the whole. My favorite is to have someone explain to me what happens when a browser makes a HTTP request to a web URL, which has <insert framework and DB here>. Network guys will tell you all about the request and response, web developers will focus on the front end, devOps will tell you how all the pieces communicate, etc. My expectation is for someone to at least be able to give a high level of all those things, while also having detailed knowledge of some specific areas... and seeing how they choose to answer such an open-ended question tells you quite a bit about where their focus and attention lies.
- thinkloop 9y agoThere is something that doesn't ring completely true about this. While I agree coding is not about coming up with some ninja recursive one line function that solves all the problems, reducing it to a simple matter of organization is not quite right either. Yes it is about organization, but there is a component of wizardry too. It takes a lot of intelligence, skill, experience and talent to be able to identify and model the fundamental relationships between all the parts in the simplest possible way. It's what separates seniors from juniors. The top guys do the tricky work of architecting and modeling the system, while the juniors fill it in until enough new information is revealed for the seniors to improve/change/update it as needed.
- watwut 9y ago> The top guys do the tricky work of architecting and modeling the system, while the juniors fill it in until enough new information is revealed for the seniors to improve/change/update it as needed. If that is how it works, I did not really experienced it. In one place where they attempted this, senior ended completely out of touch with his architecture problems - because it was only juniors experiencing them and never him. In big corporations, architect does super uber high level and negotiations. Big refactoring and architectural changes were done by seniors and require experience, of course. But that is only part of what senior does, a lot of if is using existing architecture. Also, juniors can grow into such senior only by taking on larger and larger tasks - you don't get there by filling small boxes without doing own decisions, mistakes and living with them. The biggest problems, especially in larger projects, are organizational one. As in, algorithms part is what is often done by juniors, who often actually can do them well being just out of school and being trained in them lately. And also who have bigger uninterrupted chunks of time then seniors.
- TheOtherHobbes 9y agoBut that’s the point. There are algorithms for sorting with known properties. There are no algorithms for problem analysis - just a lot of tradition (e.g. “refactoring”) which is hand-wavey even when it’s done well, and actually adds complexity when done badly. The kind of problem segmentation => simplest solution we’re talking about isn’t even mentioned on most CS courses, and certainly isn’t taught in any useful way - possibly because it hasn’t been researched or understood.
- YeGoblynQueenne 9y agoThe tough truth is that you need to be able to do both, or your skillset will never be complete. If you specialise in algorithms, you might never be able to put a bunch of them together to build a system that works and does something interesting. If you focus on architecture but never understand how to read and implement algorithms and how to evaluate them, you will always be limited in what your systems can achieve and how well they work. Additionally, most of us are limited in what we can learn in a lifetime. Talent is far from the primary limitation (most people will be average in terms of innate ability; my guess). Far more important is the time available to study and learn new skills and the motivation to do it. Then there are issues of personal preference: if you just love algorithms, you will tend to focus on them, if you love building systems, etc.
- blowski 9y ago> The tough truth is that you need to be able to do both There are many, many more opportunities for organised people who aren't great with algorithms, than disorganised algorithm geniuses.
- collyw 9y agoThe only times I have needed to implement a sort algorithm are for interview questions in 15 years.
- fouc 9y agoIsn't organizational skills a fancy way of saying refactoring & (depending on your language) Object-Oriented-Design? Just look at Sandi Metz's or Avdi Grimm's or Martin Fowler's writings and there's lots of good ideas on how to organize your code.
- xamuel 9y agoIn practice, Object-Oriented is incredibly disorganized, and you'll need an organizational wizard to clean up the mess.
- henrik_w 9y agoThis is exactly my experience too. When I started working as a SW developer, I expected to use a lot of the clever algorithms I had studied at university. That didn't happen. Instead, the tricky problem was having lots and lots of simple features aggregated together - complexity from aggregation. These were my top 2 surprises when I started working as a programmer: https://henrikwarne.com/2012/08/22/top-5-surprises-when-starting-out-as-a-software-developer/ https://henrikwarne.com/2012/08/22/top-5-surprises-when-star...
- CodeArtisan 9y agowe want to establish the idea that a computer language is not just a way of getting a computer to perform operations but rather that it is a novel formal medium for expressing ideas about methodology. Thus, programs must be written for people to read, and only incidentally for machines to execute. This is from the preface of SICP[1] which taught me that abstraction is the most important concept of programming (and computer science?). Do you need to know how sqrt() has been implemented to being able to use it? no. A programmer shall first have a good knowledge of the abstraction techniques. He shall know how, when, and the cost to use them. Then, if you are illiterate when it come to algorithm design and analysis, it shall not be a problem because replacing a bad algorithm/implementation by another would be easy due to the correct application of abstraction. "The cleaner and nicer the program, the faster it's going to run. And if it doesn't, it'll be easy to make it fast." — Joshua Bloch [1] https://sarabander.github.io/sicp/ https://sarabander.github.io/sicp/
- ndh2 9y agoDoes this promo piece add anything to the original blog post that it feeds on? I didn't notice anything. Why not link the blog instead? http://prog21.dadgum.com/177.html http://prog21.dadgum.com/177.html
- jakelazaroff 9y agoSide note for anyone who hasn't heard of the original blog before: it's fantastic. Well worth a few hours browsing through its archives.
- hellofunk 9y ago> But it’s hard to have the patience to wrap your head around a disorganized mess that you don’t care about. Only if the disorganized mess is your responsibility, something that means more to you than a case study, can you wrap your head around it and appreciate improvements. This really hit home for me. I personally find it very difficult to get emotionally invested and therefore effective when working on a codebase that I don't personally like. But that's not very professional, so I tend to phone it in when in that situation, at the expense of really using my talents or dedication. But I know that other professional coders do better than me and somehow find a way to be very interested or invested in things they don't care about, perhaps because for many coders, the code itself is enough to warrant the personal interest, and less so what the actual code is used for? If I don't have a big-picture appreciation of a project, I don't enjoy the small stuff either. Perhaps that means I'm in the wrong profession.
- wonton2 9y agoI have found out that the only thing that motivates me is thinking about the people that will use what i code. Either the users find it useful and enjoyable or the company find it profitable. I dont see any reason to work on something where i cannot see my role in contributing to these things.
- stupidcar 9y agoI was thinking along similar lines the other day. I was thinking about whether I've actually improved as a software developer over my career. It occurred to me that most of the languages and frameworks I use are either less than a few years old, or have been changed or reinvented in substantial ways. As such, not much of the declarative knowledge from my early career is of much use. But have my skills improved? I came to conclusion that my ability to code on the micro scale, e.g. at the level of an individual method or algorithm, probably stopped improving after 2-3 years of professional experience. I think you could take the 24-year-old me, ask him to work on a narrow problem, and he'd do about as well as I would now. But where the 24-year-old me struggled a lot was at the macro scale. He didn't know how to compose those individual pieces into a cohesive hole, and instead fell back on a handful of patterns like singletons. I remember horrible days trying to unravel my own code and figure out how component X was going to communicate with component Y, and the result was often a mess. I think this macro-scale ability really does improve continuously over time, as you are exposed to more and better patterns for integrating components and managing dependencies.
- AnimalMuppet 9y agoThis is not true of me. Even on the micro scale, I'm much better than I was at 24. I write far fewer bugs. And I write code that communicates intent much better.
- blueprint 9y agoIn other words, a person of training can obtain good skill, but a person of sincerity will end up with much greater skill.