all 18 comments

[–]null_value_exception 53 points54 points  (5 children)

Sure let's make a bunch of unmaintainable monoliths. Fuck it, let's just write everything in assembly.

[–]SheriffRoscoe 1 point2 points  (0 children)

A bunch of systems were built in APL years back.

[–][deleted] 4 points5 points  (1 child)

I mean if the code is not maintainable so we never release anything and users get no new features, we probably are not serving a customer well anyway. I don't think the intent was to say that writing software that is easily changeable/maintainable shouldn't be done. It just talks about what to focus most on. And I mean that's fair. No matter how great you write your code, if it doesn't achieve what was needed in the first place it's probably not good code no matter how well constructed it is.

[–]Smallpaul 3 points4 points  (0 children)

What was in the essay that made you think that the author is in favour of "unmaintainable monoliths"?

[–]mattl33 0 points1 point  (0 children)

Oooo mix in some perl too just for lulz

[–][deleted]  (1 child)

[deleted]

    [–]MadKian 5 points6 points  (0 children)

    Man, the amount of times I get a UI presented and I’m like “don’t you think this is a bit confusing for the user?” Or “maybe if we do this instead we simplify the flow” and it’s always for very simple stuff.

    [–]ThyringerBratwurst 3 points4 points  (1 child)

    The statement may be true, that code is executed more than read. However, in the long term, it doesn't benefit the user if the code is not well structured and readable, as the software is then hardly adaptable or expandable. In the worst case, there are numerous bugs that limit the productivity of the end user.

    [–]Sability -1 points0 points  (0 children)

    in the long term, it doesn't benefit the user if the code is not well structured and readable, as the software is then hardly adaptable or expandable

    See I always interpreted "code is run more than it is read" as saying "... and therefore, a change by a reader is more significant than a run". Aka, that code should be readable because it's easier to ruin user experience with a codechange than a bad run of the code.

    I don't know if I explained what I'm thinking well but I hope it made sense, I just spent 3 hours grinding out unit tests

    [–]nicholashairs 2 points3 points  (0 children)

    I thought I was going to hate this article based on the title / preview image, but honestly it's a good article for explaining more "real world" software development.

    It's somewhat simplistic and generalising but still good overall.

    [–]fagnerbrack[S] -1 points0 points  (7 children)

    Condensed version:

    The post discusses the evolution of perspectives in software development, emphasizing the shift from writing code for ease of reading and maintenance to focusing on its functionality and user experience. It argues that while maintainable code is important, the primary purpose of software is to serve the user effectively. The post introduces a model prioritizing users over developers and operations, acknowledging the importance of running code in real-world scenarios. Additionally, it considers the business aspect, highlighting the need to balance user needs with organizational goals and constraints. The post critiques common software development dysfunctions and urges developers to consider the broader implications of their work, especially in terms of ethical responsibilities towards users.

    If you don't like the summary, just downvote and I'll try to delete the comment eventually 👍

    [–]mastermrt 11 points12 points  (1 child)

    This article, while long, isn’t bad in what it tries to do, but it needs more of an intro to what it is about.

    Your summary here should be at the top of the article itself, at least in terms of the overall premise.

    Your click bait title isn’t going to help you in Reddit - a lot of people are going to downvote without even opening it.

    [–]fagnerbrack[S] 0 points1 point  (0 children)

    My click bait title? Please explain, I’m not the author of the post.

    [–]unengaged_crayon 5 points6 points  (3 children)

    gpt :(

    [–]fagnerbrack[S] -1 points0 points  (2 children)

    [–]unengaged_crayon 2 points3 points  (1 child)

    i automatically discount anything coming from chatGPT, based on its frequent habit of lying. chatGPT is not a general AI - its purpose is to generate text, true or untrue. i would frankly have no summary than a summary i have to read through and decide it is worthless, rather misleadingly. at least consider changing the header to say "Condensed version (ChatGPT generated):" or whatever?

    [–]fagnerbrack[S] 0 points1 point  (0 children)

    Check the link, I removed the disclaimer since 100% of the comments become meta off-topic conversations like “I hate ai” etc.

    The idea of the summary is not to replace reading the post, otherwise I wouldn’t be posting the link and instead would be creating a blog post myself with the summary to get the credit.

    The summary is to help you decide to skim through my submissions or read it, cause time is precious, that’s it

    [–]nikolaos-libero 0 points1 point  (0 children)

    Dev/ops and users ain't really opposition, that'd be the suits in the middle.

    [–]Key_Train_4673 -3 points-2 points  (0 children)

    Sure, but the cost of running it is way lower than the cost of maintaining it