Chuck Durfee

@neontapir@ruby.social
144 Followers
412 Following
3.8K Posts
I'm based in the Denver, Colorado area. My interests include #scifi, #boardgames, #haiku, #ttrpg, #3dprinting #gardening. I work in #software, including as a #product and #engineering #manager. I coach teams and orgs on #agile, #kanban, and craft topics like #tdd and #ddd. I'm married with #dogs and 7 adult children. He/him. Hablo #español. Spreche #deutsch.
Bloghttps://neontapir.github.io/
BookWyrmneontapir@books.theunseen.city
Chuck Durfee1d ago
mcc1d ago
Occasionally you find a person who's like "I don't agree with either extreme, I want to exist somewhere in the middle" and for some reason, those are the EXACT people who get really angry when you try to say the same thing about gender
Chuck Durfee1d ago
Open Culture (Official)1d ago

1,500 Paintings & Drawings by Vincent van Gogh Have Been Digitized & Put Online.

https://www.openculture.com/2023/06/1500-paintings-drawings-by-vincent-van-gogh-have-been-digitized-put-online.html

Chuck Durfee6d ago
Joy6d ago

I finally saw a Capybara in real life!

Visited the San Diego Zoo, and of course it was snoozing in the shade, next to his buddy, a Tapir!

Life dream realized!

#capybara #dream #zoo #artist

Chuck Durfee6d ago
Nina Kalinina6d ago

Today I was reminded that old online chats offered context awareness for the people online: you knew you won't be a bother to a friend who has a smiley flower as a status; and you knew you might not be getting a quick reply from someone who's Away.

Today I don't even know if my friends are online or not. The messenger apps make the assumption that everyone is online, and if not, they will receive a push notification, and will reply to you as soon as possible. But this assumption is barely true. I bet it makes lives harder, especially for ND people

(Edited for a pixel-perfect screenshot)

Chuck Durfee6d ago
Jonas Wisser6d ago

I don't think there's a high enough concentration of #ttrpg players or yinzers here for this to work, but let's give it a shot:

I'm looking for a D&D (or other scifi or fantasy tabletop game) group in #Pittsburgh to join. I currently DM a biweekly game, but I deeply deeply miss just getting to play.

I'm down to play with literally anyone except MAGA types, though I'd prefer a group with mostly experienced players, and I'm willing to play any class. Hit me up!

#LookingForGroup #LFG #DND #PGH

Chuck DurfeeJun 21
VeeJun 20
Chuck DurfeeJun 21
steve mookie kongJun 21

18 Rules of Software Engineering.

#dev #developer #programmer #software #engineering

Chuck DurfeeJun 21
Julia EvansJun 20

here's the final version of the "redirects cheat sheet" draft I posted a while back!

("The Secret Rules of the Terminal" is finished! 95 beta readers have read it! the copy editor is done! technical review is done! the illustrator has made the cover! It's going to be out on *****Tuesday June 24*****")

Chuck DurfeeJun 21
Police State UKJun 20

"#Meta’s tracking pixel was secretly communicating with Meta’s apps on #Android devices. This violates a fundamental security feature (“sandboxing”) of mobile operating systems that prevents apps from communicating with each other. Meta got around this restriction by exploiting localhost, a feature meant for developer testing. This allowed Meta to create a hidden channel between mobile browser apps and its own apps."

#Privacy #Facebook #Instagram #WhatsApp #Threads

https://www.eff.org/deeplinks/2025/06/protect-yourself-metas-latest-attack-privacy

Protect Yourself From Meta’s Latest Attack on Privacy

The best way to stop this cycle of invasive tracking techniques and patchwork fixes is to ban online behavioral advertising. This would end the practice of targeting ads based on your online activity, removing the primary incentive for companies to track and share your personal data. We need strong federal privacy laws to ensure that you, not Meta, control what information you share online.

Electronic Frontier Foundation
Chuck DurfeeJun 21
Pseudo NymJun 21

What's the leading cause of dry skin?

Towels.

#dadJoke

Apologies if I saw that here on Mastodon some time so. Short term memory is the second thing to go. I don't recall the first.

×
steve mookie kongJun 21

18 Rules of Software Engineering.

#dev #developer #programmer #software #engineering

Show threadSeaFury 🦜🍉Jun 21
@mookie I love how it starts at 0️⃣
Show threadsteve mookie kongJun 21

@SeaFury

Proving the list is legit!

Show threadJason RushJun 21
@mookie That's a pretty solid list!
Show threadKerr Avonsen (she/her)Jun 21
@mookie Here's another list you might like...
"Use the Source, Luke" https://kerravonsen.dreamwidth.org/976693.html
#developer #programmer #programming #SoftwareEngineer #software
kerravonsen | Use The Source, Luke

Show threadFred MoyerJun 21
@mookie when building a framework, keep your resume up to date
Show threadDr Andrew A. Adams #FBPE 🔶Jun 21
@mookie @cmsdengl
AI code suggestion systems follow NONE of these.
Show threadTFed 🍉🌻🚀Jun 21
@mookie 4 and 6 they caught me 
Show threadTFed 🍉🌻🚀Jun 21

@mookie I will document documentation one day, i hope

and actually i'm not using unnecessary dependencies, but i do over-import libraries, i will fix that one day. In nim it's allowed as it imports *only used stuff* before compiling it.

Show threadJared White (🏳️‍⚧️ ally)Jun 21
@mookie
18. There are no rules. Only guidelines…
Show threadElias MårtensonJun 21
@mookie That used to be good rules, but now they've added another one: "18 - Haha, just joking. It's vibe coding now"
Show threadgeraldewJun 21
@mookie I'd prefer 7 to say "constrains arguments" rather than prevents them, but that's probably because I've never seen a coding standard that I'd personally adopt.
Show threadMartinJun 21
@mookie
I would suggest also :
19 Get the spec nailed down
19b Beware feature creep
Show threadMàrtainn D Jun 21
@mookie I would also add “Resolving technical debt takes so much longer than the initial quick and dirty coding took”
Show thread⊥ᵒᵚ⁄Cᵸᵎᶺᵋᶫ∸ᵒᵘ ☑️Jun 21

@mookie it's missing at least one rule :

-1 : beware off by one errors

Show threadyetztJun 21
@mookie coding standards do not prevent arguments. i'm still mad at everyone who thinks two spaces are in any way superior for indentation to tabs.
Show threadSonikkuJun 21

@mookie

Some pertinent points in relation to this at the corporate where I am employed and why I don't want to do it anymore:

5. The problem is that you have poor hiring decisions and their inexperience shows in the "freshly minted graduates" writing garbage

10. These are used to reprimand developers and/or gaslight them

12. Asking for help unleashes a lecture "why are you doing it that way, instead of our way? Where's your documentation, what are you doing during the day here?" and then puts you in a pair-programming setup.

15. Say that to my manager, see how fast you'll get written up or put on a PIP

Show threadpescoJun 21

@mookie

Ich bin der Geist, der stets verneint.

0. You will regret that simplistic design when the real world calls.
1. Nobody takes pride in what they write.
2. Everything is "good enough", there is nothing excellent.
3. Nothing gets made to fit, everything has to come from some "proven framework".
4. The wiki is filled with half-assed bullet points except the bullets are Markdown headings of various sizes.
5. Nothing ever gets fixed properly, only wrapped and worked around.
...

Show threadpescoJun 21
@mookie
6. If it's not supported by the framework, it can't be done.
7. The rigid and overbearing "coding standard" is the subject of recurring arguments at lunch.
8. Commit messages are a swamp of self-righteous overexplanation why the previous code sucked.
9. When the boss decides that something is the new hotness, everyone better play along.
10. Code reviews quickly become a device to establish pecking order.
11. Most code is long-winded boilerplate that The One IDE knows how to refactor.
...
Show threadpescoJun 21

@mookie
12. Two people bog down an entire department by their incessant inability to RTFM.
13. Every "project" that aims to "get to the root" of something immediately devolves into bog standard fire fighting due to some technical or budget constraint.
14. Software is never completed.
15. Estimates are always treated like promises.
16. Every feature gets rushed out the door, the product is never in a coherent state.
17. Nothing. Is. Absolute.

SCNR.
all in good fun. ;)

Show threadWesDymJun 21
@mookie Is there a reason most of these statements aren't closed? Or is this meant to be a cascade list?
Show threadSteffi the RedheadJun 22
@mookie I would add some more like:
18 - don't build fancy stuff, solve the problem
19 - think about security and testing from the beginning
20 - wear your programming socks
Show threadskedarwarriorJun 24

@mookie Microsoft and Redhat disobey this on a monstrous scale.

To be better than them at coding is in this way is to be above water.

Another words, -1 or worse for their methods. 0+ for anything better.

Those two corporations are heinous when it comes to complexity and obscurity.
"Systemd" after all...

dbus too, etc...

And in microsoft's case particularly, "Windows"

Windows btw, is a good name for it, except they don't mention why.

Your OS can be seen from afar by them.

"Windows"

:P