Earlier quoted context omitted.
Exactly - this article makes the very common (still) (1) mistake of thinking construction of software == writing code. Construction of software is compiler/interpreter/all the machinery that kicks in to take some text or instructions and makes it do something. To correct the analogy with building physical things - you could compare the architect designing a bridge (and arguing with engineers about materials and budge…
The idea that code is the design and it's the compiler doing the construction has been around for quite a long time: http://www.developerdotstar.com/mag/articles/reeves_design_m...
Why do web sites and software take so long to build? And why is it so hard?
91–100 of 159 posts
Re: Why do web sites and software take so long to build? And why is it so hard?
#92My opinion? Because as much as the software industry loves to adopt the work "engineer", almost none of the sort of websites and software discussed here on HN ever gets anything much like "engineering" in the sense of, say, "civil engineering" done. I think in my ~20year career, I've had only 3 projects that were specified well enough up front that we just "built it according to the plans" and had a satisfied custome…
Re: Why do web sites and software take so long to build? And why is it so hard?
#93brilliant comment in the original post, just in case anybody missed it "When I had my bathroom remodelled, at first I thought it was organized amazingly well and why couldn’t software be like that? There was a designer from Expo, a primary contractor and subcontractors for tiling, painting, etc. a project workbook containing all the documents, including the design, and a logbook for every contractor to record their v…
To be fair, I can see one difference, though, at least here in Euroland: you have all sorts of standards and regulations that buildings and contractors have to adhere to and especially on bigger changes or constructions you would get an independent expert to check whether your contractors and subcontractors did obey all the rules and when they frakked up somewhere along the way, they have to fix it, typically on thei…
So, here anyway, it is also safety which triggers the regulations.
Re: Why do web sites and software take so long to build? And why is it so hard?
#94Also, the whole post is a big subscribe link for me when NoScript is enabled (pretty smart, actually, if it's not a bug).
Re: Why do web sites and software take so long to build? And why is it so hard?
#95My opinion? Because as much as the software industry loves to adopt the work "engineer", almost none of the sort of websites and software discussed here on HN ever gets anything much like "engineering" in the sense of, say, "civil engineering" done. I think in my ~20year career, I've had only 3 projects that were specified well enough up front that we just "built it according to the plans" and had a satisfied custome…
Civil projects are a constant dialogue between client and engineer - but we get further monkey wrenched by one additional stakeholder that software doesn't have: local and at times federal government review. If you think software dev is difficult now, wait til your code is regulated.
Re: Why do web sites and software take so long to build? And why is it so hard?
#96All you need is wheels, brakes, a frame, a power source, a transmission, some fuel, and some crap to connect the power to the transmission to the wheels and the wheels to the frame. And a seat. Oh, and a steering wheel. Boom. Done.
You can hand-build a car by yourself over a couple days. I mean sure, the engine, transmission, frame, wheels, tires, seat, gas tank, carburetor, brakes, etc are all manufactured by hundreds of people and dozens of companies to get you to that point. But basically, you decide what components to use and how to put them together. It takes you a relatively minute amount of time to assemble them and it's much easier than trying to manufacture all the parts yourself.
Somehow, after building cars for over 200 years, both hobbyists and huge corporations find new ways to build them (and seem to enjoy themselves). They even come out with new ones every couple years and keep finding people to buy them. You'd think the general public would wise up to the fact that it's all the same thing over and over and demand our jetson cars already.
Re: Why do web sites and software take so long to build? And why is it so hard?
#97I think these meatheads are complaining because it's work...
Re: Why do web sites and software take so long to build? And why is it so hard?
#98brilliant comment in the original post, just in case anybody missed it "When I had my bathroom remodelled, at first I thought it was organized amazingly well and why couldn’t software be like that? There was a designer from Expo, a primary contractor and subcontractors for tiling, painting, etc. a project workbook containing all the documents, including the design, and a logbook for every contractor to record their v…
Only difference, its really hard to do "git reset HEAD" when the bath tub didn't fit.
Re: Why do web sites and software take so long to build? And why is it so hard?
#99My opinion? Because as much as the software industry loves to adopt the work "engineer", almost none of the sort of websites and software discussed here on HN ever gets anything much like "engineering" in the sense of, say, "civil engineering" done. I think in my ~20year career, I've had only 3 projects that were specified well enough up front that we just "built it according to the plans" and had a satisfied custome…
I'm a civil engineer (five years) and have never been on a project that avoided the problems of a custom poorly specificied software build. Civil projects are a constant dialogue between client and engineer - but we get further monkey wrenched by one additional stakeholder that software doesn't have: local and at times federal government review. If you think software dev is difficult now, wait til your code is regula…
Re: Why do web sites and software take so long to build? And why is it so hard?
#100My opinion? Because as much as the software industry loves to adopt the work "engineer", almost none of the sort of websites and software discussed here on HN ever gets anything much like "engineering" in the sense of, say, "civil engineering" done. I think in my ~20year career, I've had only 3 projects that were specified well enough up front that we just "built it according to the plans" and had a satisfied custome…
I was working as a freelancer for a long time and I had a quite simple solution for lack of documentation. Before the first meeting I'd send a customer 12-page form to fill which covered most of the "what and why" of the project. It quickly turned out that most of people have no idea whatsoever about the product they wanted to buy. I know that it's partly our job to guide people through rough path, but if all custome…
I got this process from another Ruby consultant and it works great - Get wireframes of main page views (usually there are about 6 of these. You can help them create this - Get them to write out, or describe the requirements and take notes - Break the wireframes and requirements into user stories and load it into pivotal tracker with estimates - Tell them "we are going to build all these user stories PLUS 30 'freebie' points of stores. Any changes you want you can spend your freebie points on, and after that you can substitute out currently scheduled points if you really want those changes
It works great so far.