• 0 Posts
  • 21 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle




  • That, or you’re met with “why on earth do you want to do that?”

    To be fair, the XY problem is huge in anything coding related. Newbie wants to do X, has a vague and terribly wrong idea about how to do it (Y), then asks how to do Y instead. To give a “correct” answer to Y, assuming the question makes enough sense to have a correct answer, is less helpful than trying more or less tactfully to figure out what the actual goal was.


  • I think I misunderstood lemmyvore a bit, reading some criticism into the Lego metaphor that might not be there.

    To me, “playing with bricks” is exactly how I want a lot of my coding to look. It means you can design and implement the bricks, connectors and overall architecture, and end up with something that makes sense. If running with the metaphor, that ain’t bad, in a world full of random bullshit cobbled together with broken bricks, chewing gum and exposed electrical wire.

    If the whole set is wonky, or people start eating the bricks instead, I suppose there’s bigger worries.

    (Definitely agree on “low code” being one of those worries, though - turns into “please, Jesus Christ, just let me write the actual code instead” remarkably often. I’m a BizTalk survivor and I’m not even sure that was the worst.





  • Ignore it (edit: obviously not for the purposes of the course, which someone helpfully jumped down my throat presuming). A lot of people somehow in charge of teaching coding couldn’t code their way out of a wet paper bag.

    They are in a ton of languages in all kinds of different families for a reason: they are a logical and fairly consistent expression of two fairly consistently logical ways to deal with control flow in the specific case of a loop. Also there’s the switch-case case in C-style languages.

    Now, there are legitimate arguments for avoiding tons of of exotic control flow shenanigans, but if someone doesn’t understand break/continue, then the problem is 100% theirs and nobody should take their advice on anything much, let alone relating to programming.



  • Relational database/RDBMS? It’s because the added complexity was necessary or desirable for some reason - relational databases are pretty good at managing data fairly quickly, often with features to deal with timing issues, concurrency, transactions, security, auditing, replication… They have theory going back decades and are still highly relevant. Same as any other software offering, you sometimes expect it to provide features you can’t, won’t or shouldn’t implement yourself.

    The overhead is likely negligible, or was considered a fair tradeoff, or the database is actually better at its job in the given scenario. Hopefully. Sometimes people really do add shitloads of very unnecessary overhead by mistake, or overengineer their solutions terribly (cause it’s fun)


  • Stupidly bad project we were rushed relentlessly on, because - stop me if you’ve heard this one before - some dimwit promised months’ worth of work “in a couple weeks… by an intern”.

    I made it generally known that this whole thing had a snowball’s chance in Hell of getting done on time with a 4-5-man team, they did not deign to take that opinion on board. In fact, they pretty much twisted our arm into shipping some barely working bullshit, causing them to have to do a buttload of manual correction instead. I hope they’re having fun with that. :>