

“making it unclear why he was shot.”
Palestinians dress as civilians all the time and get shot, but that’s not a mystery.
“making it unclear why he was shot.”
Palestinians dress as civilians all the time and get shot, but that’s not a mystery.
Yes please
Now all we need is governments who want to tackle poverty.
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.
He’s your King, boy!
Could I interest you in some diagonal bracing today?
Running out of cash, Vlad?
It’s the equivalent of a fidget toy. Keeps the noisy part of your brain busy so you can get stuff done.
Same thing happened in Ireland.
Why bother with chocolate at all? Just wrap c4 in a Freddo wrapper.
I can think of no higher honour in this day and age.
Fixed rates are safer, for sure.
But during the pandemic, when rates went to near zero, I was very glad to be on a variable.
Mortgages can change repayments amounts as the central lending rate changes.
We’re in a squeeze in Canada right now because rates went up and a bunch of mortgages are up for renewal. (5-year fixed rate is standard here)
Thank you for the reply.
I’m just getting into these things. And immutability seems like a double edged sword.
I just started using Bazzite. It’s my second attempt at a Linux gaming setup (Pop_OS was first, Bazzite is working out much better).
What made you lean away from Bazzite, if you don’t mind expanding on that?
I’ll bet people said the same thing when Intellisense started suggesting lines completions.
And when errors were highlighted in the code rather than console output.
And when high-level languages started appearing.
I wouldn’t call mine experience a crash, more so my ability to focus starts to slip around 3pm and by the time it’s 7 or so I have real difficulty sitting down to enjoy any past times that take practice.
Pfft. Amateur. I have a grandfathered license from back when it was $100 one-time payment.
Let’s me install on up to 5 machines at the same time