Matt Kuritz

Here's the deck from my talk at @DevOpsDaysPHL speakerdeck.com/mkuritz/how-we…

@Kazanjy dogs pooping isn't an inconvenience, it's part of having a dog whether or not you think it 'makes sense', it sure didn't hinder us in any way, which makes your position these activities are "unacceptable" confounding, if nothing else

To be really clear: 1. Dogs pooping was the inconvenience. 2. Making the business decision to involve dogs in the office makes a lot of sense (including poop) because it's a dogfood company. 3. Making the decision to not have daycare and to knowingly embed a source of recurring distraction into the day without a commensurate positive impact on the business is NOT a good idea.

lol we built farmers dog with dogs running around the office at all times. i stepped away to clean up so many accidents, and none of the dogs were mine.

@Kazanjy to be really clear... 1) dogs are never an inconvenience 2) dogs are in no way 'necessary' to produce software (or run a biz of any kind) dogs, kids, or whatever, people can be productive and perform their role while taking time for 'non-work' tasks during the day.

@Kazanjy i'm a software engineer 🤷‍♂️

💯

Let’s make this a thing! :) I actually just did it at @DevOpsDaysPHL Who’s next?

The first Platform Engineering NY meetup is being planned for June! Have a talk for the community? Reach out to myself, @sudomateo, @clesleycode, or @sfurino

Git is far from ergonomic, but I find it interesting this resonates with so many. Why does this happen? What is the friction to actually learning how it works?

Truth, unfortunately. Also doesn’t matter if you work in tech.

Probably a good time to shout out that we're hiring Senior Engineering Manager Senior Platform Engineer Senior Software Engineer Director of Product Management Group Product Manager, Health Platform Senior Product Manager, Trial & Subscriber Experience #open-positions" target="_blank" rel="nofollow noopener">thefarmersdog.com/careers#open-p…

This was a ton of fun! Got to share a bit how thinking about engineering in terms of platform and product at TFD, among a few other things :)

@thdxr We’ve done it twice already at TFD. Has worked out pretty well. And the first thing was beanstalk 😱

every single person who says "build it using this less capable setup and you can rewrite it later if it succeeds" has never had anything that succeeded

The perks of being a dog person 🧡

Halloween is for the dogs.

I got 3-4 fresh React dramas on my feed right now. Here’s what I suggest we do about it: Shrooms

The difference with hooks and actions is they’re purely convenience. Best to avoid unless your really confident you can establish enforce a correct, strict standard for usage.

Theres a lot of flexible software that lets you hurt yourself. Git, jenkins, k8s are some things that come to mind for me, and they get there share of flack (especially k8s).

Server actions is the frontend version of sequelize hooks. A lot of people are going to find themselves in a world of hurt in a few years.

@AdamRackis @thdxr @t3dotgg Disagree. This could definitely lead to fatal mistakes for startups that take the wrong shortcuts in search of pmf or to cope with early stage growth. The team improves over time with success/funds, but its often a race against the problems from the original naive/shit team.

@thdxr @t3dotgg Aha!!! Selection bias. Consultants only visit shit teams that need consultants. If this startup thing doesn’t work out for you I’d wager you wind up somewhere a lot better than the places you consulted for, with peers who’d be capable of making good use of stuff like this

ok time’s up here’s the deal with server actions if you’re excited about them you’re wrong if you’re mad about them you’re wrong let’s do this unfortunately @t3dotgg was right - the key thing the haters are misunderstanding is that NextJS is a backend framework in your head think about it like express or any other http server - you wouldn’t be surprised if you could return html and do a database call right next to it except it’s a better express because it lets you build all kinds of complex interactive clients via React fundamentally there’s nothing wrong with this - you’ve been doing it forever in every other language, just never with this kind of focus on the frontend bits but sorry nextjs fans you’re wrong too for dismissing people’s worries about “separation of concerns” the only real job you have as a programmer is encapsulation - figuring out what details to hide and what to expose and because this is your one job, of course you’re all terrible at it forcing a hand rolled API layer at least guaranteed some level of thought and blast zone for refactoring with that gone, doing the wrong thing just got a lot easier it’s why in past generations, the frameworks had some encapsulation ideas built in (to varying degrees of being useful) all the acronyms, MVC, MVVM, DDD yes can be overkill but the root ideas exist for a reason asp.net had these ideas baked in, elixir’s phoenix has a tutorial about bounded contexts right at the beginning, PHP only got lambos once Laravel nudged you into a stricter structure are they perfect? no. but they’re a hell of a lot better than whatever you’re about to come up with given that NextJS has no philosophy on this problem at all so a lot of you are about to repeat all the same mistakes we’ve seen a generation ago if you don’t slow down