ayuhito

I have an inkling of a feeling that this generosity is a stunt only to help juice the growth and “story” specifically for the IPO…

Best use the AI subsidies while you can!

That’s exactly it for large scale hiring with finite resources.

It’s all probabilities in the end. And if an LLM gives you more a more relevant pool vs random distribution, that’s still a net benefit.

I think there’s already a big market of supply chain security companies that are proactively scanning dependencies for this sort of thing.

They’re always racing to be the first one to write an article about a case.

At least with our Renovate config, all dependencies have a 7 day cooldown, but marked security updates are immediate.

Attackers can’t push a security update without going through the reporting process (e.g. Github CVE), so they can’t necessarily abuse that easily.

Welcome to becoming a project manager.

> Just do the cutoff when everyone is asleep.

In this age, many smaller companies serve customers across the globe. There is no common “asleep”.

DuckDB has one of my favourite articles on this topic if you want something a little more high level: https://duckdb.org/2022/10/28/lightweight-compression

> My experience with GHA default caches is that it’s absolutely dog slow.

For reference, oven-sh/setup-bun opted to install dependencies from scratch over using GHA caching since the latter was somehow slower.

https://github.com/oven-sh/setup-bun/issues/14#issuecomment-...

I strongly relate to this in many ways.

Because of OSS, I’ve never actually applied for a job or done a Leetcode interview. I’ve gotten multiple direct offers through Twitter DMs (I don’t post) and multiple referrals through random encounters that I never used.

E.g. Debugging an interesting issue with GitHub customer support eventually led to a referral for Microsoft by an MD. Similar stories with Cloudflare and more.

It’s not limited to OSS, but just having any sort of backing credibility to your name without going through the whole CV/CL process unlocks a whole slew of opportunities since people can “pre-screen” you from the start.

I feel it’s an evolution of the term “Devrel” which still feels tacky.

Nor would you want someone who built most of their career as an actual engineer to suddenly drop that term and become a generic someone in “marketing”. They’re more than that for sure.

I quite like the terminology the more I think about it.

https://github.com/aarondfrancis

Also worth checking out libxev[1] by Mitchell Hashimoto. It’s a Zig based event loop (similar to libuv) inspired by Tigerbeetle’s implementation.

[1] https://github.com/mitchellh/libxev

> I'd love to know how much LLM was used to write this if any, and how much effort went into it as well (if it was LLM-assisted.)

Are people supposed to be obligated to post such a report nowadays?

I enjoyed the article and found it really interesting, but seeing these types of comments always kind of puts a damper on it afterwards.

In fact, v1 code usually uses v2 code under the hood, but with different options to maintain backwards compatibility.

You still get performance improvements even if you don’t switch over to the new import!

“Chemicals” are overused as a term for sure, but there is a huge difference between what’s legal in America and Europe that brings a shred of truth to the previous statements.

For example, common ingredients like potassium bromate or ADA are straight up banned in the EU for health concerns.

Reading the ingredient list of American bread is plain shocking at times.

Go also suffers from this form of “subtle coloring”.

If you’re working with goroutines, you would always pass in a context parameter to handle cancellation. Many library functions also require context, which poisons the rest of your functions.

Technically, you don’t have to use context for a goroutine and could stub every dependency with context.Background, but that’s very discouraged.

Good thing most of my tasks don’t require novelty, just working code.

I think it depends.

Where I used to live in the Middle East, the culture was very tea (more specifically karak) centric for sure. But it wasn’t a hobby you get so deep into that you become very specific for the average person.

You just drive to your regular place. There’s only one choice and that’s karak. You sip it in your car, chat with your buddies, and you drive off.

Definitely do miss the late nights there. No alcohol, just tea and still an extremely social society.

I don’t think the modern web was designed for you.

To me, Motherduck have so far been excellent stewards for DuckDB. I want them to find a sustainable business model.

I doubt they’ll ever enshittify DuckDB core. It’s clear they’re only aiming for better integration with their paid service via peripherals like UI to improve the experience, but you also don’t need to use it?

It’s all extensions that you can develop the end.

> routing, middleware

net/http (even middlewares are just http.HandleFunc)

> database connections

We were using database/sql for the longest of times before switching to pgx since we wanted some convenience functions.

> email sending

net/mail gets you far enough unless you want to scale it.

> logging

log/slog (which is actually production grade compared to log/log)

> view template rendering

text/template, but I also think Laravel is a better choice if that’s your main focus.

Others either need an experimental standard library package (e.g. golang.org/x/crypto/argon2 for stuff like authentication) or finally need third party dependencies. DI is not enforced like other frameworks, but an extremely common pattern in Go.

At this point, do I really want to bring out a whole framework just for the last few requirements?

Almost everything you listed already exists in the standard library.

And for the little that’s not, such as an ORM, there are many third party libraries available if you want to go down that path although it’s not necessary.

There’s nice things about a lot of these frameworks for sure, like ActiveRecord, but you usually just learn the patterns in Go and roll with it. The standard library has its own consistent style.

The standard library.

It’s honestly feature rich enough to do most things that the only other dependencies we really need to pull in is some third-party SDKs (e.g. AWS) and our database driver.

The Tailscale article taught me a lot! Thanks for sharing.

Go recently did add a new weak pointers and string interning package to its standard library which is an interesting read.

[0] https://go.dev/blog/unique

I’m all for correct attribution, but I’m curious if the author ever bothered asking the maintainers normally before going in guns blazing with legal threats.

To be fair, a lot of this is attributed to your gut microbiome being adapted to the bacteria in your usual diet. Some food may not sit well with you — not necessarily because the food is “bad” but because your system isn’t used to the new bacteria.

That’s why locals are fine but tourists aren’t in most cases.

On a funny side note, when I was in Nepal we did get some food at a pretty popular restaurant. Everyone had horrific food poisoning later that night, except me since I didn’t touch the cheese!

My company used to do everything on-prem. Until a literal earthquake and tsunami took down a bunch of systems.

After that, yeah we’ll let AWS do the hard work of enabling redundancy for us.

Kyle is a great guy. Just to correct the timeline a little bit, I only created Fontsource after its predecessor, Typefaces (which was made by Kyle), was left abandoned when Gatsby took off.

I wouldn’t say he made Typefaces specifically for the Gatsby ecosystem, but he definitely had the hacker mindset for creating frontend tooling for a while.

I recently got a chance to find a practical use for a modified hybrid trie which was fun to implement! Lots of optimisations to go around.

It’s a nifty user-agent parser for Go: https://github.com/medama-io/go-useragent

Typically this sort of problem relies on lots of regex parsing, so it was nice to take a more novel approach.

As someone who has to regularly commute one of these lines… doing “nothing” does become very dull after a while.

I think this thread is a little overblown. Some people will do nothing, read a book, listen to music, or nap. But the easiest thing to fall back to is your phone, especially for a monotonous daily commute.

I do at least try to be productive when using the phone, such as practicing my Japanese. But I think it’s totally normal to stare at the ground and listen to music etc.