10 ms·
I know exactly how it happens. Engineering projects take a long time. 90% of the effort lives in the basement where nobody can see it; getting data from some
by jrockway 7y ago
I know exactly how it happens. Engineering projects take a long time. 90% of the effort lives in the basement where nobody can see it; getting data from some other system, optimizing queries, spinning up the servers... nothing at all user-facing. So to the untrained eye, 90% of the time, programmers are doing nothing. And that 90% can be weeks, months, even years.
I don't think any of this is unique to software engineering, either. You don't just one day decide to build a bridge and show up at the bank of the river with a cement mixer tomorrow. To someone that wants to drive over the river, it looks like no progress is being made on the project. Hence, lots of meetings (delaying the project further) to make sure everyone is working hard enough. (Because there is always "that one guy" who actually isn't doing anything. And it looks the same as someone who is working hard to an outsider.)
As for why we spend money hiring people that don't actually do anything, tracking the progress of other people's work... I think it's just loss aversion in action. If you spend 10% of the day working on timesheets and pay an additional employee to check up on them... you know where your money's going. But if someone just shows up to work and does nothing, then they're stealing from you and must be punished! It is human nature.
I don't know what we did in the past that's different from today. Somehow we got to the moon. But now companies are so bloated that even doing nothing seems like it requires 30,000 employees. I don't have much hope for the future generation of megaprojects. And, you know, we're not really doing them anymore. I wonder what changed. Or maybe looking back at the all the achievements of the entire human race at once makes it difficult to put the present day into perspective.
- raverbashing 7y agoTo be honest I still can't understand how those big megaprojects got out of the ground with people coordinating by face to face meetings, circulating memos and phone calls Maybe that's part of the secret, communication was more expensive so you wasted less time with noise But how do you put a switch on the panel of the 747, make the wire go all the way to the tail of the aircraft and make it do what you need it to do?
- TomMarius 7y agoMy suspect is distraction. People used to be able to deep work regularly.
- ghaff 7y agoThat's a pretty optimistic view. My recollection is more along the lines of lots of phone calls and people stopping by your office on a regular basis.
- asark 7y agoRevolutionary Road was released at the tail end of 1962 and has some stuff to say about office work. If it's accurate (I suspect it's pretty close) then it was largely about passing papers around trying to avoid having to actually do anything with them, without it looking like you're trying to avoid doing anything. Very similar to modern corporate email, sending crap around forever and bringing in more "eyes" trying to avoid making a decision or—god forbid—actually personally doing real work that produces an actual good. [EDIT] tail end of 1961, actually, got that wrong.
- TomMarius 7y agoMy point was more that the people are also highly distracted by people around them who are also constantly distracted and thus buzzing, usually because of social media. The only solution is to go away, but then you're not seen in a good light.
- VBprogrammer 7y agoI don't know if you are correct in a 'global productivity sense'. I do know that it's quite common for me to get more 'real work' done on the train on the 30 minute journey to work than in the rest of the day.
- ghaff 7y agoYou have a lot of formal processes, a lot of time/effort/money goes into coordination. Having been involved, not with megaprojects but with fairly large design projects (offshore drilling rigs, computer systems) mostly pre- modern communication systems, there were plenty of phone calls, memos, and meetings.
- MrBuddyCasino 7y agoPeter Thiel asked himself the same question. If you subtract screens and style, how do know you‘re not living in 1973? I think Yuval Harari was onto something when he said that what guides the vision of a society and thus science spending is ideology, religion and politics. See medieval churches, the Manhattan Project, the moon landing. I could put a name on it, but better to leave politics out of HN.
- polyomino 7y agoit's hotter
- defterGoose 7y agoOoh, this heats close to home.
- yoz-y 7y ago> If you subtract screens and style, how do know you‘re not living in 1973? Depending on where you live I’d say access to resources you could not imagine back then for peanuts. People complain that technology is expensive now, but prices in the 70s and 80s were out of reach for most.
- taneq 7y ago> I could put a name on it, but better to leave politics out of HN. Dunno about churches but the other two were prompted by active large-scale military conflicts. Bring back the Cold War, I guess?
- tim333 7y agoAs someone who kind of remembers 73 in England, the coffee is way better now. Also we had some epic strikes and power cuts back then and a splendid 73% market crash. After decades of relative economic decline we decided to join EEC, the predecessor to the EU after which things recovered economically from the 'sick man or Europe' to the fastest growing economy in Europe until we recently voted to go back to the good old days.
- fnord123 7y ago>I don't have much hope for the future generation of megaprojects. And, you know, we're not really doing them anymore. I wonder what changed. We are still doing megaprojects just fine. And less people die doing them.
- michaelt 7y agoThe First Transcontinental Railroad, 1868 mi in length, was built between 1863 and 1869. Six years - completing a route from the Atlantic to the Pacific. California High-Speed Rail, 520 mi in length, began construction in 2015, cost 90x as much per mile, even after accounting for inflation, and.... was indefinitely postponed in 2019. For a rail line in a single state. Admittedly, with much higher speed, and much more humane construction. But nonetheless, even with a much higher per-mile price they still couldn't deliver it? I can see how someone someone might get the impression we aren't able to successfully deliver large projects any more.
- defterGoose 7y agoWe also live in an era where the government (federal, state, whatever) is seemingly viewed by many as less a benevolent force to be co-opted, and increasingly as a necessary evil to be thwarted and disempowered. Sure, the time period you mention is right around the heart of the civil war, with all the anti- and pro-establsihment sentiment that came along with it, but these feelings were rather new at the time. Most people were still farmers who valued "getting shit done" more highly than divorced-from-reality ideological barriers. The country was still needing to be connected and filled up.
- papln 7y agoRead the US Constitution and the Declaration of Independence if you thing this view is new.
- defterGoose 7y agoI'm of course aware of the basis of these documents as an American. However, a lot of the core ideas behind the US' founding were that it was possible to form "a more perfect union". I.e. one where government was done 'right', I.e. democracy. There were certainly anarchists at the time too, but the form of anti-government sentiment we have now seems to be almost pathological; memetic rather than considered.
- radiospiel 7y agoA manager must be able to answer the question "Are we on time? Do we need additional resources?". This happens to help a project, not to delay it. If a good team of developers estimates the effort needed for anyone task with a 20% accuracy (which would be very good indeed), that can make a 9 month project being 2 months late, which might or might not be acceptable. If developer teams would be treated like the blackbox they apparently want to be treated as would mean that whoever is managing procuesses would fly blind just hoping for the best - but the organization as a whole needs to be understanding what is going on right now. Time tracking can be a surveilling tool, but it can also be a tool to improve things - someone could find out that a team is running over capacity, and consequently assign more resources to the task at hand or redefine the task. And, well, for morning standups: when done right they are a valuable tool for efficient communication, and probably better than having people chasing each other for hours on end. IMHO an organisation should agree on a communication strategy that is the most efficient and helpful for it. It is not a religious belief that a standup meeting must be done first thing in the morning, I think that tends to conflict w/the teams personal schedules the least.
- steve_taylor 7y ago> "Are we on time? Do we need additional resources?". This happens to help a project, not to delay it. If, by “resources”, you mean people, then Fred Brooks might have something else to say about that.
- coldtea 7y ago>A manager must be able to answer the question "Are we on time? Do we need additional resources?" This happens to help a project, not to delay it. If we know anything in IT, it's Brook's law: "Adding manpower to a late software project makes it later". So if the manager asks that for a late project, they are probably incompetent. >If a good team of developers estimates the effort needed for anyone task with a 20% accuracy (which would be very good indeed), that can make a 9 month project being 2 months late, which might or might not be acceptable. For a small (a few days) project, 20% accuracy doesn't make any difference. For a large one, 20% accuracy is science fiction stuff compared to the actual accuracy rates of big projects, especially the kind with changing requirements, new issues discovered en route, etc (which is most of them). >If developer teams would be treated like the blackbox they apparently want to be treated as would mean that whoever is managing procuesses would fly blind just hoping for the best - but the organization as a whole needs to be understanding what is going on right now. If the manager is not part of the team / actively involved (and thus he is inside the "black box") then any numbers they get is bogus, time tracking or not. Software is a qualitative process, not a quantitative. "5 hours spent on X" mean nothing at all without knowing what was done for X.
- wozmirek 7y agoI respectfully disagree. Manager's job here would be to: - work with devs to make sure whatever gets into the work pipeline is well understood - everybody agrees on the planned work scope - prevent anyone from adding "just this tiny thing" into planned scope| - visualise all of this tough, tough dev work, especially the ad-hoc work (putting out fires, for example) - keeping both management and devs accountable - and more! Also I disagree with the bridge metaphor; while true, you can't use the bridge when it's 50% done, you should ideally be able to to use 5% of the planned feature. If you can't, then maybe it was planned out badly and shouldn't go into planning in the first place? If there's a person that's "working hard" in a team and a person that's "hardly working", then the team has a big issue and should do everything to fix that. However, This takes a lots of guts on part of (both!) the manager and developers and always has an emotional toll.
- lr4444lr 7y agoWell for one, this whole "agile" concept of changing things midstream can't be helping. No one says once a bridge is 20% built. Hmm... You know what, more height to avoid noise and smog problems in fact seems to be a better focus than high vehicular weight. Let's start making those adjustments and expect to stick to our time, cost, and quality estimates. Outside of a few niche areas, calling what's going on in software "engineering" seems laughable to me, and I never refer to myself with that term.
- lzol 7y agoI feel like other engineering disciplines would function closer to the software world if it was easier to iterate. It is very difficult to nearly impossible to change the design of a bridge once construction has started. If it was super easy, we'd very likely change things once they were in use. Perhaps we didn't account for pedestrians using the bridge and they're walking across it all the time or tractor trailers are having trouble making a right off the bridge. Software is inherently "soft". It's malleable. When done well, it can create better fit to purpose solutions than almost any other discipline. I agree that most "software engineering" is more like plumbing, but I do feel like "real" engineering disciplines would likely follow a similar paradigm if they had the same luxury to rework things.
- LanceH 7y agoThe development of the road system as a whole is very much iterative.
- samstave 7y agoWell, look at tooling... and in the bridge analogy; material selection. Look at the bay bridge, we built it using steel from china which, after it was already being used to construct the span was later found to be inferior. So in SW dev -- you might choose a tool for a massive project only to find its the wrong/not best tool you could have selected based on the budget at the time the project started. This can also be said of the team. Employee A was the right eemployee at the start of the project, but they later prove to not be the best resource, but youre already X% down the project timeline... what do? Esp at what cost.
- bluedino 7y ago>> Somehow we got to the Moon. But now companies are so bloated that even doing nothing requires 30,000 employees. The Apollo program had 400,000 people involved at it's peak.
- coldtea 7y agoWhich is neither here, nor there. The programmers for the Apollo software (which is what we're discussing), were at their peak, around 350 [1]. And most of those roles were secondary and only needed because of the primitive tooling and utmost reliability requirements that modern software doesn't suffer from... [1] David G. Hoag, 1976 - http://klabs.org/history/history_docs/mit_docs/1711.pdf http://klabs.org/history/history_docs/mit_docs/1711.pdf
- papln 7y agoApollo software is pretty simple, relatively speaking. It was a hard, but small problem compared to what we expect from modern tech like a car or airplane. Modern software is far more reliable than Apollo. The difference is that 99.9% correct-uptime is terrible for modern vehicle software, but was great for Apollo. https://space.stackexchange.com/questions/6361/success-fail-probabilities-for-apollo-xi https://space.stackexchange.com/questions/6361/success-fail-...
- deleted 7y ago[deleted]
- papln 7y agoThis is exactly the problem free market capitalism attempts to solve. To put it oversimply, you have a choice: * "command&control model" the risk is born by the client, paying cost+15% for everything where they oversee all the work. Low trust, lots of bureaucratic overhead, but if the are competent enough, they can get the project done. * "free market" model: risk the is born by the vendor -- payment upon successful delivery -- very high profit margin if the project suceeds, but $0 pay if the project fails or is even just second best. One trick is, even in the "free market" model, you have nested command&control inside vendors, with the same problems that the original client had. You can go "free market" all the way down, but you are still stuck with all the human risks -- people can cheat, be accidentally incompetent, or lose everything just for being second best at project A when they could have been the best at project B. > Somehow we got to the moon. The moon isn't hard to reach, it's just not worth the price. If you allocate another $250B like last time, and it will get done -- either publicly command&control NASA, or by paying SpaceX. We spend collectively about $100B/yr on the Internet, and it's super complex and huge and works amazingly well (works well technically -- how people you hate choose to use it is a human social problem)
- ci5er 7y ago> But if someone just shows up to work and does nothing, then they're stealing from you and must be punished! It is human nature. I do realize that far too many people put their faith in the healing power of judgement. But that is partly because, as a component of that cognative circuit, is that most people have some sort of innate desire to see things as "fair". Certainly not to be the victim! (That's bigger, actually, by far). People who work with people know who the slackers or the non-producers are. I try to separate those, because some high-output producers can appear to be slackers because they think for 8 days before they type that one magical line of code that saves the project. (It's hard to tell when you are in the trenches day-to-day which may be which). In any case! (I almost got lost in my parenthetical there), Workers know which co-workers are getting paid to not produce, and know that this wage, applied to a producer would lower their own work load 10% (or whatever), and besides: it's NOT fair! He get's paid $100K/year to not work! And I work my ass off for the same wage! It's enough to make me stop working myself. That will certainly show "them". At the end of the day, if we do not purge the slacker, morale-rot sets in on the rest of the team, and that's just "bad". Even without the needing to be punitive in our heart, those people must be culled for the continued positive morale of the herd. Or, so, I thought once. Now - I'm not so sure. But it seemed reasonable at the time!