Welp time to spend 3 hours rewatching all the Strongbad emails.

At my job, we have an error code that is similar to this. On the frontend, it’s just like error 123.

But in our internal error logs, it’s because the user submitted their credit card, didnt fully confirm, press back, removed all the items out of their cart, removed their credit card, then found their way back to the submit button through the browser history and attempted to submit without a card or a cart. Nothing would submit and no error was shown, but it was UI error.

It’s super convoluted. And we absolutely wanted to shoot the tester who gave us this use case.

Too real.

We had a consultation last year to better structure our code base to look more like the first picture. Then it slowly evolved back into the second picture.

Haha! Complete opposite.

Giant monorepo that’s delicately balanced and one wrong move can cause the whole thing to flip over.

(Not arguing over what is better. That’s just my life in the past few years, and It’s a stupid argument)

It’s mostly based on what he feels is good.

One of my main issues is, seeing his code in the past decade… It feels like this guy hasn’t coded in a collaborative environment in years.

His personal opinion tends to get on the way with code that’s easier to read from a team perspective. And “Uncle Bob” pushing that as the defacto way to code.

This happens from Influencer types who are so detached from the industry for decades and are no longer aligned with problems real engineers hit.

It’s not that he’s wrong. It’s that his perspective is outdated.

I’m not as much vitriol as others about Clean Code, but I will argue that engineers who preach the book as some sort of scripture are really obnoxious.

I love the Single Responsibility Principle, in theory.

What I don’t like is when devs try to refactor everything to that idea to achieve “Clean Code”. I’ve seen devs over-architect a solution, turning one function into many, because they don’t want to break that rule. Then point to this book as to WHY their code is now 20x longer than it needs to be.

It also doesn’t help that every recommendation about good programming books include this.

It’s like recommending a Fitness book from the 70s - information made sense at the time, but new research has made a lot of the advice questionable.

My main issue is the whole “Uncle Bob” persona. Robert C Martin is sexist and a racist, and has been uninvited by conferences. We don’t need that type of toxicity in the industry.

Is there a article about this I can find more info about this?

It’s a brand new topic for me and I just read this one from a previous comment. And trying to learn more.

Oh that’s super helpful and incredible.

I’m not familiar with that side of Linux as I’m primarily a user. But that’s how our devops pipelines work to ship apps/websites. We’re shopping the entire working package with every update, and rolling back with issues. It’s a fantastic system since as a developer, I can isolate problems.

I never thought about that on a OS level. And I support it!

Sorry I’m too stupid to understand this joke. Someone explain?

Average Linux solution.

“Got an emergency? It’s so EZ. Just open up the terminal and copy/paste [long string of unreadable text]. Btw fuck windows.”

as a chronic documentation reader, the best advice i can give is to document everything Anything that the user can and will potentially interact with, should be extensively documented, including syntax and behavior.

I don’t know about that. I’ve read some terrible documentation that had everything under the sun. Right now in the library I’m using, the documentation has every available class, every single method, what it’s purpose.

But how to actually use the damn thing? I have to look up blog posts and videos. I actually found someone’s website that had notes about various features that are better than the docs.

There’s a delicate balance of signal vs noise.

I used to mock people who make YouTube videos that literally just walk through the documentation. Like bro, get some reading comprehension!

But then when I fumbled with some self hosting tutorials, those YouTube videos were the only thing that made sense, because they’re explaining why and how.

Sorry y’all.

Haha normal setup to run critical systems at a small business

That works?!

Edit: ah I stupidly read NextCloud, which is kinda a resource beast.

It’s a PDF in slideshow format after you give them your email.

Fun story! At a conference, I asked this vendor (the company collapsed now) if I can see their documentation. The obvious sales person made a big stink how it’s only for paid customers and I can see it when I paid.

I told him how stupid it was since his competitors have their docs open.

During a conference’s event where they parade their sponsors, the vendor got on stage and called me out with “And paid customers will have a wealth of support, like developer documentation… Especially for you [name]”.

In my nerd rage, I shouted from the audience “What kind of shit software is afraid to share their developer docs publicly?” I was escorted out by security.

And during the night event when everyone mingles (including sponsors), the guy didn’t show up. And apparently, news got around where by the last day of the event, the entire booth was taken down.

I dunno if it was me shouting and everyone agreeing with me, or the conference realizing that attacking a paid member of the audience wasn’t a good idea and told him to leave.

Either way… Tell it to their faces when their product isn’t dev friendly. These charlatans seem to get bolder and bolder with their garbage.

Actress Millie Bobby Brown, aka Eleven from Stranger Things, revealed when she was still a minor that Drake and her used to text each other. Particularly concerning advice about Drake’s similar experience being a child actor.

In 2018, Drake reportedly dated, then 18 year old model, Bella Harris. However there are posts of them in intimate positions as old as 2016, where she would’ve been 16 years old.

https://www.reddit.com/r/OutOfTheLoop/comments/1c91nnr/comment/l0ikqdf/

https://css-tricks.com/css-database-queries/

1. Use a hand-modified-to-ESM version of SQL.js, which is SQLite in JavaScript.
2. Get a database ready that SQL.js can query.
3. Build a Houdini PaintWorklet that executes queries in JavaScript and paints the results back to the screen in that <canvas>-y way that PaintWorklets do.
4. Pass the query you want to run into the worklet by way of a CSS custom property.

That’s actually a valid skill to know when to tell the AI that it’s wrong.

A few months ago, I had to talk to my juniors to think critically about the shitty code that AI was generating. I was getting sick of clearly copy-pasted code from chatGPT and the junior not knowing what the fuck they were submitting to code review.

Shhh… The poster doesn’t understand CSS and we shouldn’t embarrass them in a community with memes