It's not the tires that are flat, it's the face of the rims.
6,662 karma · joined December 3, 2010
My heart belongs to Django/Python and Linux, however.
It's not the tires that are flat, it's the face of the rims.
For starters, he's talking about communications within a team, not the whole company. Should all work conversation happen in a single #general channel on slack (or whatever the equivalent is wherever)? Absolutely not.
For a long time my boss was a big proponent of this, and I was against it. However, I'm personally tired of having the same conversation over and over as we realize we need to add more people to it. Or half the team decides on an approach in private, and then someone in the other half sees in the PR immediately that they didn't consider some huge thing and now it's back to the drawing board.
So now, everything should happen in the team's open channel.
Seems like this is the stuff that the economy is built on. The inclusion of "avocado toast" makes me think I know exactly where this guy stands on basically every political issue without looking any deeper into him, though.
> Or it could inflate asset prices as we’ve seen with the $12 trillion from Covid relief.
I'm not an economist (thank God), but there's no way that's what happened here. Asset prices increased due to restricted supply. There's no way that lumber prices tripled in mid 2020 due to "covid relief funds".
Besides, a ton of people were suddenly able to work from home and couldn't go out for fun. That meant saving huge amounts on gas and wear and tear on vehicles (or public transportation) and no more fun nights out to spend money on.
If you are writing view code in DRF, you are probably doing it wrong.
Your kids and your houseguests, that's who!
Why it was so important they be amateurs, I couldn't tell you.
Playing video games feels like progress. It gives you all the satisfaction of a job well done, without actually providing any benefit whatsoever. Finishing a tv or anime series can have this affect as well.
It can be difficult to break free of that and direct energies towards actual productivity.
For instance, I find vuejs to be way simpler as a non-frontend dev, and that's way overkill for what I'm interpreting the OP to want.
Finally I went in, and got "oh, we don't do curbside pickup".
I was already paranoid about it, and now I'll be forever.
As a parent dealing with some of this currently, this isn't entirely how I'd put it.
Roblox is marketed for kids, and claims to have a large number of parental controls, but in fact they either don't work or don't exist. Most parents aren't savvy enough to know they even need to check for that.
Meanwhile, I'm extremely computer literate (a developer even), and have largely banned my kids from the internet, installed multiple blockers and monitors, and my kid still gets to shady places and content. It's f-ing impossible unless you are going to literally watch over their shoulder the whole time, which is wildly unrealistic and frankly immoral once they reach a certain age.
It's exasperating.
Prime is similar to or cheaper than Netflix (depending on your Netflix plan), and yet also includes "free shipping", a selection of free movies, a selection of free books, all the "Prime Gaming" goodies, and a bunch of other stuff.
Netflix, meanwhile, charges you extra for 4k (and by some perspectives, HD).
I dunno, Prime doesn't feel that expensive, even if it is more than Disney+ or HBO.
Then again, there's also a vocal minority who thinks the government should spend as little as possible, and new projects are even worse.
If you are seeing performance gains from removing indexes, then I'm assuming your workload is very heavy on writes/updates compared to reads.
Wow, not a fan.
Everything was poorly documented (both in the actual API and GraphQL itself) and fussy, and required a huge amount of code to get anything done. Nesting and union types were really hard to figure out.
Frankly, the more I used it, the less I liked it.
Is it possible that the API design was bad? Sure. But my googling to figure things out didn't make me think they were doing anything out of the ordinary at all for GraphQL.