Oh for chrisakes. I also donate to The Wikimedia Foundation, feeling secure in the knowledge that at least I could feel good about that one. Time to do some reading I guess.
Oh for chrisakes. I also donate to The Wikimedia Foundation, feeling secure in the knowledge that at least I could feel good about that one. Time to do some reading I guess.
Ugh, poor error reporting is such a frustrating time sink.
Completely agree! It’s SO much easier to lighten the mood and keep things upbeat and productive in an actual conversation vs. just text-based feedback. For example it makes it easy to throw in self-deprecating anecdotes of your own when discussing mistakes / needed changes, which can really help put juniors at ease. It’s just worlds better in >90% of scenarios.
I really wonder about this too. If Russia destroys those undersea cables, would that get a direct response? I would like to think so, because that’s a planet-scale disruption (I think?), but it really depends on the people in charge of the countries involved and their stomach for violence and escalation.
I’m passionate about minimizing war and I seriously hope we never fire nukes at each other again. But a country willing to inflict global damage as a kind of tantrum over their failures in a conflict they single-handedly started…I mean, we can’t tolerate that as a species. There’s gotta be a line somewhere.
Completely understand the frustration here. Mistakes happen, even competent people sincerely trying to do a good job can overlook things, etc. But if it’s a pattern of just copying and pasting code without really even trying to understand what it does, that’s a big problem that needs to be addressed. And frankly they should feel embarrassed if it happens more than once or twice.
OTOH, delivering criticism in a way that winds up productive for all involved is difficult at best, and the outcome depends on the junior as much as it does the senior. What good is being right if it ultimately just alienates you from your team? Tough situation for sure, and one of the many reasons it’s so important to hire carefully (which is itself a whole huge can of worms too!).
Can you simply ask them to walk through their submission line by line with you, explaining what it’s doing? If you’ve never asked that before it might come across as a strange request, but if you phrase it well it’s possible this causes them to notice their poor understanding without you ever seeming to point it out.
I was simply pleased by your comment, to see how much you care about helping folks and moving the community forward. Seems like quite a lot of effort to me, far more than I’d be able (willing?) to contribute, and I’m just forever grateful for folks you like you and wanted to say something about it :)
I appreciate the invite. I’m not at a point currently where I can put sincere effort toward much that’s non-essential, but if that changes, Rust is on my short list of targets for ways to spend some spare effort and time.
Welp, YOU’RE frickin cool, kudos!
Just make sure you’re getting some outside feedback on that, I’ve known folks so used to their own “brand” that they just couldn’t tell. Smelled utterly rank and couldn’t be convinced of it.
What! That’s awesome, what a cool idea.
That’s true and a great example of what my industry needs.
To make an analogy, in the software industry we call 7 different knee-like things “knees”. Not to be confused with the product, Knee, which is also knee-like, but due to its name either pollutes the search results for other knees OR can literally not be searched, and is only a very specific case of knee anyway!
I do plenty of technical writing just documenting software I write, and that’s definitely what has me pining for something a little more prescriptive. Even just reordering some words can suggest different meanings and it’s very difficult to step outside my own understanding of what I’m writing about to see it with “fresh eyes”, how someone else may interpret it.
I have to acknowledge that legalese does meet the criteria! Someone else mentioned that too. It feels very far off from what I had in mind though. Maybe just because I don’t speak it fluently!
I completely agree that Git has some great use cases outside software, and I like the one you suggested. If git is a bidet, random untracked edits (by anyone with access!) to documents are the TP we should have left behind as a society by now.
Yeah that’s fair, and it was clear to me from the jump that it’s an unrealistic desire.
Holy shit. My life is a lie?!
Thank you for fighting the good fight.
I wish we had a dialect or subset of English that was intended to be more like computer code, and would be used for precisely specifying things. I have no idea how we’d do such a thing, and it’d never be adopted (and probably it’s been tried!). But trying to write English in a way that can’t be misinterpreted can be a real chore.
My pedantic hill to die on is the word “jealous”. For example:
“I’m going on vacation!” “Ugh, I’m so jealous!”
No, that’s envy. Jealousy is a weird way of behaving about things you already have, it’s not wishing you had what someone else does! Weirdly, explaining this does not cause people to use the correct word. At this point the battle is probably lost and the meaning has officially shifted.
I write myself little lists of tasks, even when I’m entirely clear on what needs to be done. It may not feel like a hack, but it sure works like one for me - it’s a simple habit that makes a dramatic impact on the flow of my day.
Advantages I notice:
I dunno, really feels silly that it makes such a big difference, but here we are. I don’t do it every day by any means (overdoing it “roboticizes” life to an unpleasant degree), but I use it most work days at least, and sometimes to keep up with chores and personal life stuff when I get real busy.
Analog Zettelkasten! You’re rad.
Self-hosting isn’t some silver bullet. Poorly self-hosted stuff is way less secure than large corporate cloud-based services. There are very few organizations that can successfully craft a secure IT environment for themselves.