kdazzle

Would this be like an alternative to Delta? Am I thinking about that right?

Ha, I’ve heard a few Dutch say that American style racism didnt really apply to them, but then later they say that some person isn’t Dutch because they aren’t white. All in the workplace.

I think it’s just not as top of mind in other places, but its there.

Lol yeah. My old team had oncall pages in the middle of the night pretty often where nothing was actually the matter. My manager was only nominally on call. In the handoff meetings every week he was basically just like “that sucks”.

Thats cool - I’ll give it a shot with Go after I get over my PTSD.

API development on lambda has to be the worst devex I’ve ever had. Not sure if it was cuz we were also using Dynamo, a half-baked JS framework, or cuz we had wacky internal requirements pushed down (one ex: live-live multi-region deployments for our 0 users!)

Maybe you’ve figured it out, but the local dev flow seemed pretty hacky/nonexistent. It also got expensive with real traffic

Django with DRF will get you a very maintainable API, and you can have as little or as much boilerplate as you want. For example, you can inherit all of the model’s fields, or you can choose to specify them all, or somewhere in between, add additional fields, etc. You can have it generate pagination or certain filters. It’s got plenty of hooks for overriding functionality.

If you see performance issues or situations where youre hitting the n+1 query issue, you can optimize by using the orm’s prefetch_related, select_related, or just drop into raw sql.

Im obviously a fanperson, but have yet to find a framework combo that I like more than those two. It’s not very fashionable, but you’ll end up with an app thats quick to develop and thats reasonably secure by default.

I’m with you. If everything has to be consistent all the time, then nothing evolves.

“There’s a product manager sitting out there who just had a mediocre idea for some new feature. What happens?”

I used to agree, but there’s so much software that is just so bad. Wrong DB, bad framework, crazy abstractions, black box magic, no security, behavior that is just wrong, etc.

The dev team going away for 3 months to rewrite is probably a bad idea, though. There are definitely good ways to rewrite and then not good ways.

You mean the definition of factoid (noun) isnt: little facty?!

I think teammates would have enough context of each others’ positions that they could play the part if necessary, even if theyre not as good. They might even appreciate the skills gaps. So I think sports holds.

My favorite factoid is that Windows desktop Outlook uses the MS Word engine to render emails. If regular emails are caveman html (which they are), then I don't know what that makes Outlook html.

It would actually probably be pretty helpful if the designers knew their way around the production code, since they'd have a lot more context about what is going to be easy/hard to do. They won't be in some design vacuum.

Silo-ing off code because someone isn't a "software engineer" also feels kind of funny to me.

For one, Snowflake is expensive (you pay for the convenience and simplicity) and the data in there is usually stored in S3 buckets that Snowflake owns (and they dont pass along any discounts that they get from AWS for the cost of that storage).

I think the universal agreement is actually to measure things in football fields

Enterprise software is just a shadow of the ideal software

Plus managed kafka is pretty expensive

Presumably those tractors wouldn't be connecting directly to the db though. Not sure why they dont just go the standard iot events route and store data in a data lake and propagate into an analytics db/warehouse from there. Add a layer to make recent events available immediately.

S3 is relatively cheap.

This sounds awful. An IQ test (and needing to prep for one)? Failing an interview based on a bad DB timeout answer? shudder

Dat you, David Cameron?

Just wait until more jobs are outsourced to Canada - there won’t be any difference

DRF is also great because it allows flexibility when you dont want the API to mirror the DB, which is a lot of the time.

Nice. The two-way syncs are where all the complexity lies, and why people end up paying the big bucks to like Mulesoft.

Someone was like: “Bro is this even tape?” And 3M was like “oh shit”

> never reads your entire emails

That’s basically every executive, or most managers, so only lead with the most important bullets and put details way at the bottom

Azure actually had a nice Heroku-like service that served me well for a couple years. I forget what it’s called, but it’s probably the one reason I’d ever consider choosing Azure if that was ever my call to make.

> The whole concept of a counterculture is gone. The closest thing we have to a counterculture in the US today is the MAGA/militia/Q-Anon movement.

You're probably just getting old

I don’t know about this. I do think people tend to prematurely optimize by over-generalizing their APIs instead of building what they need. But this seems like it swings too far the other way.

Remember Evernote had those physical notebooks where you could write in them with real pens and pay the subscription and then take a picture and upload them with OCR? That was the only thing I remember that you couldnt get for free.

Man, you know what you can really just mostly ignore when you’re using an ORM?

Injection

If i’m building an app or an API, I will ORM till I die (as long as it’s Django). If I need anything so much as a groupby, though, i will drop right into SQL or create an aggregate table that my ORM can just do a basic SELECT from