Codex

Someone shared this on Mastodon so I’ll just repost my thoughts from there. (Bonus for Lemmy, I was forced to squeeze all my thoughts into 500 characters, so this is the most succinct I’ve been on this site!)

Pretty incredible how little people seem to understand these. For one thing, every method other than waterfall is a subtype of agile methodology. The major distinction is that waterfall has a series of phases from design through building, testing, and delivery that attempts to plan the whole project up front. Agile methods focus on smaller iteration cycles with frequent, partial deliverables.

Something like kanban is designed for continuous delivery: we want to go to mars weekly.

LEAN development is a scam though, that one is accurate.

Shrödinger’s Roll

They say there are no asexuals in fox holes

Everybody… Get! In! Line!

I feel like this has truly earned a “bazinga!”

I never I realized I was so evil, nor so neutral.

You seem like a person who wants to try and do well and be a good manager. So be very careful of burnout, because the constant tension between doing what is right for your team and meeting upper-management expectations can drive you crazy. It did me anyway, which is why I don’t manage anymore.

Take regular vacations and actually disconnect from work when you do. Try to do the same for at least 1 or 2 weekends per month. Being organized is important and helps with the job and the burnout, but there’s a thin line between “keeping notes in Obsidian keeps me focused” and “my entire 2nd job is now maintaining Jira tickets.”

Organization is for you, keep it for you, and don’t let your organizing become a part of your “public api” or else it’ll become another avenue for status updates that you’re obliged to maintain. Turning your notes and private charts into data for upper management is why you compile special reports, just for them.

Me who just cook her dinner AND likes to go down for dessert! ( ͡° ͜ʖ ͡°)

I made a static site with Hexo a few years back. I thankfully didn’t make any “Get started with Hexo” posts but I did only really use it for a few months. I think that puts me in the cluster with the “switch from Jekyll to Hugo” people. Now it just sits there, absorbing some money every two years for the “personal website tax”.

Shame too, I constantly think I need to get back to it. Hexo is nice, popular with Chinese users I think. I don’t recall now why I liked it over Jekyll or Hugo, but I’ve always loved an underdog. Once I got the hang of using it, it was very customizable and fun to work with.

Oh is this why Biden is suddenly cracking down on immigration and wanting to build the wall too? I had assumed it was just blatant appeals to the right.

Oui

One world, one gender, one love 💗

I want to upvote the OP for presenting an interesting discussion but downvote them for being wrong. This presents a case for a non-binary voting option.

A singular like button would still only express one portion of my sentiment. A third option could be many things, none are sufficient: a none or 0 or neutral option is effectively not voting, a sideways arrow or maybe state, or mixed state would express indecision or indeterminism rather than mixed feelings.

Therefore, I propose that a second positive-negative axis is required. The addition of these “sideways” arrows allow expressing 2 kinds of sentiment: towards the post content, and towards the poster themselves. I will not specify whether left or right is positive nor will i clarify which axis (x or y) corresponds to which kind of sentiment. I’m sure this undefined behavior will cause no problems.

Here is your composite vote in the new system: ↖️

If there already exists “a binary” then that says there are 2 states. “Non-binary” only means there are not-two-states. This could be unary (there is one kind of thing), trinary (there are now 3 things, the old 2 and new, secret 3rd thing), or really any n-ary set of n distinctly numbered things, so long as there aren’t only exactly 2 of them.

I really enjoyed this game back when, and replayed it a couple of years ago. Very unique RTS mechanics and engine, I’m excited to see this open sourced!

Perimeter had several weird gimmicks. Bases must be built on terrain that has been flattened with a terriforming tool (voxel/heighmap manipulation of the landscape is part of the game.) The titular permiter is an energy shield that you can put up around your entire base. There’s also only 3 basic units, but units can be fused together (and separated back out) to make more advanced units on the fly.

The terraforming-as-war approach is neat and I’ve always been surprised that more games don’t try to incorporate similar mechanics. The multi-units are interesting but to me suffer a similar issue as games with many guns but only one kind of ammo. By the time you’ve decided to switch tactics, you might already be too low on basic units of one type to change into what you need.

Picturing a wimpy sad hand labeled “The Klan” which has been left eternally hanging.

I keep my Obsidian notebooks and several source code repos in syncthing and then have them auto-shared between all my computers and my phone. Its been a great system, all my docs I need are readily available on all my devices with almost no delay and no cloud needed. A little advanced configuration to allow local deletes and I also have all my phone photos backed up this way too.

When I travel, I use my laptop and phone on a little travel router, so they’re always networked together and syncing files. Definitely saved my butt a few times!

But then I decided, I wrote my own solution, a thing of 1,600 lines of code, which is, yeah, it’s like thousands of times less than the competition.

And it works. It’s very popular. … I got 100 emails from people saying that it’s so nice that someone wrote a small piece of software that is robust, does not have dependencies, you know how it works.

But the depressing thing is, some of the security people in the field, they thought it was a lovely challenge to audit my 1,600 lines of code. And they were very welcome to do that, of course. And they found three major vulnerabilities in there.

He makes a ton of excellent points, but the succinct impact of this little example really hit for me. As someone who often rewrites things so that I can both understand and fully trust in what I’m depending on, it’s always good to be reminded that you literally can’t write 500 lines of code without a good chance of introducing a major vulnerability.

The tech stack is so dizzyingly high today, and with so many interlocking parts, it continually amazes me that anything at all functions even in the absence of hostile actors.

Damn, watching the doctor break down almost gave me a sympathy panic attack! Effectively told, well made and acted. A little too real though, haha