![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/fed50129-04e7-4dbc-8f54-4ba5bae58370.png)
This is part of what I love about the Playdate.
This is part of what I love about the Playdate.
Bad code, yes, calling it ‘shit’, no.
Stuff like this is a big part of why software circles are seen as so hostile and unwelcoming to outsiders.
You can be completely clear and frank without resorting to insult, mild though it may be. Just because you and people most like you understand that calling their work ‘shit’ doesn’t reflect on them personally, doesn’t mean it’s not significantly exclusionary.
Now, obviously you can get to know your reports well enough to understand whom would take ‘shit’ well, but that doesn’t mean it’s not generally important to temper criticism with kindness. Kindness never has to mean holding back criticism, just avoiding stooping to insult.
“You’re dumb” is disrespectful, but “your code is shit” isn’t? How does the latter not reasonably imply the former?
Being respectful is taking the time to moderate “your code is shit” to something like “your code is not acceptable”. You might even go a modicum further into kindness with “there are aspects of your code I need you to improve”.
All express the same idea, some will leave the listener more open to internalizing the criticism.
Work Time Fun is a sort of strung-out Wario Ware that I really enjoyed back in the day. If you like minigames, trinkets, and grinding, then check it out.
deleted by creator
What ways do you mean? More than just expert-systems, I’d imagine.
Play dom-jot, hu-mon?
It’s good exercise.
What’s being discussed here is the hiring of engineers rather than consumer choices. Hiring an engineer is absolutely an expression of trust. The business trusts that the engineer will be able to concretely realize abstract business goals, and that they will be able to troubleshoot any deviations.
AI writing code is one thing, but intuitively trusting that an AI will figure out what you want for you and keep things running is a long way off.
The thing with Ruby clusterfucks is you have to go looking for them. Languages with implicit type coercion and loose comparison like PHP and JS have clusterfucks lying in wait for you and it takes concerted effort to avoid them.
What do you mean regarding weird typing?
Ruby gives you all kinds of tools to make clusterfucks, but it’s not hard to keep your hands out of the metaprogramming cookie jar.
But with careful application even fucky features can be put to good use. Like monkey-patching a problematic method to only throw an exception rather than allow accidental misuse. With a nice verbose error message and good testing practices there’s almost no risk.
Ruby’s ===
operator actually serves a useful purpose at least.
Unifont: it looks clean and I love the curly braces.
Of course, but when you don’t know who is a deadly foe, there’s a bit more subtlety than having to be defenseless because you aren’t certain. The risks can never be reduced to zero, and the safety of you and your team can’t be ignored.
At least aiming their phasers while they were unsure would have given them a chance to react once the changeling transformed.
RIP to an OG.
Gentoo: not even once.
It does happen among Esperanto speakers; parents whose common language is Esperanto is a major source of what few native speakers there are.
And the whole human body, brain and all, can run on ~100 watts. Truly astounding.