SEGA has lost it's shine over the years, but IMO they are the greatest game company of all time. Their arcade output was STELLAR, their game dev teams were the most elite all through the mid 00's.

Seriously, look at their list of output. Just banger after banger. Not to mention their arcade hardware was top notch and was widely adopted.

Rest in peace David! Thank you!

They do what Nintendon't!

Even though I haven't liked a lot by Sega in quite awhile, I really respect at how amenable they seem to be with fan projects, so much so that they hired one of the biggest Sonic hackers (Christian Whitehead) to make Sonic Mania. I'm sure Sega is aware of most of the fan projects (e.g. Sonic Robo Blast 2), and they seem to be somewhere between "not caring" and "supportive", which is pretty cool.

Sega also embraced emulation pretty early. I remember as a kid I had "Sega Smash Pack" on my PC, which used Kega Fusion, and on Steam I have "Sega Mega Drive & Genesis Classics", which is using vanilla Genesis ROMs that I believe you can load in virtually any emulator.

Compare this to Nintendo, who took down stuff like AM2R, and multiple Switch emulators.

My parents made me do everything, and were so fucking mean about everything, I ended up missing out on the things I actually enjoyed b/c I didn't want yet another thing to get yelled at about.

Specific: guitar and music

To be fair: part of it was to be rid of me and to not have to watch me.

Beauty pagents? Go take a good long look in the mirror. That is pathetic. Is that what you want your kids to value? Passivity? Whatever the fuck beauty pagents encourage?

At least dance is a skill.

reads like an edgy high-schooler jerking off at how much better they are than everyone else.

Its like reading Rick Rubin from a loser whose opinions I don't value at all.

Hicks with overpriced trucks don't want EVs, shocker!

They are a status symbol for middle class workers with no taste

Alternatively, they are the most versatile vehicle on the road. But kids on HN have real trouble seeing outside their tiny bubble.

I don't care how it is done just dont rely on your database schema for data modeling and business logic

"Age Gated"?? minnesota and wisconsin are trying to ban VPNs!

I would honestly not mind 2-3 days a week but PDX is dead for tech jobs, and the pay is trash.

Can't wait to have to move to SF and pay 5k for a shoebox so I can work in an overcrowded office in a boring, crappy part of town.

Yea! Start over my career, work way longer and harder hours, and make 1/3 of what I currently do! Sounds great!

The one thing I would like to preserve from microservices is stuff about database table hygiene.

Large, shared database tables have been a huge issue in the last few jobs that I have had, and they are incredibly labor intensive to fix.

In my experience basically everything being good in software is downstream of good data modelling.

It's partly why I've realised more over time that learning computer science fundamentals actually ends up being super valuable.

I'm not talking about anything particularly deep either, just the very fundamentals you might come across in year one or two of a degree.

It sort of hooks back in over time as you discover that these people decades ago really got it and all you're really doing as a software engineer is rediscovering these lessons yourself, basically by thinking there's a better way, trying it, seeing it's not better, but noticing the fundamentals that are either being encouraged or violated and pulling just those back out into a simpler model.

I feel like that's mostly what's happened with the swing over into microservices and the swing back into monoliths, pulling some of the fundamentals encouraged by microservices back into monolith land but discarding all the other complexities that don't add anything.

I learned this early and as a result I'm the guy who's trying to clean up other people's crap while they ship features and get promoted

I feel that if you have multiple sets of application logic that need to access the same data, there should be an internal API between them and the database that keeps that access to spec.

Only allow clients to execute stored procedures?

That could certainly be one way to handle it, if your specific problem domain supports that logic being in stored procedures.

A databases is a global variable in disguise.

Heh, split databases is the thing I think is most problematic and the first thing I would eliminate in most microservices architectures. A huge fraction of the problems of microservices come from trying to split the data model along team structure / service domain rather than the true application / underlying business domain. It doesn't mean you shouldn't have multiple database, just the concept of splitting them arbitrarily along service lines is a huge cause of friction / impedance mismatch / overhead.

I actually like close to a full microservice architecture model, once you allow them all to share the database (possibly through a shared API layer).

Why big orgs use microservices: makes teams focused on a clear problem domain

Why small orgs use microservices: makes it nearly physically impossible to do certain classes of dumb shit