5 ms·
Weeks of coding can save you hours of planning.
by exabrial 9y ago
Weeks of coding can save you hours of planning.
- Joe-Z 9y agoHaha, you just summed up perfectly what I was trying to describe with my child-comment to another poster on here!
- cordite 9y agoI wear this shirt to work.
- LeoNatan25 9y agoBut then it wouldn’t be called “hacking”, and so wouldn’t pass as software development these days. Instead, let’s have no planing whatsoever, no design and no requirements, have minimal time for actual development, “hack” code together and see where bugs take us. Aka “scrum”, “agile” and whatnot.
- Joe-Z 9y agoI feel like the problems you describe here (constantly changing requirements, minimal time for development, "hacking" code together) have less to do with agile methods and more with people-stuff. I think agile methods can help a great deal in software development, especially breaking apart your projects into more discreet steps and supervising progress or giving the possibility for correcting course via sprints. Also using eXtreme programming tools like pair programming or code reviews to avoid having people slip into a frenzy of their individual domain / help keep obvious bugs out. Having minimal time and changing requirements is just part of the game. And people "hacking" code together is just... well bad craftsmanship really
- javabean22 9y ago>>using eXtreme programming tools like pair programming or code reviews to avoid having people slip into a frenzy of their individual domain / help keep obvious bugs out. Wtf does this even mean? What are you talking about. If the bugs are obvious why do you need extreme programming to find them? What frenzy? Extreme programming is garbage.
- LeoNatan25 9y agoAgreed. From my experience, when a proper preparation is done and there are clear requirements, most of the "obvious" bugs do not even come into play. They do, when "hacking" a feature and / or working in "POC" mode, which, for me, is not software engineering.
- Joe-Z 9y agoFor me it isn't either and I'm certainly not advocating for "hacking" features together. The obvious bugs I mentioned were not design bugs, but simple slips that creep in when you've already worked for a few hours and your attention starts lacking.
- Joe-Z 9y ago>If the bugs are obvious why do you need extreme programming to find them Because sometimes you've already worked for a few hours and end up wasting time with stuff, which could have been spotted easily by help of a fellow developer. >What frenzy? The frenzy I was talking about was referring to working on a project for weeks on end and forgetting that of course you are now skilled in that domain you built yourself, but at some point other people will have to work with that system too and for them your answers might not be that obvious. Having other people check in regularly can prevent this. Also, please don't 'wtf' me, you could have just as easily framed your question in a more humane way. I wasn't trying to defend extreme programming here, but merely stating that a focus on open communication will lead to more robust software. Don't abuse my comment for furthering your personal hate against some software development methodology.
- javabean22 9y agosorry fren
- SAI_Peregrinus 9y agoAgile methods are people stuff. Agile is just another management strategy. Standard engineering design breaks projects into discrete steps, it's not at all unique to Agile. Doing that is essentially the definition of "work breakdown structure". Course correction time is built into Gantt charts. Engineers have had to deal with constantly changing requirements, minimal development time, etc, since long before software came around. They're further constrained because you can't just ship a patch to a bridge or plane after it's completed. And yet they manage to get reliable, functional work done! Agile is management with ADD. Waterfall is a straw man process that no competent organization would use.
- lr4444lr 9y agoDo you ever get the feeling that software "engineers" are expected to be little more than business-ops guys with a higher IQ and a habit of unusual fascination with solving problems that must be done in tiny detail?
- booleandilemma 9y agoDon't worry about creating bugs, we have a separate team to fix those.
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- jameslk 9y agoPlanning assumes you know what you're building. Most of my career has involved dealing with others who aren't sure of what they want, and whom change their minds on a regular basis. See also: Big Ball of Mud http://www.laputan.org/mud/ http://www.laputan.org/mud/
- shams93 9y agoBam! You hit the nail right on the head. Now when its just a freelance customer its not as stressful, what is really horrid is when you have a product manager getting paid big bucks who has absolutely no clue how things work and no interest to find out, he has just one demand, "never tell me anything i ask for is impossible", that's a hard demand when he refuses to actually learn anything about technology or the web.
- protonfish 9y agoThis isn't necessarily a bad thing. Software prototypes are an excellent tool to explore solutions to problems. We need to stop the hubris that we can immediately know exactly what we need without any effort.
- jononor 9y agoYes, but then exploring solutions should be an explicit goal. And the problem to be solved must be defined, along with criterias for evaluating solutions. Otherwise it's just an excuse for "we don't know what we are doing or why".
- exabrial 9y agoAgree. But then when the prototype becomes the product is when things really get bad.
- exabrial 9y agoAgree. But then when the prototype becomes the product is when things really get bad.
- ScottBurson 9y agoHaving recently made the mistake of diving too quickly into coding something, without having done enough analysis, I have to upvote this. Sometimes nothing slows you down as much as being in too much of a hurry.
- Koshkin 9y agoOn the other hand, writing testable code can be a perfectly valid and very useful part of the design process - even at its initial stages, when things are just being explored. There is nothing special about writing code compared to scribbling on a piece of paper or just walking around and thinking. Who says that pseudocode must always be written in a pseudo-language? Incidentally, prototyping also gives rise to a very powerful idea of solving the problem by first creating a domain-specific language in which a solution to the problem can be expressed in the most natural way, and then providing an efficient implementation of that language.
- ScottBurson 9y agoYes, and often diving into the code works for me, which is why I'm in the habit of doing it, but in this case two or three days of whiteboarding and analysis might have saved me a couple of weeks of going down a dead end.
- Too 9y agoThere is also the opposite, which is even worse: Weeks of planning can save you hours of coding.