14 ms·
Project from Hell (2008)
- lainga 9y agoDoing a first checkout requires taking an appointment with the version control team, usually granted a week later. Editing files is not permitted without authorization from middle management. Ah, I recognize this. It is a special level beyond workplace hell, Tokugawa shogunate hell, where the entire organization is structured to provide as much busywork for as many superfluous management layers as possible. Fifteen porters for every samurai...
- hinkley 9y agoYeah but think of all the sweet swords and armor you can have when you have a dozen people to carry your stuff...
- bitwize 9y agoThe Tokugawas liked to spy on their daimyo and samurai, the better to maintain and consolidate power. Giving each samurai fifteen porters was a great way to make sure that eyes friendly to the shogun were on that samurai at all times. I'll leave the workplace parallels as an exercise.
- VMG 9y ago> Versioning is simple. Old software is version 1, today’s software is version 2, software in the future is version 3. Nobody can actually tell which version has been delivered to the customer. Many such cases
- deleted 9y ago[deleted]
- corrigible 9y agoSounds like they invented Continuous Delivery ;-)
- mpweiher 9y agoAnd there are people who claim performance doesn't matter, only correctness does. Hmm.. Also: we chose C++, because it is fast.
- msla 9y ago> And there are people who claim performance doesn't matter, only correctness does. Hmm.. Performance is meaningless if the code is not correct. After all, I can make the code arbitrarily fast if I'm not going to be held to any standard of correctness: It always returns "FOOBAR". Done, and very, very fast. > Also: we chose C++, because it is fast. That is a bit naive. C++ is a standard, so how fast is a stack of paper?
- hinkley 9y agoThere’s a great phrase for this I stole a long time ago: faster than possible. When your code is only fast because it does the wrong thing, and fixing the problem takes much more overhead.
- desertrider12 9y agoC++ is only "fast" because people who care about performance use it and a lot of people who are good at compilers work on gcc/intel/llvm. If the LLVM team decided to spend 5 years making python "fast", I bet they could make it benchmark just as well as C++.
- msla 9y ago> If the LLVM team decided to spend 5 years making python "fast", I bet they could make it benchmark just as well as C++. Better, perhaps, if John Walker's experiences with Javascript are anything to go by: https://www.fourmilab.ch/fbench/fbench.html https://www.fourmilab.ch/fbench/fbench.html John Walker has a program called fbench which is a floating-point benchmark built around raytracing. He's implemented it many times, in many languages, throughout the decades, beginning with implementations for the original IBM PC. Anyway, the results are posted on the site, in terms of multiples of the speed of the C implementation, which is defined to be 1.0. The Python implementation is 2.633 (PyPy 2.2.1 (Python 2.7.3), Linux), and the Javascript implementation is 0.372 (Mozilla Firefox 55.0.2, Linux). Yes, it completes in approximately a third the speed of a C implementation compiled on full optimization (-O3) by GCC 3.2.3. (The C++ implementation is at 0.939, GCC 5.4.0 -O3.) Anyway, Javascript has been the target of a lot of people for a fairly long time, and, despite the fact it's a very dynamic (hard-to-optimize) language... well, the numbers speak for themselves. I have no doubt Python could be improved to a similar degree. Downloads: https://www.fourmilab.ch/fbench/ https://www.fourmilab.ch/fbench/ The weblog post where he analyzes the modern Javascript numbers a bit: https://www.fourmilab.ch/fourmilog/archives/2017-10/001715.html https://www.fourmilab.ch/fourmilog/archives/2017-10/001715.h...
- rhapsodic 9y ago>Average turn-over for the newcomers: 3 months, the legal time to leave your job in France. Can someone explain the meaning of this? I think something got lost in translation.
- sodapopcan 9y agoI took it as you aren’t allowed to quit until you’ve been somewhere for three months.
- 66o 9y agoActually it depends. When you're on probation period in France you can quit as well as be fired on the spot or within 2 weeks depending how long you've been hired for (don't remember the exact timeframe). Then after your probation period is over (it can last from 4 to 7 months) there is 3 month notice period on both (employer and employee) sides.
- neuromantik8086 9y agoYou have to work for 3 months before you can quit an employer in France. It's not "at-will". At least that's how I interpreted it, and given France's stronger labor laws I wouldn't be surprised if that's the case.
- baud147258 9y agoNo, it's the length necessary before the process is finished. You give your resignation and the contract is terminated 3 months later.
- hadrien01 9y agoThat's exactly how it's done, except in Alsace-Moselle (the German part of France during a few wars) where it's two weeks when the employee wants to leave and two to four months (depending on job-specific labour laws – convention collective – and seniority) when the employee is fired.
- mpweiher 9y ago
- baud147258 9y agoRegarding this part: "they had to pay soon for Free Software. None of them ever mentions ‘Software Libre’, but they all know about ‘Software Gratuit’. " In French, we have two word for Free: Libre is for free as in free speech and gratuit is for free as in free beer.
- lainga 9y agoWhich we had to borrow to distinguish the two, thus LibreOffice (which is also conveniently GratuitOffice).
- maxxxxx 9y agoSame in German. It's a quirk of English that free as in freedom and free as in no cost are the same word.
- mrybczyn 9y agoBut then you get the great quip that 'freedom isn't free'...
- maxxxxx 9y ago"Freiheit ist nicht umsonst" just doesn't have the same ring :-)
- arfar 9y agoIn English we do have the word "liberty" for freedom.
- andrewflnr 9y agoWell, we do have the word "liberty" in English, too. Maybe it's more that one meaning for a word and one word for a meaning just aren't enough for us.
- dragonwriter 9y ago> Well, we do have the word "liberty" in English, too But no commonly-used adjective form of that noun.
- toomanybeersies 9y ago> It is forbidden to come to work after 9am. One day, the site manager stayed behind the main gates and fired on the spot every person who came in after 9.01am, including a number of managers and sales. This surprised me. I thought it was extremely difficult to fire people in France.
- baud147258 9y agoFrom another post in the blog: "Among the many comments, some surprised me. Seems lots of people cannot believe you can be fired in France for being 1 minute late at work. Sorry to burst your bubble, mates, but this is what SSIIs (contractor companies) were invented for. You don’t lose your job, you immediately lose the contract you are working on (no justification needed, this is what contractors are for)" So they were not really employees, but consultants. Still, he also wrote: "For people who have a direct contract with the company, same story. Nothing prevents the company from saying you have committed a major blunder, fire you on the spot, and see you a couple of years later in court (Prud’hommes). Yes, that will cost them money if people choose to sue (I hope they all did). When you are unemployed, are you really looking forward to two years of battle with your former employer, even though you know you will win?" Link to the post: https://projectfailures.wordpress.com/2018/03/24/follow-up-on-project-from-hell/ https://projectfailures.wordpress.com/2018/03/24/follow-up-o...
- marcosdumay 9y ago> So they were not really employees, but consultants. On places where it's hard to fire people, mostly everybody works as consultants and people tend see those positions as normal job positions.
- 1ris 9y agoIn Germany it is hard to fire somebody. Almost nobody works as consultant, and consultants are not normal job positions.
- 9y ago
- hinkley 9y agoWith a moment of silence in sympathy for this poor sod who is sharing a special level of pain few of us have encountered... > With so many files in store you may think that two people working on the same file would be rare, but it turned out that most work happened within the same 100 files or so. Not really surprising, unfortunately. This is a hallmark of the Big Ball of Mud. Thousands of code files and yet people keep tripping over each other.
- baud147258 9y agoAnother comment regarding this: "In a country like France, corruption is not uncommon at that level, goes mostly undiscovered and is rarely prosecuted. " My brother is working in a construction bussiness in France and he has a handfull of stories of this type of high-level corruption (house built for the ex-mayor, refection work done for a lawyer, invitations to Roland-Garros...). But as the author have said, it's the same thing everywhere.
- kakwa_ 9y agoNot to mention that we have the former president Nicolas Sarkozy on trial for corruption right now. He just took a few millions from Muammar Gaddafi to finance his 2008 campaign. And there were a slew of big international military contracts in the 80ies/90ies which were subverted to finance political campaigns (Taiwanese frigates, Agosta contract with Pakistan). These scandals tend to be judged long after the facts (10 to 20 years), and the verdict is generally underwhelming to say the least.
- baud147258 9y agoI've said high-level to contrast to street-level when you slip a bank note to avoid a fine or go first in the queue, but his stories do not implicate that level of corruption, at most local politicians.
- jt2190 9y ago> 12 years after [1996], the project is still active. The company recovers daily penalties by billing ever-increasing change requests to the government. The year is 2008. So this was a project for a government agency in France that limped along for years.
- jmull 9y agoI would guess the project was (is?) running pretty much just as the people in charge wanted it to run. 10 years in and they were still billing -- more than ever -- for a project that would have completed 7-8 years previously if things had been done according to plan. All the seemingly massively stupid and counter productive decisions made make sense if the goal is to confuse matters to make it seem like progress has been made or reforms instituted or bold corrective actions taken while actually keeping the project hopelessly mired. It's like the Producers. (Though without the ironic twist... in reality it surely must be impossible to accidentally complete a software project successfully. No doubt, without the laughs either.)
- ryandrake 9y agoWhat did the demotivational poster say? Consultants don’t make money with solutions, they make money by prolonging the problem.
- fnordsensei 9y agoThat's the fallacy with hourly billing. The alternative model is value-based pricing, where you price the solution/intervention upfront. Of course, this becomes more expensive upfront as well, because the consultant takes on the risk. Hourly billing seems cheaper to the client, since they have to take on the risk instead.
- kakwa_ 9y agoPublic contracts (like the one mentioned in the blog post) are "valued-based" ("contrat au forfait" in french). But you can circumvent these by over-billing contract additions/change in requirements ("avenants" in french). In theory those are limited to 20% of the original amount, but with contract renewals and if the government agency already sunk large sum of money into the project it's possible to bypass this limit.
- sokoloff 9y agoWhich leads to situations like this: http://www.quartetservice.com/wp-content/gallery/boat/cs-pic2.jpg http://www.quartetservice.com/wp-content/gallery/boat/cs-pic...
- ryandrake 9y agoI love how the first thing complained about was the use of C++ for the project. Compared to the lack of sane source control and release management, inexperience of the team, dozens of layers of abstraction, management bureaucracy, toxic culture, basic facilities like toilets being inoperative... I think using C++ was literally the least of their concerns.
- sjm-lbm 9y agoThey also started, if I'm doing my arithmetic right, in 1996. Honestly, I could see C++ having been their best choice back then. Every language I would rather do a large project in is either newer than that or would have been pretty immature for a large project in the mid-90s.
- TheCoelacanth 9y agoC++ was pretty immature for a large project in 1996. It was first standardized in 1998.
- hfdgiutdryg 9y agoIt was already in wide use long before then. Microsoft's MFC was first released in 1992, and that was the Windows desktop library for years. Java was still new and slow. There were some interesting RAD tools, but those weren't particularly well suited to 'large' projects.
- rosser 9y agoI worked on a mega-LoC (millions of lines of code) C++ project in the late 90s. It wasn't even (to the extent I could honestly tell at that point in my career, anyway) a particularly hellish codebase or design, and suffered none of the madnesses described in The Fine Article. (Of course, we were sub-sub-contractors working only on designated parts of the application. The stuff I did touch was consistently sane enough, though, that I don't think I'm too out of place in positing a legit minimal degree of not-terribleness across the rest of the project.)
- 9y ago
- draw_down 9y agoBut by all means, please continue to shit on JavaScript.
- KKKKkkkk1 9y agoWhat I have witnessed there is beyond everything I could possibly have imagined in terms of software engineering. Far more serious than just a lack of professional competence was the utmost contempt for human dignity which at some point made me compare the whole experience to (what I imagine can be) jail. I think these two actually go hand-in-hand. Happy Monday!
- drinchev 9y agoThere are lots of people on the pipeline that take their share of our taxes to deliver to "the letter of the contract" [1], without considering the intend. Closest I've been is when an agency sold my time to another agency which sold my time to the end client, who paid me with "profit" from insurance money ( the end client was an insurance agent ). And as I'm not in my 20s anymore and I look at how government related IT services work, I'm so much afraid about everything else happening around me. Questions like "What about the tram I use every day? There should be a company maintaining these things. Probably is hell there as well." 1 : https://en.wikipedia.org/wiki/Letter_and_spirit_of_the_law https://en.wikipedia.org/wiki/Letter_and_spirit_of_the_law
- cpeterso 9y agoSo what was the ultimate fate of the project? The 2018 follow-up post [1] says the boss was jailed for fraud, but doesn't say whether the project eventually shipped or was killed (or, even worse, is still in development). [1] https://projectfailures.wordpress.com/2018/03/24/follow-up-on-project-from-hell/ https://projectfailures.wordpress.com/2018/03/24/follow-up-o...
- ordinaryperson 9y agoMy best guess is the article referred to Louvois, France's attempt to build a military payment system. An article in French about it: https://www.franceinter.fr/emissions/secrets-d-info/secrets-d-info-27-janvier-2018 https://www.franceinter.fr/emissions/secrets-d-info/secrets-... In 2018 it still does not exist. The French government has decided to try again, awarding the contract to the same company.
- _hearsay 9y agoUsing some hints from the blog, the company is likely Sagem or one his subsidiary, well known for mismanaging armies of consultants. I am not sure they actually worked on Louvois, so this is possibly another unrelated epic failure.
- nudpiedo 9y agoI cannot distinguish this story from a made up one. If someone wanted to make it up it could have not been worse. EDIT: unless personal boundaries would be trespassed.
- EdSharkey 9y agoThe beatings will continue until morale improves
- commandlinefan 9y ago> “C++ for dummies” on many people’s desks. Surprised they didn't get fired for reading/learning at work when you're paid to be programming all the time. Although I've never been fired for reading at work, I've had it made clear on multiple occasions at different jobs that reading wouldn't be tolerated, and I was already down a couple of strikes.
- ILikeConemowk 9y ago> I've had it made clear on multiple occasions at different jobs that reading wouldn't be tolerated Story time? Please? You definitely seem like a good prospect for the following "workplace of hell" saga? ;)
- deleted 9y ago[deleted]
- recursive 9y agoWhat in the actual fuck? I can't fathom how this would even theoretically work. Like people ostensibly would just memorize every api and library they might ever have to use in advance?
- commandlinefan 9y ago> memorize every api and library Outside of work hours, of course. You're paid to program, not to learn.
- astrodust 9y agoMaybe at a hell company like this example, but in most that are sane you're encouraged to learn on the job. At the end of the day you're not paid to program, you're paid to solve problems, and typically that's easiest to achieve by producing code. Sometimes the problem is you don't know a particular language or toolkit even if it's the best fit for a problem domain...
- 9y ago
- n0mad01 9y agoreminiscent of any reasonably large state project.
- kakwa_ 9y agoBeing from France and having worked in a company that deals mainly with government contracts, I've seen some of these aspects first hand. The company I was in was far from being as horrible as the one mentioned in this post and management was not complete douchebags, they never fired people for being 1 minute late, didn't impose strict hours. On thing to keep in mind is that public contracts are extremely unhealthy for all the parties involved. The government agency as more rights than a private organization asking for the same kind of job, the agency can impose everything as long as it is written in the scope statement document (which is rather mediocre in general, can be vague, can be self-contradictory and some requirements may not be doable at all), your actual technical offer as little weight. I remember a project where we got screwed by one pretty vague phrase mentioning a document (which was not provided during the call for bids by the way). In this document there was a lot of idiotic guidelines regarding software path installation, init scripts, users running daemons... that even the government agency didn't follow internally, and that made any kind of automation extremely difficult. We got screwed also by indecision from the client in this project, first Debian was chosen, then CentOS, then a mix of Debian and CentOS, I reinstall our platform 3 or 4 times before it was decided... Then there is the other part. The bids are generally quite competitive, and the most important factor is the price generally, little digging is done on the actual technical quality of the answer. As a result, these projects are generally undersold, with the idea that it will be possible to ludicrously bill maintenance and changes of scope after the initial contract. As an example, I've seen a project where the risk provision was ridiculously low despite the fact a core piece of the system was an off the shelf software that existed only on paper at the time of the call for bids (and we lost several months trying to make it work and advising the editor). Also, sometime some legitimate risks are taken but are not completely assumed. For example, most of these contracts will have a tight schedule, but in general, the government agency will be quite slow on their parts (buying servers for example). So it's safe to assume that your tight schedule is a bit more lax, and you have more time than what is written on the contract. It's taken into account in the bid, but in the end, management doesn't remember it and ask you why it took more than the tight schedule agreed in the contract. Globally, everybody is trying to screw everybody at the detriment of the users who actually need the system. And as an engineer, it's really not satisfying to work in those conditions, you constantly cut corners (unit tests? no.), you have to make due with what you have (I literally stole old servers that seemed abandoned by other projects to work) and you produce sub-par systems that will blow up in production (and you don't have access to production systems, so any bug is pretty much catastrophic). I decided to left this company when a sales guy told me that we were losing money because we "engineer were too perfectionist".
- nineteen999 9y ago> No dynamic library linking: executable sizes in the range of several hundred megabytes I thought that with Golang and the popularity of static linking for apps in Docker containers that this was now considered acceptable again (tongue firmly in cheek).
- std_throwaway 9y agoI don't actually see this as a problem; as long as you're only running one application like that.
- nineteen999 9y agoIf somebody is going to run statically linked binaries, they would understand the security implications of that, and that they need to be able to rebuild and redeploy their binary if a security hole is discovered in a third-party library that was linked into their program. They would already have CI/CD processes in place to rebuild the binary/container, run regression tests and redeploy the application/container to production, surely? So what difference does it make if it's one or one hundred applications/binaries/containers then?
- OliverJones 9y agoComputervision in the 1990s.
- MisterTea 9y ago> Coffee machines are regularly out of order for several days. Somebody who drinks coffee is less productive than somebody sitting at his desk, typing away precious lines of code. > The same coffee machines are switched off whenever officials come to visit the site, to give the impression that everybody is at work. Inconceivable! I'm convinced this person worked for aliens in human skin suits. Think Edgar from Men in Black. Obviously missed the memo from high command where it is mentioned that humans perform better when caffeinated so supply them with plenty of free coffee and tea to keep them productive and ready to harvest, er, review.
- kelvin0 9y agoThis is the 2nd 'French' horror story I've heard. An ex-colleague (ex-pat french man) told me an almost exact same story (different software: numerical simulations). Of course bad software happens all over the globe (Looking at you Canadian Phoenix pay system). However (to me) there are some cultural issues which make things even worse it seems : a VERY rigid chain of command structure and a strict 'political' hierarchy which makes changes happen very very slowly and not always towards the best outcome (for the project, billing is $$$ great). As mentioned each country has issues, but I don't know if I could go into such a strict hierarchical corporate environment.
- alex- 9y ago> given the abysmal quality of this thing, nobody will ever insist that they release the sources I am interested in seeing the source :)
- barbs 9y agoI'd love to see this project on Github, though I'm sure that'd be highly unlikely - it's probably mired in a bunch of red tape, and there's probably some ridiculous technical reason why that wouldn't be feasible.
- kabdib 9y agoI think I've used the source code control system mentioned in the article. It was indeed a pile of garbage. Took a couple days of training in it, and the folks running the class kept telling us not to use certain checkboxes and features of the UI "or bad stuff will happen".
- ww520 9y agoJust curious. What is it?
- seren 9y agoIt might be Telelogic/Rationale Synergy, given it is from a Swedish company originally.
- kabdib 9y agoIt's been nearly 20 years and hard to remember. I think it was called Continuus, but that they changed their name. A sibling comment refers to 'Synergy' and that sounds right. Just another proof that if a product involves the word "Synergy" in its marketing, you should run away fast.
- deleted 9y ago[deleted]
- vegetablepotpie 9y agoI'm curious to know what version control system they settled on.
- puppetmaster400 9y agoWay cheaper than jsf in USA. Also in c.
- TheMagicHorsey 9y agoThere are a lot of jobs like this in economies where stasis and stability are prized over creative destruction. These organization continue to exist because companies are considered sacrosanct ... they are sources of jobs that are to be protected at all costs. The jobs themselves are sacrosanct. Very hard and slow to fire people. So people hire slowly. So there are few jobs. So the few open positions are positions where the employer abuses the employees. Have you ever noticed how many smart French programmers there are in the USA? People vote with their feet when given a chance.
- draw_down 9y agoWhoops, you missed the part where people were fired for being one minute late
- woliveirajr 9y ago> The tool that was finally chosen is a disaster with a graphical user interface, an abomination coming directly from Sweden. Ohh, which versioning software comes from Sweden and is so bad? Got curious about this one.
- emmelaich 9y agoMaybe ClearCase? Centralised, with access through a versioning filesystem. Performance would strongly depend on the power of the server and a bunch of other things. Also, apparently builds are done centrally. A get the shivers just thinking about it. https://en.wikipedia.org/wiki/Rational_ClearCase https://en.wikipedia.org/wiki/Rational_ClearCase See also these two links. https://www.daedtech.com/how-rational-clear-case-stole-my-innocence-and-nearly-ruined-my-life/ https://www.daedtech.com/how-rational-clear-case-stole-my-in... https://stackoverflow.com/questions/1074580/clearcase-advantages-disadvantages https://stackoverflow.com/questions/1074580/clearcase-advant...
- collyw 9y agoClearcase was fucking awful when I had to use it. My install was so fucked I needed a whole new Windows reinstall.
- kpil 9y agoI think it's a French proverb.
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]