"If you just want JSON over HTTP with some status codes"

yes this

Qualifier: have not been able to use graphql yet, and I'd still like to try it out at least before making and judgements

GraphQL costs a lot more to do, but also gives you a lot more.

Just some benefits we've seen:

- Automatic codegen in the client removes a lot of boilerplate.

- Verification of schemas in CI makes sure we don't "go backwards" on the API inadvertently.

- Documentation tooling that makes it easy to show API structure.

- Easy to generate schemas automatically from underlying data models in the backend service (database tables, ORM models, enums, etc).

- Great type safety compared to JSON over HTTP.

see this is why i browse under 'new' sometimes

:D

The day EA killed Westwood Chat and it's active community and replaced it with their hideous in-game matchmaking was I think the day the internet stopped being fun and weird for me.

Or I maybe just lost my internet innocence, seeing Big Game come in and decide on a whim to toss in the bin the place where I spent most of my after school time. Also where I learned how to un-ban myself by editing the right registry key. :D

I wouldn't give our leaders that much credit.

I'm exclusively a Linux user these days, have been for ~4-5 years. Photoshop CC, for my wife's anniversary gift was the last time I used Windows because I had to, that was ~4 years ago.

I'm 100% for FOSS, I support it, I'm happy to donate to it, but honestly there aren't always FOSS tools that can replace what's out there.

I honestly tried using GIMP to do the work I needed, but have you tried using GIMP circa 2015 on a 4K display? It's unusable. Even without the scaling issues it's harder to use than CC, and I'd additionally had experience with PS previously.

Further, the IDE I use every day for my work (on Linux), is second to none, and there is simply nothing comparable in the FOSS space (I've tried many options); If I want to be productive, I _must_ use this IDE.

I'd love if we could get more money into FOSS projects to make them first-class citizens, and I'm trying to do my part, I just don't know that it's an easy problem to solve.

I have experience with both PS and GIMP, and for simple tasks they are pretty much the same. Actually PS does some things in a slightly less intuitive way.

The strong points of PS are a better optimization of some common professional workflows, and the plugin ecosystem... which most people using it just once or twice a year don't need.

Couldn't help but wonder what role the union played in the recent GM plant harassment case.

They're gonna hang a noose and GM is still too scared/unable to fire them? Am I misreading this?

But also can easily also see how merit based promotion at a production plant would be used to work workers to the bone. Gotta be some kind of balance.

Roughly speaking, one less place where we need to use lodash.

"or will it just obfuscate bugs in the long run?"

Probably. :shrug emojii:

But more stable in the sense of turning hard crashes into UI quirks.

Promotion at Google does not mean management.

Specifically, there are two job ladders in this area, one for management and one for engineering. People are welcome to switch ladders, though there's some friction in the process because they actually are different jobs. The idea is that people shouldn't sacrifice talents to progress in their careers, as often happens when talented engineers are pushed into people management at other companies.

Like a lot of jobs in tech, there is overlap. Managers can write code, and senior engineers can manage people if they want. Everyone needs at least some technical skills, and everyone needs at least some people skills. But the intent is to provide a good long-term path for people who want to focus more on one or the other.

That is true, but what's also true is that it's _way_ easier to get promoted beyond L5 as a manager, and darn near impossible to get promoted beyond L6 as an IC. Google values managers more, just like any other company. That's why you see like 7 layers of management there by now and directors reporting to directors and VPs reporting to VPs: people want more money but can't get to the next level as ICs. Fun fact: when I left Google, I was 1 level deeper in the hierarchy than I've ever been at Microsoft, a company that at the time I left was twice the size of Google I left 7 years later.

I wouldn't say it's easier to get promoted in the sense that the work is easier. A company with 85,000 employees needs a lot of managers (who themselves need managers, and so on), so there's definitely demand. But that demand need not change the stringency of the job requirements.

Google could let half its managers go tomorrow and things would only improve. And you know it, even if you are a manager. :-)

If Google could distinguish between smart people and useless people, why keep the useless people?

I guess i should clarify. Useless in a technical sense, not in a bureaucratic sense. You still need them of course.

And I'm sure even the worst at google are far from 'useless.' Figure of speech.

Edit: Possibly better than the alternative overall though. So frustrating to have competent people promoted as you're trying to put out a working product. Cancel those meetings and fix this code!

But just to be clear for when this comment gets mined by some future HR department. It is of course very important to have good people making the high level architectural decisions, and you should absolutely hire me for your senior technical positions to maximize the output of all those around me!

It's just the whole needing to give blunt assessments of underlings that may have consequences for their and their families livelihood that I'm not suited for.

but still, if you want to measure that then play a turn based game. if i could micro as good as the pros i'd be pretty damn good too.

hooking it up to a camera looking at a screen and a robot arm with a mouse would be more fair though.

edit: ok they did have a camera version, but i still want a robot arm.

how about a foldable small phone?

We’ll see if anybody can make one that doesn’t have a compromised user experience.

Even so, people who like small phones would complain that the screen is too big to use one-handed when the thing is unfolded.