Scratch @ DScratch @sh.itjust.works

Posts

1

Comments

373

Joined

2 yr. ago

I do want to commend you on changing your stance and posting about it.

Internet needs more of that plz n tnx.

I don’t miss them, no.

Peak arch nemesis behaviour. Completely demolish their self esteem. S+ tier gameplay.

Or skin tone.

Caught me slipping!

2

If you are open to friendship with this person, then you could still go for a drink. It can be nice to have someone who has experienced similar negative things to talk to.

And if you shine a beam of light through some slits, the banans split.

Ah, but you see the AI let us reduce headcount for full time employees. Reducing the budget for full time salaries.

Now we just spend twice as much on contractors and consultants, but that’s a different budget, so it’s not my problem.

And even then, imagine having to live in this universe 30 more times.

The site doesn’t define what a code smell is, though. It’s just a list of Don’t Do’s.

That’s kind of the nuance I would be hoping for.

Something like:

Code Smells are clues that something is amiss. They are not things that always must be ‘fixed’. You as an engineer will, through experience in your own codebase and reading of others, develop a sense of the harm imparted by and the cost of fixing Code Smells. It is up to you and your team to decide what is best for your codebase and project.

(The rule of 3 formatting was intentional, given the community we’re in)

I think to present rules like this as hard rules, with little explanation and no nuance is harmful to less experienced engineers.

A prime example here is the Duplicated Code one. Which takes an absolute approach to code duplication, even when the book that is referenced highlights the Rule of Three:

    
The Rule of Three
Here’s a guideline Don Roberts gave me: The first time you do something,
you just do it. The second time you do something similar, you wince at the
duplication, but you do the duplicate thing anyway. The third time you do
something similar, you refactor.
Or for those who like baseball: Three strikes, then you refactor.

  

I've seen more junior devs bend over backwards, make their code worse and take twice as long to adhere to some rules that are really more what you'd call guidelines than actual rules.

Sure, try to avoid code duplication, but sometimes duplicating code is better than the wrangling you'd need to do to remove it.

Making extra changes also leaves extra room for bugs to creep in. So now you need to test the place you were working, and anywhere else you touched because of the refactoring.

Like all things programming; It Depends.

Fancy pants. The only time I got online to check my emails was when the travelling bitwarden came around, usually in the spring. Unless the winter was hard and the pass was blocked.

Hey now! Only reading the headline is a tradition on social media!

Well done, Mr. Freeman!

To maintain the status quo.

Name an anime that builds hype better than Ippo.

Difficulty: Impossible

He’s your King, boy!

https://store.steampowered.com/app/2257010/Creeper_World_IXE/

I blasted through the campaign. If it’s anything like 4 I’m expecting 4000 good community levels.