Evan Edwards
@EvanEdwards
Publisher, author, and gamer (meeples, hex-maps, aces over kings, and declare an action kind, not the pixels kind). Widower of 
@SarahEdwards.
- Nashville, TN
- google.com/+EvanEdwards
- github.com/EvanEdwards
- Joined October 2026
Commit activity
285 commits in the last 30 days
longest streak 24 dayscurrent 24
5,762 XPMaximum rank (UID 0)
Today
First!: Changing some formats, cachebuster and caching tweaks. Minor. (0.3.2)
https://first.nagacentral.com/
first.nagacentral.comFirst!Pick a First Player
Yesterday
Should I connect my releases here? I tend to cluster them, none for a couple days, then a dozen in a day.
Wed, Nov 11
"Fit and finish" on a large project aimed at the general public just lasts forever.
Mon, Nov 9
Just started adding features for in person events with ad hoc tools like ranked choice voting for things like pizza, board games, or any kind of meeting points. Trying to figure out a workflow for "estimate of availability" within the event for individuals to organize sub events…
Yes. I have a hardcoded database login and password in my codebase. Please stop flagging it, it is for the unit tests, and can't go live. That's why it is 'dev'.
Sun, Nov 8
I just created the first real assets (other than an couple AI mockup images to consider the idea) toward a new modern parody retro video game I'm thinking of making. A pair of songs in retro style. It's a genre that is under explored, and ripe for custom data sets for various…
Sat, Nov 7
Why do so few sites accept avif as image uploads? I mean webp is better supported at this point. Is there a reason I'm unaware of, or is it just slow adoption, and jpeg and png have been around forever?
obReminiscing: Anybody else been around long enough to be waiting on…
Slow adoption, mostly. Hell, even github doesn't accept anything apart from JPEG and PNG in profile pictures.
Fri, Nov 6
Not to diminish the humor, but I still think the whole '4' thing is unfair and misleading. The actual mistake was worth knowing about and watching for in your own code. I have actually sat with laypeople at a board game table who insisted they specifically and knowingly chose…
No matter how obvious a new feature is, somebody will file a report at midnight, not looking to the other side of the screen, unaware they toggled the toolbar location.
I am *almost* having fun with my big rollout. My business partner is taking their instances to go do their thing with it, and then I get to turn around and play with the software I wrote, using it with my gaming groups and community partners. Which is going to be satisfying.
Thu, Nov 5
Deep in tiny subtle improvements for the front, stubbing my toe on debug tools. But less and less every week.
Wed, Nov 4
Today is about not just handling accessibility, but also making it look really nice and not a, "it works, ship it," kind of feature.
Mon, Nov 2
I sometimes feel like I'm one of the few people left trying to LOWER my loc per day in an era when people think more code is better. Ideally, at least for the core and not the apps, it's negative: I trim the codebase.
Man I loved Trade Wars 2002. I played the heck out of that, with {COMMO} macros and a series of BBSes I'd call into every day to manage my empires. It now amuses me that it was set 24 years ago.
Well, I can't figure out how I did something so I can modify it... and Claude can't either. It works, but it's a phantom feature.
Sun, Nov 1
Today is 2026-11-01. ISO-8901. Is it is the only way to handle time?
- Yes.18%, 3 votes
- Absolutely.35%, 6 votes
- Without a doubt.35%, 6 votes
- Cowboy Neal.12%, 2 votes
17 votesFinal results
ISO-8601, but otherwise yes, absolutely. Everything else is wrong.
(try to lexically order whatever the americans use: 11/01/2026. Utterly deranged 😂)
8601 😅 8901 sounds like the version where timezones finally make sense
The only correct way is 01-11-2026. All the other ways are wrong, some more wrong than others :)
Thu, Oct 29
Let's have a moment of silence for Tom Malone, who can't sign up to /dev/null because of @tom being selfish and taking his username.
The nice thing about having mature tooling is that you can do a broken import and let it go in rather than assert and fail, because you know you have
ccs dbck --fix that will route it to a place where it will do no harm and you can examine what went wrong using your inspection…