The largest benefit of mob programming (or software teaming or ensemble programming) is the continuous knowledge sharing. Instead of trying to figure out context during code reviews or syncs, you do it organically all the time. Developing together builds a tight team where people grow together.

Yeah, and reduces the lottery factor. Much less siloed knowledge banks creating unicorn Subject Matter Experts (SMEs). Lots of SMEs is a security risk.

Nice job! Pretty fun game.

Only improvement ideas I have are for a smoother start for new players:

1. Let the user start the game themselves so that they have a chance to read the rules without a stressful first impression.

2. Use a different label text than "Build your word here" as it sounds like a drag and drop target rather than an output.

I'd argue the value goes up with larger payloads. The tradeoff is ease of use vs efficiency.

Hence my question was about programming rather than engineering. Composition could, for a long time, be a task humans do whereas the components are generated by AI.

They're likely on the hype train, I'll give you that. Doesn't mean next generation won't be doing software engineering completely different from how it's done now.

Of course it will be different. It is different now than it was 10 years ago, even without AI, and it was another flavor of different 10 years before that. Jobs evolve. That doesn't mean that we should be advising people to not learn. Keep learning, and be comfortable adapting as things change.

Lizardking’s stuff is great, e.g. Triton Theme: https://chiptune.app/?q=lizardking

An Es Kew El or A Seakewl Lite

Either way, the name SQLite is not SQL-lite but SQL-ite (think graphite). SQLite is an element of SQLey stuff.

Source: https://youtu.be/Jib2AmRb_rk

I'd link the exact timestamp, but then you might watch less than the entire talk, which would be unfortunate.

For reference: The person in the video pronounces it Ess-Kew-Ell-Ait.

I've pronounced SQL "Es Kew El" for the entirety I've used it and have gotten flak for it before. This "an" makes me feel vindicated.

The title actually surprised me because of that. I would’ve assumed the SQLite team would pronounce it sequelite since es kew el ite is pretty awkward to say.

But the grammar would suggest they do say it by pronouncing each letter of the acronym separately.

I thought it was pronounced "es kew lite", S Q Lite instead of S Q L ite.

I definitely prefer the pronunciation that sounds like a sugar-free beverage additive. "This Java tastes like Rust, would you parse me sum see'kwel-ite?"

I actually googled to check the rules, I didn’t think of the first alternative.

An Ess-Kew-Lite.

squealite

Done well (like here), The Goal like storytelling, is both educational and interesting.

Great work! Mashing up data based on tweets, HN posts and real-world projects (i.e. from GitHub) would be an interesting dimension.

Yeah, I have some ideas about including different data sources. You have to start somewhere, though, and Meetup.com has a nice real-life aspect to it. My best guess would be that Github and HN would add most interesting data from a technology / community popularity and natural language perspective respectively.

Question is: how do you connect a Github repo or a HN post to a specific community? Content based? User based? Topic based? The community detection in the real life Meetup.com network is at the very basis of this and for good reasons, so you'd have to find a way to tie other data to that idea.