

Friend started dating a guy. Guy would spend a bunch of time over at friends house. Lo and behold, one day we visit and there’s a new bidet that BF ‘bought for friend’.
We all know BF bought for himself.
Friend started dating a guy. Guy would spend a bunch of time over at friends house. Lo and behold, one day we visit and there’s a new bidet that BF ‘bought for friend’.
We all know BF bought for himself.
Honestly I have a meaty endgrain cutting board, and unless it gets wet, I usually leave it alone.
It gets an oil and wax as needed (the colour fades, for example)
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
I had heard Bamboo was resistant to that sort of thing?
(It’s still good advice, more an academic question)
What kind of finish you gonna put on them?
2
An old leather belt and some stropping compound off Amazon to polish the edge from time to time really extends the life of the edge.
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.
Well done, Mr. Freeman!
Project Farm on YouTube regularly puts tool through their paces. Knipex often shows why they cost as much as they do.
100%
Add a lid and Bob’s your mother’s brother.
Big true.
Also, would a smaller saucepan speed things up a bit?
The internet has ruined me to the point I’m looking for either Saddam or Loss.
If we’re looking in a mirror, shouldn’t the name on the door be readable?
Unless they’re sitting in the hallway…
Wait, so I can just damage other people’s property?!
Ranked Choice, please!
Raw Linseed oil can work, though it is still an organic oil and can go rancid.
I (personally) stick to white/food grade mineral oil and finish with a paste made from melting beeswax into warm mineral oil.