jmoiron plays the blues

@jmoiron This has manifested mostly as a knack for building the right sized thing, and I wouldn't build our current tech for the company we were back then. That sounds ridiculous to me. And that's what we've done as an industry by defaulting to all these internet scale technologies.

@jmoiron As someone who played a significant engineering role at a company from full-co single-room standups to a successful IPO, I've learned a lot about scaling an org, scaling a tech stack, and the requirements of a company at many different stages of development.

@jmoiron This widespread adoption is good for big tech cos, because their scale required them to operate in a completely different technological universe from the rest of the industry. How can you bridge that gap? Export your engineering culture as "the way."

@jmoiron To paraphrase an old one from @benji_smith: "Nobody really buys hammers anymore, they're kind of obselete... What you need is a hammer factory." https://t.co/SGwUpfYKBk "Nobody really does platforms anymore, what you need is a platform platform." https://t.co/s8mcTkh5n2

@jmoiron We shouldn't passive voice "tech became complex", it was made that way on purpose. Loads of X-faang + conference circuit + devrel convinced everyone that YGNI, and with the smart money bought in, everyone else jumped board.

@jmoiron @elithrar tbh black sesame milk sounds like it would be delicious 🤔

@jmoiron @elithrar what, you don't want black milk?

@jmoiron @RayS @BenThePCGuy @Microsoft Consolas

@jmoiron In this new starship troopers game, you play as the fascists? Is this a "spec ops:the line" situation?

@jmoiron @JoelBarciauskas well, serious answer, if it really collapses, one or more things will fill that niche and i'll probably be on at least one of them :)

@jmoiron @RayS It's where millenials go to find their pogs or whatever

@jmoiron If things go south, I am incredibly googleable.

@jmoiron @phil_eaton "If you’re thinking without writing, you only think you’re thinking." https://t.co/8kxqWOnWuM

@jmoiron When IBM, HP et. al tried to sell us on CORBA/UML/SOAP/WSDL etc in the early 2000s, we were like "lol nope" and built everything with REST+json, but now FAANG evangelize internal practices that scale down poorly to small orgs and people think "yes this is the right way." https://...

@jmoiron @copyconstruct Everyone wants to know what differentiates staff/principal engs, and an huge amount of it is "good engineers who also understand how people and organizations work."

@jmoiron @simonw @oneunderscore__ Makes this aspect of NFT profile pics seem even more troublesome, since verification status was the backstop. https://t.co/Hd4wpzepCw

@jmoiron This explains why Google has such a great reputation for product development compared to Apple. https://t.co/X70Qy1PNch

@jmoiron As an Engineer, I know that every time you look at an unfamiliar but sophisticated system, your first reaction is "this is 10x more complex than it needs to be, we could get rid of half of it", and I can tell you that this reaction is always wrong.

@jmoiron @copyconstruct Other than thinking this was obvious based on my timeline, my first thoughts were that they missed a favorable IPO market 3-4y ago when they were clearly "ready" if they wanted to raise, and not being sure if that would have made this better or worse.

@jmoiron @MarcJBrooker No, this is exactly it. A lot of backends can handle some nominal shuffling in the temporal order semantically but are actually relying on this order for throughput, eg. to run compactions less frequently.

@jmoiron When queue transit latency is very low, LIFO will produce load that loosely approximates FIFO. This can be a metastable state, as your goodput may be higher in FIFO-ish circumstances, when requests are roughly ordered, than during a LIFO catchup. https://t.co/OSNlovzWNc

@jmoiron Definitely a response to something in #yorkville. Something related to the construction site on 84th and 2nd maybe? https://t.co/RMS7kzSggX

@jmoiron naming a service: day 1: this only does x, so we will call it xer day 180: xer is the natural place for y.. fine, lets add it day 365: x is actually a multi-stage pipeline, so we pulled out half of x into xworker day 730: oh, yeah, for historical reasons "xer" is where we do y

@jmoiron @jkupferman A version of this is the "climate accord", which is a meeting whose result is the an agreement on when to have a followup meeting where you will address the problem at hand.

@jmoiron "git add <dir>" should require --force and do a sleep 30 to discourage people from using it