3 ms·

You’re wrong about the mentally taxing bit because you’re comparing Apples and Oranges. Most doctors are not spending solid 4hr blocks in flow focusing on a hig

You’re wrong about the mentally taxing bit because you’re comparing Apples and Oranges. Most doctors are not spending solid 4hr blocks in flow focusing on a highly complex problem (surgeons being the obvious exception) but instead dealing with a sort of multi-tasking complexity which is a completely different type of mental taxation.

filleduchaos 3y ago
I mean, most doctors are spending their entire shifts trying not to inadvertently kill or disable anyone. Yeah that's a completely different type of mental taxation - one far worse IMO than any highly complex problem I've ever encountered in software engineering (and quite frankly, the problems aren't that complex most of the time. If anything, personally the SE stuff that's actually hard is fun and the rest is rather mind-numbing).
Zenzero 3y ago
> Most doctors are not spending solid 4hr blocks in flow focusing on a highly complex problem I'm sorry but this is exactly what I meant by my original post. You don't realize that 4hr blocks in flow is an enviable luxury. Granted my time was in a high acuity setting but let me cast it in more relatable terms. Software 1 is brought to you with a complaint of the billing system dropping occasional transactions over the last 4 months. Now it is dropping 1 in 100 transactions. They use the Stripe API. It's your job in the next 15 minutes to debug and determine if there will be a complete service outage occurring within the next couple hours. If there will be an outage, you are expected to push a temporary fix to prod immediately and refer for continued review. If not, you must determine which parts of the billing system require referral for revision. Mind you that every decision you make can be reviewed years after the fact and can be litigated as they please. Your assistsnt comes over with softwares 2 through 5 that were just submitted for your review. Software 2 has issues with a simple deadlock that could have been handled by someone other than you, but now it's your problem to deal with. Software 5 has been inexplicably ported from Delphi to Angular, and they've seen 2 others before you about why some of their native functionality broke, but now it's a big problem and they need you to look at it. There were some patches made by other devs but the stakeholders don't have access to them right now. As you are looking into software 4,the assistant tells you "Dr zenzero, devops is on line 1 for you". They tell you that software 1 has more problems than described and it looks like it needs to be refactored in multiple areas. Software 3 keeps complaining to your assistant that you're ignoring them. So no, "Most doctors are not spending solid 4hr blocks in flow focusing on a highly complex problem" because they don't get that luxury. I get to do that now and it's bliss.

filleduchaos 3y ago

I mean, most doctors are spending their entire shifts trying not to inadvertently kill or disable anyone. Yeah that's a completely different type of mental taxation - one far worse IMO than any highly complex problem I've ever encountered in software engineering (and quite frankly, the problems aren't that complex most of the time. If anything, personally the SE stuff that's actually hard is fun and the rest is rather mind-numbing).

Zenzero 3y ago

> Most doctors are not spending solid 4hr blocks in flow focusing on a highly complex problem I'm sorry but this is exactly what I meant by my original post. You don't realize that 4hr blocks in flow is an enviable luxury. Granted my time was in a high acuity setting but let me cast it in more relatable terms. Software 1 is brought to you with a complaint of the billing system dropping occasional transactions over the last 4 months. Now it is dropping 1 in 100 transactions. They use the Stripe API. It's your job in the next 15 minutes to debug and determine if there will be a complete service outage occurring within the next couple hours. If there will be an outage, you are expected to push a temporary fix to prod immediately and refer for continued review. If not, you must determine which parts of the billing system require referral for revision. Mind you that every decision you make can be reviewed years after the fact and can be litigated as they please. Your assistsnt comes over with softwares 2 through 5 that were just submitted for your review. Software 2 has issues with a simple deadlock that could have been handled by someone other than you, but now it's your problem to deal with. Software 5 has been inexplicably ported from Delphi to Angular, and they've seen 2 others before you about why some of their native functionality broke, but now it's a big problem and they need you to look at it. There were some patches made by other devs but the stakeholders don't have access to them right now. As you are looking into software 4,the assistant tells you "Dr zenzero, devops is on line 1 for you". They tell you that software 1 has more problems than described and it looks like it needs to be refactored in multiple areas. Software 3 keeps complaining to your assistant that you're ignoring them. So no, "Most doctors are not spending solid 4hr blocks in flow focusing on a highly complex problem" because they don't get that luxury. I get to do that now and it's bliss.