Login
You're viewing the functional.cafe public feed.
  • Sep 18, 2026, 4:04 PM

    Back in college, I had a Systems Architecture and Design professor. The very first day of his class he stood up in front of us and said:

    "One day, you're going to be brought in to help optimize a company. You'll see that they're doing things by using index cards in shoeboxes. Then, after you understand their processes, points of interaction, and audits, you'll find out that the most optimal way for them to work is by using index cards in shoe boxes. Walk away."

    That was one of the best bits of advice I ever got in my career. Why? Because it reinforced that in order to solve a problem, you have to understand the problem. You have to understand how the problem fits into it's larger ecosystem. You have to understand what the solution breaks and what problems it will cause. Nothing lives in isolation. Everything is interconnected.

    The last thing you do as a systems architect is write code.

    I wish like hell more folk understood that, particularly the vibe-coding, rapid iteration, "throw code at it" types.

    💬 34🔄 133⭐ 1

Replies

  • Sep 18, 2026, 6:07 PM

    I had a civil engineering prof spend a whole weeks homework on “sometimes the best solution is to do nothing”. It wasn’t written into the homework, it was the explanation afterwards of why all the active solutions were wrong.

    I think someone in the back actually fell off his chair when the enlightenment hit.

    @jrconlin

    💬 4🔄 42⭐ 136
  • 💬 2🔄 9⭐ 50
  • Sep 18, 2026, 8:13 PM

    @DamonHD @clew

    Heh.

    There was another incident in my life. I was doing some contracting work at a site. There were multiple contractors working at that location. A high level individual was discussing some possible future work with a different contractor, and was outlining the things that they wanted. The exec did a pretty good job describing the problem, the desired outcomes, and the situations that folk would be in when they needed the solution.

    The other contractor sat, and listened to the exec talk for quite some time before they said "I hear you, however, I think this is the solution you really want" and then proceeded to describe a very expensive system that wouldn't have done most of the things the exec had wanted.

    I sent my management a high priority notice to come talk to that exec because it was work I knew my company could deliver.

    We got the contract.

    So, yeah, sometimes even just "standing there" is a damn good idea.

    💬 2🔄 1⭐ 0
  • Sep 19, 2026, 12:48 AM

    @jrconlin @DamonHD @clew

    This all reminds me of a class I took in college on technical documentation. I don't remember the title. I remember the professor had a U-shaped diagram on whiteboard. Before a project can begin in earnest, there was a process which must be followed, and all of it required the proper documentation. Then he humorously drew a line through diagram saying that there are those who take shortcuts and that's why projects fail.

    💬 0🔄 2⭐ 6
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 7⭐ 31
  • Sep 18, 2026, 8:12 PM

    @clew @jrconlin We had a coursework group project on my masters (operational research) to optimise a particular system.

    The trick was that the system as described was, it turned out, already running optimally. The recommended action was "no corrective action -- continue as you have been".

    It was a useful lesson.

    💬 0🔄 3⭐ 25
  • 💬 1🔄 5⭐ 18
  • Sep 19, 2026, 1:33 AM

    @mcmullin this is good advice but it can be difficult to follow. For some reason, it's easier for me to stop, think things through, and proceed calmly in medical emergencies than in my tech job, unfortunately. It's one of the things I have to get better at.
    @clew @jrconlin

    💬 1🔄 1⭐ 7
  • Sep 19, 2026, 9:23 AM

    @alter_kaker @mcmullin @clew @jrconlin I remember too being told that an emergency in a plane is not like you see in an action movie - people shouting at each other, pressing buttons and flipping switches quickly.

    If you've seen a cartoon where the characters end up flying a plane, something goes wrong, and they find the manual and start reading "Congratulations on purchasing your new Zlin Aviation 7532 aircraft..."

    ...that's actually closer to the truth. The copilot gets out the Emergency Procedures handbook and starts reading out the steps one by one, slowly and calmly.

    💬 1🔄 0⭐ 8
  • Sep 19, 2026, 5:00 PM

    @robinadams

    People panic at the unknown. The thing I love about folk in high stress situations (like pilots) is that a not insignificant part of their training involves introducing them to the most horrific experiences you can imagine.

    I'd probably just become a weird, twitchy mess before I qualified for anything.

    @alter_kaker @mcmullin @clew

    💬 0🔄 0⭐ 0
  • Sep 19, 2026, 10:38 AM

    @clew @jrconlin I've lost count of the times a client has come to me looking for an extension to their house and I've respond by showing them how they can better use the space they already have.

    💬 1🔄 0⭐ 9
  • 💬 0🔄 0⭐ 2
  • 💬 0🔄 0⭐ 3
  • 💬 1🔄 3⭐ 6
  • 💬 1🔄 0⭐ 7
  • Sep 18, 2026, 8:17 PM

    @mcr314 @sb

    Look, we warned you that getting those discount pets from that Colombian reseller might be a bit problematic.

    Try a line of white powder that leads out the door.
    Possibly to a neighbor's house.

    💬 0🔄 0⭐ 0
  • Sep 18, 2026, 8:45 PM

    @jrconlin

    In my first few mechanical engineering classes, we were taught that real engineering is mostly pondering. That's what you are paid to do: understand the situation and think about it. That particular professor said your best work should be at your desk, with your feet up.

    It's why I think software "engineering" as we do it today is a joke: not enough pondering.

    💬 8🔄 56⭐ 156
  • Sep 18, 2026, 9:57 PM

    @jrdepriest

    One of the reasons I chafed at things like AGILE and other stuff was that, while the basic core ideas were solid, there were far, far too many ways that those ideas could be corrupted. "Points" and "Sizes" may be meaningless to us, but to anyone else, they're measurements.

    Likewise, call it what you want ("spike" or whatever) but by the end of the two week sprint, you had to have something to show for your effort that someone else can judge and critique you for. That does not lend itself well to thoughtful design work.

    🙎‍♂️"So, Bob, why did you spend half the sprint changing the design you specified last week?"
    👨‍🦰"Well, I learned a bunch of things last week that required redesigning those things."
    🙎‍♂️"That's not very efficient of you."
    👨‍🦰"Neither would spending several months designing something that doesn't work."
    🙎‍♂️"I don't see your point."

    💬 1🔄 1⭐ 0
  • Sep 19, 2026, 3:03 AM

    @jrconlin @jrdepriest

    I gather it's been demonstrated multiple times that open-ended, un-mandated research tends to be far more productive in the long run than specific, targeted research aimed at achieving specific goals.

    Unfortunately the latter tends to be favored by the people with the money to •fund• the research....

    💬 0🔄 0⭐ 10
  • Sep 19, 2026, 3:14 AM

    @cavyherd @jrdepriest

    Not really sure I agree, at least not within this context. Open research is different than directed problem solving. Most code is generated toward problem solving, or at least task resolution. That said, even those sorts of things need to be well understood before action is taken.

    If you're just adding a set of numbers, the problem space is pretty limited and sure, you can probably jump right to the code.

    If you're developing a new cryptographic library, things are quite a bit different, and you'd be far better off making sure that you really do understand the problem space and the sorts of ways that those things fail.

    Likewise, if you're building a markup language parser, knowing that there are probably already several dozen out there is probably going to save you a fair bit of effort.

    💬 1🔄 0⭐ 0
  • Sep 19, 2026, 3:16 AM

    @jrconlin @jrdepriest

    Fair. I was thinking research generally, not so much in a coding context. The latter does seem like a suboptimal context for "throw it at the wall & see what sticks."

    💬 0🔄 0⭐ 5
  • 💬 1🔄 1⭐ 0
  • 💬 0🔄 0⭐ 7
  • Sep 18, 2026, 11:50 PM

    @jrdepriest @jrconlin My uncle, who studied engineering at Durham, quotes his head of department as saying : "I am not here to teach you to be engineers. I am here to teach you to think."

    💬 0🔄 3⭐ 12
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 5
  • Sep 19, 2026, 5:16 AM

    @sigfpe I find that the past few months, I'm spending a lot more time pondering and a lot less writing code that I would consider routine and tedious. Because of Claude.

    💬 0🔄 0⭐ 2
  • Sep 19, 2026, 12:35 PM

    @jrdepriest @jrconlin thats kina why I believe my manager at work when he says that we are engineer. Well maybe we ponder too much...
    Sometimes we ponder all day

    💬 0🔄 0⭐ 0
  • Sep 19, 2026, 6:57 PM

    @jrdepriest @jrconlin
    I work as a so called "SRE", you can call it a glorified sysadmin.

    80% of the work when upgrading a major component (kubernets, postgres, clickhouse, what have you) is reading the changelog, and for each change, digging through our configuration repo to understand how we use the feature that changed and how the change affects us.

    Even then, it's still not enough pondering.

    💬 2🔄 1⭐ 7
  • Sep 19, 2026, 8:16 PM

    @wolf480pl @jrdepriest

    SRE folk are wizards who are able to bend mighty systems to their will. They are skilled jugglers of digital chainsaws and are woefully underappreciated.

    I frequently told folk that my job as a dev was to make sure that every SRE slept through the night, or at worst had at most two buttons to click at 3 AM if an alert ever went off.

    (I also noted that Test Engineers are the trained hackers that were nice enough to give us detailed damage reports. I loved getting stuff from them and giving them the opportunity to unleash holy hell upon my stuff. Any test engineer just running unit or integration tests was a waste of resources. Sadly, folk at the C level saw everyone as fungible because they had no clue what the skills of the job actually were.)

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 1
  • Sep 19, 2026, 8:53 PM

    @jrdepriest @jrconlin
    yeah but then you end up with 5 year old versions of stuff and never have time to upgrade...

    So I don't blame people who just upgrade on dev, wait a week to see if it blows up, if not, upgrade prod, without reading changelog at any point in the process.

    When the upstream project's rate of change is "web-scale", you're stuck between to bad options :/

    💬 1🔄 0⭐ 1
  • Sep 19, 2026, 10:39 PM

    @wolf480pl @jrdepriest

    I mean, a LOT of that supposes that the Change log is accurate. I think we've all see major, breaking changes rolled out in a minor or bug release.

    On a separate note, I noted that I would do version updates once a quarter (unless there was a critical CVE or something), and would do them by hand whenever possible. (There were a few engineers that said "Have Claude do that!", and it made a cold chill run down my spine.)

    Doing those updates re-familiarized me with the code. In addition, the changes were often subtle, and sometimes required changes in other parts of the library or code (so I didn't roll out some breaking change). Plus, they were kinda zen since it was an opportunity to learn some new approach. For instance updates to Rust generally included changes to  clippy which taught me new approaches.

    Surrendering that to some automated function basically made sure that the code was that less familiar to me, meaning that any future changes will probably have subtle errors or force me to learn the change anyway.

    💬 1🔄 0⭐ 0
  • Sep 19, 2026, 10:47 PM

    @jrconlin
    Oh, it doesn't, the second 80% of the work is fixing stuff after it broke due to things not described in the changelog, or that were described but you didn't thought would affect you.

    Also, version updates once a quarter? More like, one dependency a quarter.
    @jrdepriest

    💬 0🔄 0⭐ 2
  • 💬 0🔄 0⭐ 2
  • 💬 1🔄 0⭐ 2
  • Sep 18, 2026, 9:48 PM

    @wronglang

    Oof, it's been multiple decades (and several school renaming events) since then. I believe he only taught a few classes, and was an IBM alumn (although, I also had another prof who was one of the IBM Calculators who taught me COBOL and few other programming languages).

    I don't have any yearbooks from then, so I can't look it up. It's always been a small school, so there's not a lot of stuff put online.

    Damn shame though, I'd love to give him proper credit.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Sep 18, 2026, 10:15 PM

    @wronglang

    Sure thing, it was probably around 1986-1988.

    If there are photos, he had straight black hair and a mustache. (Believe it or not, but that does actually narrow things down a bit.)
    The other gentleman with curly black hair and a mustache was my old History prof who taught me some of my more fun anarchy ideas.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Sep 18, 2026, 11:53 PM

    @wronglang

    Huh, it may have been. Strange that all the articles list him in the Psychology department, but perhaps he changed specialties after I was there? (It would explain a good deal of his teaching methods.)

    Thanks! (Although, now I'm down the rabbit hole of looking up old profs ;) )

    💬 2🔄 0⭐ 0
  • Sep 19, 2026, 12:02 AM

    @jrconlin he is listed as professor of both and apparently he taught the first programming classes there! He was in psychology but obviously saw a little bit of the future and don't a way to teach it. He's listed here among other places:

    lib.digitalnc.org/record/31395

    Sadly passed away in 2013, but I was thinking of poking the college archives to all is anybody remembered the quote, I imagine he told it more than once!

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Sep 18, 2026, 9:08 PM

    @jrconlin Every job that I've been on when management was convinced to rewrite software, I always try to get them to bring in some retirees to walk the team through the manual processes instead of pretending that the to-be-replaced version was magically the right way...because if it was the right way, then we shouldn't rewrite it.

    💬 0🔄 6⭐ 13
  • Sep 18, 2026, 9:37 PM

    @jcolag

    That's brilliant!
    I've often said that it's important to review things like process and procedure, and that includes stuff around software. Life is dynamic.
    The added bonus you introduce is the "teaching" aspect, since the better you understand something, the better you are at teaching it. It also forces the teachers to examine things from outside the view they normally have.

    I love this approach!

    💬 0🔄 1⭐ 0
  • Sep 18, 2026, 11:56 PM

    @jrconlin We have a strong desire to see something work. I know that from my own coding. It's hard to do work for any length of time without seeing something run. I think that's why vibe coding is popular.

    It's easy to automate the formal rules of the existing process but leave out all the manual workarounds. I.e. no way to write notes on a form or staple a document to a form. Then the automated process doesn't work.

    💬 0🔄 0⭐ 3
  • Sep 19, 2026, 12:05 AM

    @mike805

    Oh, I completely understand that. I often say that sometimes the way you think about something is to do 90% of the work. (You investigate, try out an approach to see if it works, etc.) For that part, I get the whole "iterate fast" thing.

    The problem is that if it stops there, you wind up with only the sketch work and the prototype, not the actual version. Explaining that to someone who's got a stopwatch and a pay voucher isn't easy. (I did a LOT of things that had no prior version. I literally had no idea how long it was going to take because there was absolutely no precedent, anywhere. That was super fun to explain to management.)

    Still, the act of construction forms the knowledge not only of the problem but the domain. Whole lot of folk are missing that via vibe coding, which means their next experience essentially starts as blind as the one they just completed.

    💬 0🔄 0⭐ 0
  • Sep 19, 2026, 12:46 AM

    @jrconlin
    reminds me of my favourite maxim:

    “The purpose of a system is what it does”—Stafford Beer

    it also tells—me—that very often to change a company’s processes, you have to change how the company functions, because

    “[O]rganizations which design systems…are constrained to produce designs which are copies of the communication structures of these organizations”—Melvin E. Conway

    💬 1🔄 2⭐ 8
  • Sep 19, 2026, 1:27 AM

    @argonaut @jrconlin sometimes you just need to rewire the company.
    Group A says we have to do this. Group B says we can’t. Can we get their marching orders/source documents for these requirements/prohibitions? I have had to deal with corporate telephone enough.

    💬 1🔄 0⭐ 4
  • Sep 19, 2026, 2:47 AM

    @c0dec0dec0de @argonaut

    Well, as an old history prof would say "Wealth buys power." (And power steals wealth, but that's not important here.)

    The group with money always sets the rules, since they have the power. If they're wise, they listen and work with other groups, particularly the ones that say "it can't be done". It may be that they weren't clear, or that they missed a considerable hurdle that the opposing group  knows all too well.

    Sadly, we've gotten to the point where the Group with money thinks they're also experts and are right because they have money.

    Fortunately, this is also a self correcting action, since they won't have money very long.

    💬 0🔄 0⭐ 0
  • Sep 19, 2026, 1:41 AM

    @jrconlin in my systems design class in grad school, my professor (a former Bell Labs researcher) said that there is wisdom in understanding when something is not a technology problem, but is instead a management problem.

    Also very good advice.

    💬 2🔄 4⭐ 7
  • Sep 19, 2026, 2:25 AM

    @GreatBigTable

    Yep, very much so.

    I would frequently note that some problems have non-technical solutions. It'd be fun to watch some folk grind to a halt with that, but it's very true.

    Likewise, some tech problems get non-technical solutions, due to things like laws and social restrictions.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Sep 19, 2026, 1:46 AM

    @jrconlin My favorite philosophy class at university was one where the professor stood up to start the first session, and the first thing he said was "I know this is a Mickey Mouse class."

    Learned a lot from him!

    💬 0🔄 0⭐ 3
  • Sep 19, 2026, 2:29 AM

    @dancingtreefrog

    Heh. I had an 08:00 AM Philosophy and Ethics course I took. I think I probably either drove my prof nuts or was the star student. Still have no idea to this day.

    First question he asked us: "What is a chair?"
    I was the only person who raised their hand.
    "It's something I sit on."

    We spent the rest of the semester going over various aspects of philosophy and though experiments.

    At the end of the semester he stated "So, now you know that a chair, or any other idea, is not restricted to what you believe, but can be anything, including whatever you happen to be sitting on."

    My response? "Told you"

    I got a 87 in that class, but damn was it useful.

    💬 1🔄 0⭐ 0
  • Sep 19, 2026, 4:05 AM

    @jrconlin What I remember about my class was that it was an Intro to Philosophy class, so it covered schools/categories of philosophy. There was a student that came into class and parked himself in the middle of the front row, and proceeded to try to get the professor to discuss/argue over graduate-level topics. (The guy was a grad student.) Professor finally threw him out of the class because he wouldn't stop!

    I like your professor, he sounds fun!

    💬 0🔄 0⭐ 1
  • Sep 19, 2026, 2:49 AM

    @jrconlin

    My employer is on a big push to consolidate functions into a central department "for efficiency." I.e., as an excuse to lay off 30% of the staff. The reader is left to guess whether they asked the •staff• what would make the work more efficient.

    💬 0🔄 0⭐ 2
  • Sep 19, 2026, 3:18 AM

    @cavyherd

    Sigh. This is one of those super fun executive ideas that let you know that they got ripped off by whoever sold them their MBA. They got the "widget factory" education that only teaches the basics and presumes that everyone has the same job and is completely fungible.

    I fully expect these folk will ask their dentist if they can perform heart surgery with a straight face.

    💬 1🔄 0⭐ 0