• 0 Posts
  • 59 Comments
Joined 6 months ago
cake
Cake day: December 31st, 2023

help-circle




  • Sir if you will simply fill out this form in triplicate…

    And initial here, and here, provide your SSN#, yes and bank account and a credit card number there, and mother’s maiden name yes, and provide rights to the soul of your first, second, and third-born child…

    Then you are all set! Oh wait, now just watch this advertisement, and this other one here, and this other one here, and also this other one, and we will allow you to save… hey, where are you going?


  • It isn’t just a language, but it is a language - as it eventually gets around to saying, but it starts off by saying that it isn’t, then later corrects itself to say that it is, etc. I feel like the focus of this ignores the historical context of what C was written to be for - at the time there was like Assembly, BASIC, Fortran (?), other long-dead languages like was it A and/or A* or whatever, there was a B language too! (developed by Bell Labs, if Google can be trusted these days), etc. - and C was developed to be better than those. So saying that like it lacks type conversions is very much missing the point - those were not invented yet. A lawn mower also lacks those, but it’s okay bc it doesn’t need them:-) I am probably nit-picking far too many points, I suppose to illustrate that the style of the article became a hindrance to me to read it b/c of those reasons. But thank you for sharing regardless.






  • Assembly was my first language after BASIC - I know I’m weird, and I’m okay with that:-). Tbf it was for a calculator, so simplified. Any language ofc can go off the deep end in terms of complexity, or if you stick to the shallows it can be fairly simple to write a hello world program (though it took me a month to successfully do that for my calculator, learning on my own and with limited time spent on that task:-).


  • For those of us who read developer code better than PO/PM “english”, indeed code is the documentation, or at least can be. Ofc when the code is thousands of lines long, split between multiple files, interacts with networked resources that you’ve never heard of, sending signals that do who knows what downstream, upstream, sidestream, flipstream, or whatever… yeah documentation can be important too:-). Also when the code is in some other language that you don’t know quite as well.

    By “testing” I should clarify that I did not necessarily mean things like user or unit testing - though that stuff has its place too - but rather even more foundational “verify that your code does what it is supposed to do” kind of testing:-). One could argue that that is just straight-up “writing code”, but then too writing documentation could be folded into that as well, e.g. having things like human-readable variable names, Pre & Post conditionals for functions and the like, so it all gets a bit fuzzy here.

    And if we are being pedantic, a “quick call?” could save a month or year’s worth of time “writing code”, to ensure that you know what needs / desires to be done. Likewise, updating Jira could save someone else SOO much time, or even yourself down the line when you wonder about something that was never mentioned. So I assume that OP was not taking this all that seriously, and just joking about “yeah, meetings are less fun than writing code”, and we all ofc have to pile on with our further opinions about what’s fun:-).








  • Similar, except we only budget for half an hour so as it drags on past the first or sometimes even second hour it takes over lunchtime.

    Even when people avoid trying to say anything so as not to drag it out, the mere fact that the meeting is happening means that it will manage to take up the whole block of time and then some.

    Ironically I’m starting to wonder if the solution might be MORE rather than fewer meetings, bc people need SOME time to work it all out, so if there were other more focused ones then all that could go there rather than have to take place in the only meeting it can - where it takes up the time of the entire team.


  • It absolutely is imho. Like at some point it was not social media as it became later, following (well, attempting to) the financial success of Facebook and Twitter/X, and instead people could submit long-form answers to questions, rather than merely vomit their feelings into the never-ending stream of others doing the same.

    ^This

    I also choose this guy’s wife

    And my bow

    etc.

    By deprioritizing people finding answers and instead encouraging them to make new posts all on their own to ask the question yet again, over & over, spez tried to make money and enshittified Reddit by taking it away from its original purpose that had given it such a reputation for being great.

    So it’s not “having ads” that destroyed it, but the chasing after ad revenue at all costs that was driving it into the dirt. Even before the protests revealed that starkly to us all that the Reddit we had known and use to love was dead - spez had stolen it, he took our efforts and that ad-bloated, authoritatian-modded corpse was what was leftover. And it wasn’t even bc of profits alone, but greed in chasing short-term profits above all else, including long-term profits. Aka capitalism killed it.