7 ms·

What is it about software development that keeps on attracting these "methodologies"? Why don't doctors or lawyers or commercial pilots have people coming alon

What is it about software development that keeps on attracting these "methodologies"? Why don't doctors or lawyers or commercial pilots have people coming along with a methodologies for doing their jobs? I have a few ideas, but I still feel like there's more to it than I quite understand.

nullspace 7y ago
Can't speak for lawyers or commercial pilots, but doctors absolutely have "methodologies" or processes. And processes that each individual hospital dept sets up last for years. They're usually different across depts and hospitals though.
- tonyarkles 7y ago
  Oh man, our provincial health region recently went through a “Lean” transformation. Talking to people on the inside, it had some positive efficiencies come out of it, but it also resulted in some pretty terrible negative consequences. For example, medication shortages in rural areas, because they figured it would be better to send it to areas that needed it Just In Time. Except... some of those areas only get weekly deliveries, or worse. Similar story with diagnostic medicine. Smaller laboratories shut down because they were redundant, and then lead times for blood work etc go up because of travel time. We used to have a provincial bus/courier system in place, but the govt shut that down because it was losing money, and the health care system suffered for it. Last I heard, rush samples between major centres are currently being shipped by 3-hour taxi cab rides.
  - AstralStorm 7y ago
    Actual Lean as opposed to paper tiger version carefully verifies the effects and side effects of any change. This rarely happens in "Lean" implementations in reality. What happens is "change and see" which is not what the process is about.
    - roenxi 7y ago
      You get into a funny position because management philosophies, Lean included, are basically defined as "Do things that work, don't do things that don't work. Only spend money on things that add value". So basically anything that spectacularly doesn't work is usually not 'actual' [insert method here]. Management failures are rarely obscure even in foresight.
cameldrv 7y ago
Commercial Pilots have Crew Resource Management.
- phkahler 7y ago
  Not to mention checklists for all sorts of things.
  - ekianjo 7y ago
    Checklists are actually a very good thing in aviation. You don't want to have huge variability between what each pilot should be doing.
    - phkahler 7y ago
      I agree. I use them. They're like a formal procedure.
- keithnz 7y ago
  having done software for scheduling air crew onto planes, one of the biggest factors for them are the various aviation authorities rules / airport certifications etc. That shapes a lot of their lives, but airlines do have their own methods for trying to get the "best" out of their staff.
blackflame7000 7y ago
Because that's exactly what software engineering is, coming up with "methodologies" aka algorithms to perform a task more efficiently.
deleted 7y ago
[deleted]
stone-monkey 7y ago
aren't hospitals infamous for their broken processes? It doesn't seem to me like forcing doctors to work 24 hour shifts improves their judgement while on the job, or improves overall health outcomes, anyway.
- blfr 7y ago
  Supposedly it does improve health outcomes because tiredness is less of a killer than patient handoffs between doctors.
MegaButts 7y ago
Pilots especially are heavily trained to use checklists for just about everything. A significant chunk of training to be a pilot is just reinforcing the behavior to always use the checklist. Doctors, based on my limited understanding, are becoming more and more pragmatic about using checklists in surgeries. I am not a doctor, nor am I an expert, I have just read some interesting articles and heard from surgeons that they are trying to improve the process to reduce careless mistakes. No clue about lawyers. So processes can actually be incredibly useful, and oftentimes are designed after the fact. Agile has some neat ideas as well, but in practice I'd say 90% of the time it's pretty fucking terrible and the company would be better off without trying it entirely. Not because agile is bad, but because the people in charge of agile are usually bad. At the end of the day it comes back to something I've learned painfully time and time again throughout my career. No matter how talented you are, you are powerless against a shitty manager.
- deleted 7y ago
  [deleted]
- reading-at-work 7y ago
  > Not because agile is bad, but because the people in charge of agile are usually bad. That's the crux of it. Currently working at an org which is "Agile" and has Scrum masters, but management still insists on measuring work in man-hours and defining requirements in huge chunks then delivering them at arbitrary deadlines. So... it's waterfall with Scrum masters who make it look nice on Jira charts.
- tolien 7y ago
  > Pilots especially are heavily trained to use checklists for just about everything. Yeah, but it didn't appear out of nowhere. NASA et al did a tonne of research [0, 1] that led up to the idea of using checklists. Likewise Cockpit/Crew Resource Management [2] and the psychology of getting people quickly out of aircraft that are on fire [3], all of which were prompted by one disaster or another. Software engineering could use some of that rigour, but I'd anticipate a little resistance to publishing research which shows that the process of building some piece of software was a shitshow because the people running said show were bad at it. 0: https://ti.arc.nasa.gov/m/profile/adegani/Flight-Deck_Checklists.pdf https://ti.arc.nasa.gov/m/profile/adegani/Flight-Deck_Checkl... 1: https://ti.arc.nasa.gov/m/profile/adegani/Cockpit%20Checklists.pdf https://ti.arc.nasa.gov/m/profile/adegani/Cockpit%20Checklis... 2: https://web.archive.org/web/20131026210937/http://yarchive.net/air/airliners/dc10_sioux_city.html https://web.archive.org/web/20131026210937/http://yarchive.n... 3: Lots of which happened after British Airtours 28M, https://en.wikipedia.org/wiki/British_Airtours_Flight_28M https://en.wikipedia.org/wiki/British_Airtours_Flight_28M and https://assets.publishing.service.gov.uk/media/5422efe840f0b61342000277/8-1988_G-BGJL.pdf https://assets.publishing.service.gov.uk/media/5422efe840f0b...
AmericanChopper 7y ago
Software development is an incredibly immature professional discipline, which has lead to people mostly making it up as they go. You also have the rate at which it changes, making it hard for any sort of standard practices to keep up with. Outside of some industries that regulate security and privacy, software development has also never attracted the attention of any regulator that may have an interest in actual quality of workmanship (which would be impossible in any case). Can you imagine the architecture equivalent of shipping terrible code? “This software has bugs” is acceptable, “this brand new building is falling down” isn’t. There’s a standard way to build a house, there’s a standard way to perform heart surgery, there’s nothing close to a standard way to build software, and if you can’t properly plan your work, how can you properly manage it? That seems to be the problem these management fads are trying, and failing, to solve. People hated waterfall because you have to do so much planning up front, and in software development, that process rarely works. Project requirements change, or planning assumptions are proven wrong. So you need a management framework that works without that level of planning. That’s the core of agile in my opinion, only plan a little bit of work at a time. Really I think it just leaves you with the same problems, only now you have a lot of small failures rather than fewer large failures. If you look at the agile shops that succeed, they tend to have good leadership that simply has the competency to plan ahead well. Those teams would likely succeed under any management framework, only with agile you now also have the benefits of continuous delivery.
pkaye 7y ago
Doctors, lawyers and pilots are in highly regulated industries so not just anyone can come in with their new methodologies.
- Ididntdothis 7y ago
  They are also not asked to be innovative. If the software industry decided to stick to one stack for the next few decades we would also get much better methodology and maturity. Instead we have this constant churn of new stuff where we never learn how to use our tools properly.
deleted 7y ago
[deleted]
gtycomb 7y ago
> What is it about software development that keeps on attracting these "methodologies"? Here is one data point for you from personal experience. A few months after got started at a US company operating in about 30 countries (primary business is manufacturing in the Casino and gaming industry) the word came from the CIO that I implement Six Sigma as part of the enterprise architecture activity that I headed. I countered that neither software engineers nor the IT architects and admins worked in the Six Sigma way and wondered at the meeting where this whole idea came from. I was told this was what the Chief Operating Officer and/or VP of Finance wanted to implement "across the company". Such things happen in this world we live in.
dreamcompiler 7y ago
It's because software development is always harder than you think it's going to be, takes longer than you think it's going to take, and results in more bugs than you think it should. So the temptation to seek simplistic magic bullets that "fix" software development is overwhelming. A better idea would be to reexamine why we "think" software should be so much easier than it really is. Perhaps it's because when we watch it being done, it looks like typing.
mmatants 7y ago
Law as an industry is pretty dysfunctional. Plenty of data governance issues, losing track of documents, etc. A lot is at stake there, for sure, but that's actually the thing that process helps with - reliability and safety. And law is very resistant to incorporating that.
- bonoboTP 7y ago
  Lawyers feed on complexity and obscurity. If things made sense and the processes were logical and simple and easy to navigate, nobody would need their services.
booleandilemma 7y ago
New industry + lots of money being thrown around = lots of attention and snake oil salespeople. Software development is riddled with unscientific practices that are derived from some person’s blog somewhere. 100 years from now when they’ve found out the optimal way to do development we won’t have all these methodologies.
- kakwa_ 7y ago
  Software is also a really immature field. Software development is not an industrial process, it's more like craftsmanship. Part of it comes from the fact the field is relatively young, but also because in software, it is extremely easy to modify to suit new needs and to fix introduced mistakes which results in an inherent instability of design and no strong patterns. It's getting better, but it's still present. For example, nearly each source tree I've seen has its own idiosyncrasies in term of organization and layout. Are the tests in ./test/ or ./tests/? how do I run the tests? where do you put the headers? ./inc/? ./include? what are the options available at compile time? how are they exposed? what are the install targets? does it support the usual variables (looking at you DESTDIR)? Granted more modern languages tend to be more normalized than the previous examples which are valid for C/C++ mainly. But these questions still applies. For example, the Go projects I've seen tend to vary wildly in term of compile tool chain, some have nothing, just run go build, other have a ./build.sh and the better ones have a basic Makefile which is generally not so great (no variable present to override the path to the go binary or set some compilation variables, no proper install target, very weird handling of the ./vendor/ directory in some cases).
  - 6thaccount2 7y ago
    Also, there are big differences in the paradigm used. Sure OO is dominant in enterprise software, but there is also functional programming and many others that have a big impact on organization.
  - deleted 7y ago
    [deleted]
  - rstuart4133 7y ago
sagebird 7y ago
As the demand for computer automation increased, the market produced tools that less intelligent people could use, like Visual Basic vs C++. Management fads infect the dummies. How many lisp nerds do you see at an agile circle jerk meetup? Lawyers and doctors still have an intelligence test in the form of admissions criteria to universities, programmers don’t.
- thanatropism 7y ago
  > Lawyers and doctors still have an intelligence test in the form of admissions criteria to universities, programmers don’t. This is both incredibly rude and pretty much irrefutably true. As a startup cofounder I've had the experience to hire like 3.5 programmers to do front-end work in the past year. I'm not at a specially "hot" location for developers, but my n=3.5 anecdata is that the few intelligent programmers you can find have terrible work ethics and continually try to spend more time with what they find interesting and avoid drudgery work. The hoi polloi (who might have made damn fine designers, copywriters, etc.) rely on stack overflow for whatever they can, and dither on the slightly more challenging tasks they didn't know existed. Besides filtering on IQ, one thing a nerdy education teaches you is that challenging problems are often solvable if you will just [wo]man up and try.
marcosdumay 7y ago
Doctors are always on the news for resisting such imposed methodologies, the amount of them should be much larger than what is visible. For pilots, I literally work in a pilots methodology factory :) But if you want to see crazy methodologies, imposed by the ton, by people that have no idea what they are talking about, go look at teachers.
blihp 7y ago
The fact that software development is not something most organizations understand how to do (well/at all) but still insist on trying to do anyway. Unfortunately, this means that a significant percentage of their projects will fail. Changing out methodologies/tech stacks/languages are great way to redirect blame when things go wrong.
praptak 7y ago
'What is it about software development that keeps on attracting these "methodologies"?' An unbelievably high level of interdependence between worker teams caused by the complexity of the product. This produces chaos, the methodologies promise to tame it.
micmil 7y ago
They all have methodologies. The pilot's checklist that was already mentioned is just one. For doctors you have different paths of treatment that can be standardized for years, then undergo major changes when new information is discovered. With lawyers it depends on what they do. New approaches to cases, new discovery methods, everything is a process and everything can be improved. Software development attracts these things because software development isn't as firmly entrenched in tradition as doctors or lawyers are. There are way more people that are open to implementing ways of accomplishing tasks that are more open and efficient than there ever could be in most other realms.
DanBC 7y ago
> Why don't doctors [...] have people coming along with a methodologies for doing their jobs? They do. You're not involved in healthcare so you don't read healthcare specific websites. Here's some stuff aimed at the English NHS, but there is lots more. http://horizonsnhs.com/ http://horizonsnhs.com/ https://fabnhsstuff.net/ https://fabnhsstuff.net/ https://q.health.org.uk/about/ https://q.health.org.uk/about/ This tends to be the NHS learning about something and implementing it themselves, rather than hiring a management consultant. That's because they want to protect public money and there has been a lot of bad experience of management consultants for this kind of work in NHS organisations.
dragonwriter 7y ago
> What is it about software development that keeps on attracting these "methodologies"? Nothing. Management theories exist around managing every specific kind of work, as well as generic theories. Software development, HR, and other kinds of work that are done in (or contracted for by) almost every organization of non-trivial size probably get a bit more because more people are managing them. Many of the theories in software development are direct adaptations of process theories from other disciplines. Waterfall —before it was named—was just application of practices from non-software engineering, Lean is from manufacturing, kanban is a specific practice from the manufacturing organization whose processes inspired Lean, etc. “Agile” started in software but it's everywhere. > Why don't doctors or lawyers or commercial pilots have people coming along with a methodologies for doing their jobs? They do. They are even often the same methodologies seen in software: e.g., in healthcare: https://www.healthcatalyst.com/insights/healthcare-project-management-techniques-pragmatic-approach-outcomes-improvement https://www.healthcatalyst.com/insights/healthcare-project-m.... Note that the theories around software are often the theories of process improvement rather than the daily work in other domains (interestingly, this is not true or kanban), because software is just automated process so software development is essentially the exact same task as process development/improvement, where some portion of the process is executed on a computer.
philpem 7y ago
It's not just software -- manufacturing sees a new "methodology" every other year. Sometimes two or three in one year.
TheOtherHobbes 7y ago
Software is derived from the production line/engine room model. It's based almost entirely on metaphors that assume the things that matter happen in a sequence, and there are ways to make the sequence faster, more efficient, more reliable, and predictable. So the same thing applies to software management. And also - in different ways - to management in general. Law is derived from the competitive sport model. The sport is verbal rather than physical, but it's really a form of mental combat with the physical violence abstracted away. So in practice it's a combination of business negotiation, corporate politics, national and international diplomacy, book research, a very specific kind of creative writing, acting, public speaking, and psychology of persuasion, with different emphases in different areas. You could have a process for basic case management, and I would be surprised if practices didn't. But the sharp and pointy end - the part where all the elements are used to create a negotiated contract or a court performance - is very difficult to formalise.
pnw_hazor 7y ago
Doctors, lawyers, and commercial pilots are licensed professionals. Doctors and lawyers are personally liable for their screw-ups. I don't know how liability works with pilots but they will lose their license if they screw up. By operating within the medical standard of care, doctors diminish malpractice liability. So having well-defined systems that help prove that you follow the medical standard of care is important. Lawyers don't have anything like that as a whole. Each lawyer handles their clients their own way. Even in the same firm different partners will have different practices. Some use checklists for their staff to confirm that the certain required forms have been filled out or provided. In the actual work of lawyering, checklists are not a thing I have seen. Though there are "outline" documents to help with bigger projects.
blaser-waffle 7y ago
Methodologies are attractive for situations that are ambiguous. Lawyers and pilots have a clear cut set of procedures. Pilots aren't inventing new technologies each time they fly, they're just driving the bus from City A to City B and worrying about occasional edge cases. Lawyers follow legal procedures and have their own built-in rules and processes; they're tested on these processes to pass the bar. You see methodologies for things that vary wildly like sales, military leadership, and of course, engineering tasks. Each project, situation, or client could be extremely different, and it's not possible to build a prescriptive how-to for each scenario. So you create a methodology and framework so that managers and leaders can quantify uncertain situations and build (and alter) their own how-to's.

nullspace 7y ago

Can't speak for lawyers or commercial pilots, but doctors absolutely have "methodologies" or processes. And processes that each individual hospital dept sets up last for years. They're usually different across depts and hospitals though.

tonyarkles 7y ago
Oh man, our provincial health region recently went through a “Lean” transformation. Talking to people on the inside, it had some positive efficiencies come out of it, but it also resulted in some pretty terrible negative consequences. For example, medication shortages in rural areas, because they figured it would be better to send it to areas that needed it Just In Time. Except... some of those areas only get weekly deliveries, or worse. Similar story with diagnostic medicine. Smaller laboratories shut down because they were redundant, and then lead times for blood work etc go up because of travel time. We used to have a provincial bus/courier system in place, but the govt shut that down because it was losing money, and the health care system suffered for it. Last I heard, rush samples between major centres are currently being shipped by 3-hour taxi cab rides.
- AstralStorm 7y ago
  Actual Lean as opposed to paper tiger version carefully verifies the effects and side effects of any change. This rarely happens in "Lean" implementations in reality. What happens is "change and see" which is not what the process is about.
  - roenxi 7y ago
    You get into a funny position because management philosophies, Lean included, are basically defined as "Do things that work, don't do things that don't work. Only spend money on things that add value". So basically anything that spectacularly doesn't work is usually not 'actual' [insert method here]. Management failures are rarely obscure even in foresight.

cameldrv 7y ago

Commercial Pilots have Crew Resource Management.

phkahler 7y ago
Not to mention checklists for all sorts of things.
- ekianjo 7y ago
  Checklists are actually a very good thing in aviation. You don't want to have huge variability between what each pilot should be doing.
  - phkahler 7y ago
    I agree. I use them. They're like a formal procedure.
keithnz 7y ago
having done software for scheduling air crew onto planes, one of the biggest factors for them are the various aviation authorities rules / airport certifications etc. That shapes a lot of their lives, but airlines do have their own methods for trying to get the "best" out of their staff.

blackflame7000 7y ago

Because that's exactly what software engineering is, coming up with "methodologies" aka algorithms to perform a task more efficiently.

deleted 7y ago

[deleted]

stone-monkey 7y ago

aren't hospitals infamous for their broken processes? It doesn't seem to me like forcing doctors to work 24 hour shifts improves their judgement while on the job, or improves overall health outcomes, anyway.

blfr 7y ago
Supposedly it does improve health outcomes because tiredness is less of a killer than patient handoffs between doctors.

MegaButts 7y ago

Pilots especially are heavily trained to use checklists for just about everything. A significant chunk of training to be a pilot is just reinforcing the behavior to always use the checklist. Doctors, based on my limited understanding, are becoming more and more pragmatic about using checklists in surgeries. I am not a doctor, nor am I an expert, I have just read some interesting articles and heard from surgeons that they are trying to improve the process to reduce careless mistakes. No clue about lawyers. So processes can actually be incredibly useful, and oftentimes are designed after the fact. Agile has some neat ideas as well, but in practice I'd say 90% of the time it's pretty fucking terrible and the company would be better off without trying it entirely. Not because agile is bad, but because the people in charge of agile are usually bad. At the end of the day it comes back to something I've learned painfully time and time again throughout my career. No matter how talented you are, you are powerless against a shitty manager.

deleted 7y ago
[deleted]
reading-at-work 7y ago
> Not because agile is bad, but because the people in charge of agile are usually bad. That's the crux of it. Currently working at an org which is "Agile" and has Scrum masters, but management still insists on measuring work in man-hours and defining requirements in huge chunks then delivering them at arbitrary deadlines. So... it's waterfall with Scrum masters who make it look nice on Jira charts.
tolien 7y ago
> Pilots especially are heavily trained to use checklists for just about everything. Yeah, but it didn't appear out of nowhere. NASA et al did a tonne of research [0, 1] that led up to the idea of using checklists. Likewise Cockpit/Crew Resource Management [2] and the psychology of getting people quickly out of aircraft that are on fire [3], all of which were prompted by one disaster or another. Software engineering could use some of that rigour, but I'd anticipate a little resistance to publishing research which shows that the process of building some piece of software was a shitshow because the people running said show were bad at it. 0: https://ti.arc.nasa.gov/m/profile/adegani/Flight-Deck_Checklists.pdf https://ti.arc.nasa.gov/m/profile/adegani/Flight-Deck_Checkl... 1: https://ti.arc.nasa.gov/m/profile/adegani/Cockpit%20Checklists.pdf https://ti.arc.nasa.gov/m/profile/adegani/Cockpit%20Checklis... 2: https://web.archive.org/web/20131026210937/http://yarchive.net/air/airliners/dc10_sioux_city.html https://web.archive.org/web/20131026210937/http://yarchive.n... 3: Lots of which happened after British Airtours 28M, https://en.wikipedia.org/wiki/British_Airtours_Flight_28M https://en.wikipedia.org/wiki/British_Airtours_Flight_28M and https://assets.publishing.service.gov.uk/media/5422efe840f0b61342000277/8-1988_G-BGJL.pdf https://assets.publishing.service.gov.uk/media/5422efe840f0b...

AmericanChopper 7y ago

Software development is an incredibly immature professional discipline, which has lead to people mostly making it up as they go. You also have the rate at which it changes, making it hard for any sort of standard practices to keep up with. Outside of some industries that regulate security and privacy, software development has also never attracted the attention of any regulator that may have an interest in actual quality of workmanship (which would be impossible in any case). Can you imagine the architecture equivalent of shipping terrible code? “This software has bugs” is acceptable, “this brand new building is falling down” isn’t. There’s a standard way to build a house, there’s a standard way to perform heart surgery, there’s nothing close to a standard way to build software, and if you can’t properly plan your work, how can you properly manage it? That seems to be the problem these management fads are trying, and failing, to solve. People hated waterfall because you have to do so much planning up front, and in software development, that process rarely works. Project requirements change, or planning assumptions are proven wrong. So you need a management framework that works without that level of planning. That’s the core of agile in my opinion, only plan a little bit of work at a time. Really I think it just leaves you with the same problems, only now you have a lot of small failures rather than fewer large failures. If you look at the agile shops that succeed, they tend to have good leadership that simply has the competency to plan ahead well. Those teams would likely succeed under any management framework, only with agile you now also have the benefits of continuous delivery.

pkaye 7y ago

Doctors, lawyers and pilots are in highly regulated industries so not just anyone can come in with their new methodologies.

Ididntdothis 7y ago
They are also not asked to be innovative. If the software industry decided to stick to one stack for the next few decades we would also get much better methodology and maturity. Instead we have this constant churn of new stuff where we never learn how to use our tools properly.

deleted 7y ago

[deleted]

gtycomb 7y ago

> What is it about software development that keeps on attracting these "methodologies"? Here is one data point for you from personal experience. A few months after got started at a US company operating in about 30 countries (primary business is manufacturing in the Casino and gaming industry) the word came from the CIO that I implement Six Sigma as part of the enterprise architecture activity that I headed. I countered that neither software engineers nor the IT architects and admins worked in the Six Sigma way and wondered at the meeting where this whole idea came from. I was told this was what the Chief Operating Officer and/or VP of Finance wanted to implement "across the company". Such things happen in this world we live in.

dreamcompiler 7y ago

It's because software development is always harder than you think it's going to be, takes longer than you think it's going to take, and results in more bugs than you think it should. So the temptation to seek simplistic magic bullets that "fix" software development is overwhelming. A better idea would be to reexamine why we "think" software should be so much easier than it really is. Perhaps it's because when we watch it being done, it looks like typing.

mmatants 7y ago

Law as an industry is pretty dysfunctional. Plenty of data governance issues, losing track of documents, etc. A lot is at stake there, for sure, but that's actually the thing that process helps with - reliability and safety. And law is very resistant to incorporating that.

bonoboTP 7y ago
Lawyers feed on complexity and obscurity. If things made sense and the processes were logical and simple and easy to navigate, nobody would need their services.

booleandilemma 7y ago

New industry + lots of money being thrown around = lots of attention and snake oil salespeople. Software development is riddled with unscientific practices that are derived from some person’s blog somewhere. 100 years from now when they’ve found out the optimal way to do development we won’t have all these methodologies.

kakwa_ 7y ago
Software is also a really immature field. Software development is not an industrial process, it's more like craftsmanship. Part of it comes from the fact the field is relatively young, but also because in software, it is extremely easy to modify to suit new needs and to fix introduced mistakes which results in an inherent instability of design and no strong patterns. It's getting better, but it's still present. For example, nearly each source tree I've seen has its own idiosyncrasies in term of organization and layout. Are the tests in ./test/ or ./tests/? how do I run the tests? where do you put the headers? ./inc/? ./include? what are the options available at compile time? how are they exposed? what are the install targets? does it support the usual variables (looking at you DESTDIR)? Granted more modern languages tend to be more normalized than the previous examples which are valid for C/C++ mainly. But these questions still applies. For example, the Go projects I've seen tend to vary wildly in term of compile tool chain, some have nothing, just run go build, other have a ./build.sh and the better ones have a basic Makefile which is generally not so great (no variable present to override the path to the go binary or set some compilation variables, no proper install target, very weird handling of the ./vendor/ directory in some cases).
- 6thaccount2 7y ago
  Also, there are big differences in the paradigm used. Sure OO is dominant in enterprise software, but there is also functional programming and many others that have a big impact on organization.
- deleted 7y ago
  [deleted]
- rstuart4133 7y ago

sagebird 7y ago

As the demand for computer automation increased, the market produced tools that less intelligent people could use, like Visual Basic vs C++. Management fads infect the dummies. How many lisp nerds do you see at an agile circle jerk meetup? Lawyers and doctors still have an intelligence test in the form of admissions criteria to universities, programmers don’t.

thanatropism 7y ago
> Lawyers and doctors still have an intelligence test in the form of admissions criteria to universities, programmers don’t. This is both incredibly rude and pretty much irrefutably true. As a startup cofounder I've had the experience to hire like 3.5 programmers to do front-end work in the past year. I'm not at a specially "hot" location for developers, but my n=3.5 anecdata is that the few intelligent programmers you can find have terrible work ethics and continually try to spend more time with what they find interesting and avoid drudgery work. The hoi polloi (who might have made damn fine designers, copywriters, etc.) rely on stack overflow for whatever they can, and dither on the slightly more challenging tasks they didn't know existed. Besides filtering on IQ, one thing a nerdy education teaches you is that challenging problems are often solvable if you will just [wo]man up and try.

marcosdumay 7y ago

Doctors are always on the news for resisting such imposed methodologies, the amount of them should be much larger than what is visible. For pilots, I literally work in a pilots methodology factory :) But if you want to see crazy methodologies, imposed by the ton, by people that have no idea what they are talking about, go look at teachers.

blihp 7y ago

The fact that software development is not something most organizations understand how to do (well/at all) but still insist on trying to do anyway. Unfortunately, this means that a significant percentage of their projects will fail. Changing out methodologies/tech stacks/languages are great way to redirect blame when things go wrong.

praptak 7y ago

'What is it about software development that keeps on attracting these "methodologies"?' An unbelievably high level of interdependence between worker teams caused by the complexity of the product. This produces chaos, the methodologies promise to tame it.

micmil 7y ago

They all have methodologies. The pilot's checklist that was already mentioned is just one. For doctors you have different paths of treatment that can be standardized for years, then undergo major changes when new information is discovered. With lawyers it depends on what they do. New approaches to cases, new discovery methods, everything is a process and everything can be improved. Software development attracts these things because software development isn't as firmly entrenched in tradition as doctors or lawyers are. There are way more people that are open to implementing ways of accomplishing tasks that are more open and efficient than there ever could be in most other realms.

DanBC 7y ago

> Why don't doctors [...] have people coming along with a methodologies for doing their jobs? They do. You're not involved in healthcare so you don't read healthcare specific websites. Here's some stuff aimed at the English NHS, but there is lots more. http://horizonsnhs.com/ http://horizonsnhs.com/ https://fabnhsstuff.net/ https://fabnhsstuff.net/ https://q.health.org.uk/about/ https://q.health.org.uk/about/ This tends to be the NHS learning about something and implementing it themselves, rather than hiring a management consultant. That's because they want to protect public money and there has been a lot of bad experience of management consultants for this kind of work in NHS organisations.

dragonwriter 7y ago

> What is it about software development that keeps on attracting these "methodologies"? Nothing. Management theories exist around managing every specific kind of work, as well as generic theories. Software development, HR, and other kinds of work that are done in (or contracted for by) almost every organization of non-trivial size probably get a bit more because more people are managing them. Many of the theories in software development are direct adaptations of process theories from other disciplines. Waterfall —before it was named—was just application of practices from non-software engineering, Lean is from manufacturing, kanban is a specific practice from the manufacturing organization whose processes inspired Lean, etc. “Agile” started in software but it's everywhere. > Why don't doctors or lawyers or commercial pilots have people coming along with a methodologies for doing their jobs? They do. They are even often the same methodologies seen in software: e.g., in healthcare: https://www.healthcatalyst.com/insights/healthcare-project-management-techniques-pragmatic-approach-outcomes-improvement https://www.healthcatalyst.com/insights/healthcare-project-m.... Note that the theories around software are often the theories of process improvement rather than the daily work in other domains (interestingly, this is not true or kanban), because software is just automated process so software development is essentially the exact same task as process development/improvement, where some portion of the process is executed on a computer.

philpem 7y ago

It's not just software -- manufacturing sees a new "methodology" every other year. Sometimes two or three in one year.

TheOtherHobbes 7y ago

Software is derived from the production line/engine room model. It's based almost entirely on metaphors that assume the things that matter happen in a sequence, and there are ways to make the sequence faster, more efficient, more reliable, and predictable. So the same thing applies to software management. And also - in different ways - to management in general. Law is derived from the competitive sport model. The sport is verbal rather than physical, but it's really a form of mental combat with the physical violence abstracted away. So in practice it's a combination of business negotiation, corporate politics, national and international diplomacy, book research, a very specific kind of creative writing, acting, public speaking, and psychology of persuasion, with different emphases in different areas. You could have a process for basic case management, and I would be surprised if practices didn't. But the sharp and pointy end - the part where all the elements are used to create a negotiated contract or a court performance - is very difficult to formalise.

pnw_hazor 7y ago

Doctors, lawyers, and commercial pilots are licensed professionals. Doctors and lawyers are personally liable for their screw-ups. I don't know how liability works with pilots but they will lose their license if they screw up. By operating within the medical standard of care, doctors diminish malpractice liability. So having well-defined systems that help prove that you follow the medical standard of care is important. Lawyers don't have anything like that as a whole. Each lawyer handles their clients their own way. Even in the same firm different partners will have different practices. Some use checklists for their staff to confirm that the certain required forms have been filled out or provided. In the actual work of lawyering, checklists are not a thing I have seen. Though there are "outline" documents to help with bigger projects.

blaser-waffle 7y ago

Methodologies are attractive for situations that are ambiguous. Lawyers and pilots have a clear cut set of procedures. Pilots aren't inventing new technologies each time they fly, they're just driving the bus from City A to City B and worrying about occasional edge cases. Lawyers follow legal procedures and have their own built-in rules and processes; they're tested on these processes to pass the bar. You see methodologies for things that vary wildly like sales, military leadership, and of course, engineering tasks. Each project, situation, or client could be extremely different, and it's not possible to build a prescriptive how-to for each scenario. So you create a methodology and framework so that managers and leaders can quantify uncertain situations and build (and alter) their own how-to's.