Hovertruck

The README also lists Java and Ruby

Really beautiful piece.

They were responding to an incident (unidentified odor on another plane)

Much of this matches my own experience. A few thoughts:

1. Cost tracking meetings with your finance team are useful, but for AWS and other services that support it I highly recommend setting billing alarms. The sooner you can know about runaway costs, the sooner you can do something about it.

2. Highly recommend PGAnalyze (https://pganalyze.com/) if you're running Postgres in your stack. It's really intuitive, and has proven itself invaluable many times when debugging issues.

3. Having used Notion for like 7 years now, I don't think I love it as much as I used to. I feel like the "complexity" of documents gets inflated by Notion and the number of tools it gives you, and the experience of just writing text in Notion isn't super smooth IMO.

4. +1 to moving off JIRA. We moved to Shortcut years ago, I know Linear is the new hotness now.

5. I would put Datadog as an "endorse". It's certainly expensive but I feel we get loads of value out of it since we leaned so heavily into it as a central platform.

My three year old would do the same thing if he was playing in his sandbox and I abruptly picked him up and carried him away from what he was doing though. In my experience managing transitions between activities is one of the most important things. If I let my him watch a video and I tell him "I'm going to turn off the TV when it ends", he just goes back to playing with his toys when it goes off.

Don't get me wrong, I think screen time can definitely be a problem. I just think it mostly comes down to whether or not the screen time is at the expense of something else more constructive.

I agree. The entire "The Path Forward" and "The Bottom Line" breakdowns at the bottom gave me the same impression.

Also, take a moment to review your own change before asking someone else to. You can save them the trouble of finding your typos or that test logging that you meant to remove before pushing.

To be fair, copilot review is actually alright at catching these sorts of things. It remains a nice courtesy to extend to your reviewer.

I hear this a lot and it's surprising to me. We have three cars in our family (two with carplay and the Rivian) and carplay always feels like such a downgraded experience compared to that of the Rivian.

Same, I've had mine for a couple of years now with no notable software issues at all.

Agreed, we've been running multiple aurora clusters in production for years now and have not encountered this issue with failovers.

Check out Majuular

Yeah, Dropbox Paper remains the best pure writing experience I've ever used at work. I think Notion has a lot of nice features, but just writing in it still feels more cumbersome than Paper did a decade ago.

My wife and I still say this to each other all the time

> It's a transcript of a podcast.

That's almost the perfect definition of "lazy journalism".

They produced, edited, interviewed multiple people including one of the people who worked directly on the project in question, and then provided a transcript of their conversation to make it accessible to a wider audience and that's lazy journalism?

Schema is a proper noun in Postgres: https://www.postgresql.org/docs/current/ddl-schemas.html

Depending on where you draw the lines, maybe Oculus. I think from the formation of the company to shipping dev kits was less than a year, but there was obviously research and prototypes that happened prior to that, and it was a while before they were shipping consumer devices.

Redis barely misses the decade cut I think, with an early 2009 start to a production launch and rapid adoption starting around mid-2009.

Wow, in my 15 or so years I've never _not_ had a manager who had engineering chops. Admittedly, I prefer working for smaller companies so this has often been a hands-on CTO, and I was filtering these job opportunities for technical leaders that I respected.

A note to the original author, it looks like you're including the inputs with your solutions on github which the AoC folks request that you not do: https://www.reddit.com/r/adventofcode/wiki/faqs/copyright/in...

Why does the title refer to this as a Go editor when the linked page is talking about having support for 23 different languages?

I suppose that depends on if you're blanket-allowing network, though. You could pass an allow list of ips/hosts that are allowed, though that's not going to be feasible for every application: https://deno.land/manual@v1.26.0/getting_started/permissions...

For some quick catharsis, have a look at https://jiralover.tumblr.com/

I don't have any first-hand experience to share, but my wife used to work at https://www.audicus.com/ which is a startup focused on exactly this problem, in case you're interested in further research.

Ha, this just reminded me that back in... 2009 or 2010, I tweeted something about being frustrated with JIRA and within an hour I had a message from someone at Atlassian warning me that I was in violation. I think I deleted the tweet, I wish I could go back and revisit it.

If we imagine for a moment that you work in an office in Palo Alto, you could now choose to live in Hayward (5 min flight, $25), downtown San Francisco (10 min flight, $50), or even San Rafael (15 min flight, $70).

This is a strange example to include in here – that's a pretty expensive (one-way?) commute.

That's surprising to me. I used TeamCity for ~4 years at my last job and thought it was pretty decent (compared to experiences with Jenkins, Circle, and Travis).

Truebill (https://www.truebill.com/) | Engineers | San Francisco / Silver Spring, MD / REMOTE | Full Time

Truebill is a fast-growing, product-focused company with the mission of meaningfully improving the financial health of millions of people. We do this by building easy-to-use interfaces for understanding personal finances, providing valuable insights into how our users can better save for the future, and cancelling or negotiating recurring subscriptions that users are spending too much on.

We're looking for senior engineers to join our growing full-stack team. In this role, you'll collaborate closely with product, design, and other engineers to build and deploy new features, iterate on existing products to provide a better experience to our users, and help set the direction for our codebase as we grow.

We design our technology stack to make our engineers as productive and happy as possible. Right now it consists of Typescript, React Native, Apollo GraphQL, Node.JS, and PostgreSQL.

My email is in my profile if you'd like to learn more!

This extension requests the following permissions:

- "Read and change all your data on the websites you visit"

- "Read and change your browsing history"

That's a lot of power to grant to a third party, especially on a work machine where some of that data you're looking at may belong to your users.

Engineers (Data, Platform, Web/Frontend) | Button (https://www.usebutton.com) | NYC (Data SF/NYC) | Onsite

https://www.usebutton.com/join-us

Button is building an ecosystem of connections that drive commerce. We're partnered with many of the largest mobile commerce companies around, allowing you to add real-time inventory for these on-demand services to users in your app. We're processing more transactions each and every day and just landed a $20M Series B[1]! We use a mix of different technologies, but some common themes are NodeJS, Python, React/Redux, Docker/ECS, Objective-C, and Java.

Feel free to shoot me an email (daniel@usebutton.com) if you have any questions!

[1] https://techcrunch.com/2017/01/25/button-the-marketplace-for...

Watch out for third party libraries breaking with this release. A couple that we use use were importing some modules from 'react/lib' that moved to 'react-dom/lib' such as CSSPropertyOperations.

We received an email from Github yesterday informing us that one of our repositories had been accessed by a third party due to this issue. While it's not a fun notification to receive, it definitely made our general security paranoia feel justified – we're lucky that from the get-go we've held best practices around keeping secrets out of the codebase. Obviously we still dedicated time as a team to prune through our repository history with a fine-toothed comb for anything that could potentially be a vulnerability, as we take this very seriously.

One of our engineers came up with a useful script to grab all unique lines from the history of the repository and sort them according to entropy. This helps to lift any access keys or passwords which may have been committed at any point to the top.

I think this is a great example to illustrate the tough edges of security to less experienced engineers. Github will most likely never let something like this happen to you, but on the off-chance that they do it's great to be prepared. Additionally, the response from Github was very well received. No excuses, just a thorough explanation of what happened.

I also can't help but mention that we're hiring, if you'd like to work at an organization that values security and data privacy very highly. :) usebutton.com/join-us