"Can our app work from 8am to 9pm, Monday to Friday?"
"Yes but it's an app, it can run 24 hours a day, 7 days a week."
"Oh... Is it possible to make it work only from 8am to 9pm Monday to Friday? They're our opening times and we want everything consistent!"

Slippery slope, a very slippery slope...

Ah yes, Brave, the browser that "respects your privacy" has started putting ads directly *in* the browser.

When they introduced Brave Rewards and people were confused why I was upset, it's because I knew it was a slippery slope to toward this sort of thing.

EDIT: Turns out, the ad is targeted towards LGBT people. As an LGBT person who just wants to live life in peace, this shit aggravates me even more. First, corporations are not your friends. They do not care about you. It's virtue signalling. Second, it's a bit ironic seeing as how Brenden Eich made Brave. If you don't already know, Brenden Eich (also creator of javascript) is pretty anti-gay.

So many things wrong with this. Can't wait to stop leasing away my devices' resources to advertisers.

When i'm in a coffe-shop, i always have the same thoughts:

"Hello, friend.
Hello, friend?
That's lame.
Maybe I should give you a name, but that's a slippery slope.
You're only in my head."

Title: The problem with "good enough" code

Body:

I'm a software developer, and I've seen my fair share of "good enough" code. You know the kind of code I'm talking about: it works, but it's not pretty, and it's not very maintainable.

The problem with "good enough" code is that it's a slippery slope. Once you start writing "good enough" code, it's easy to fall into the trap of always taking the easy way out.

Before you know it, your code is a mess of hacks and workarounds. It's hard to understand, it's hard to maintain, and it's a nightmare to debug.

I've seen projects go down in flames because of "good enough" code. The code was so bad that it was impossible to fix, and the project had to be scrapped.

I'm not saying that you should never write "good enough" code. Sometimes, you just need to get something working, and you don't have the time or resources to do it perfectly.

But if you're going to write "good enough" code, you need to be aware of the risks. And you need to make sure that you're only writing "good enough" code for a short period of time.

Once you have a working prototype, you need to start refactoring your code and making it better. You need to make it more readable, more maintainable, and more testable.

If you don't, you'll eventually regret it. Your code will become a liability, and it will hold you back.

So next time you're tempted to write "good enough" code, think twice. It might save you some time in the short term, but it will cost you in the long run.

If it’s a personal project, I’ll put it off for a while and do something else to switch things up - I might work on a different project for a day and then pick the first one up again.

If it’s a work project, I can’t naturally put it down, but I might just drop it for a shorter period of time, like a minute or two. Get up, take a walk, refresh my thoughts.

This may of course be a slippery slope for some, but for me it’s proven effective in juggling my projects.

New day. New legacy project that needs triage.

The project has existed since before 2000 so it all "works" and has no known business logic bugs. It does however have performance issues which sure I can have a look. It can actually be quite fun and rewarding to optimize performance.

This is a titanic dotnet framework leviathan consisting of over 12,000 cs files using razorpages, entity framework, and... nhibernate? I have my gripes with both EF and NH but they are both fine if used correctly, like any other tool. I've never seen them used together however.

As It Turns Out™, NH was implemented first and at a time when NH did not support async operations. It made sense if you look it up and it's meant to delegate commands via a separate layer, but different story.

Then for... reasons... EF came in and gradually took over.

Because of the way this is all set up, everything will faceplant if you try doing anything async, even if it has nothing to do with calling the db. Any attempt in making this work leads you down a slippery slope of having to rewrite the entire thing, which is out of the question in terms of their budget and expectations.

Sometimes it's a detriment when it works in spite of its issues.

So, the internet is over. Just in case you didn’t notice. If you post a link to anything that involves you: an article, a podcast, a thing you built, a video you made - then mods and admins and trolls get their pitchforks and ban you or roast you or delete you.

This is not the way.

Not only are the walled gardens of apple, Twitter, Facebook/Instagram, breaking the web into little areas - and marketing is buying your time - but we’re doing it to ourselves too.

I can’t post a video about some of my favorite programming books in
/learnprogramming or I’m immediately banned!? Every link that takes people away from your ad dollars is ‘spam?’ Without any useful discourse and content - then why would anyone be there in the first place.

One time I posted a link HERE about how people could get CSS help in the CSS discord and I got fire-stormed for self-promotion. Really? Hundreds of hours helping people learn programming - for free... is my self promotion? Is everyone so insecure that they can’t allow anyone else to talk about their work? It’s super scary.

This is how you control people. This is Nazi shit. It’s a slippery Slope. Watch out.

And whatever you do... don’t share links to your things. That is NOT what the internet was made for.

Do you ever procrastinate getting into a project, at any phase, starting, mid code updates, etc,,, knowing it is not only going to take you time to get your head back into it, but you also know that once you do, and hopefully yes you get into a groove, that it requires a mental time commitment... that last word, commitment, I'm not quite sure if I'm ready to get into, commit to just yet, so, I start procrastinating by doing a whole list of small stuff I need to finish first, because god knows when I get into this thing, I won't be able to jump out and do anything else easily... and then let's say all that goes well,,, small stuff done, I've procrastinated long enough, now I'm ready to drive in, OK, here we go, 5 minutes of reacclimating myself, and someone walks in, wants my attention, which I can't give them, I've already started down this slippery slope... and somehow I come off rude if I don't acknowledge them....aaaggghhh...!