zegl

Many other countries have figured this out since the early 2000s, the US could do it as well if they wanted to.

As a long time Hatchet user, I understand why you’ve created this library, but it also disappoints me a little bit. I wish more engineering time was spent on making the core platform more stable and performant.

Congrats on launching! What’s the difference between this and Feature Flags in PostHog?

I recently migrated to Fastmail, and they are handling this very well.

Does "some databases" mean all? I have three databases on Render, all are currently down.

The real puzzle is to figure out how to play it in Safari.

+1 for Zigbee2MQTT. I've been using it at the core of my home automation for a few years, and it's incredibly reliable.

The trick to make CI in large codebases fast, or how to make any system fast, is to only test what’s changed.

In CI you only need to lint the files that have changed, or run the tests that depend on code that has changed etc.

This way the time it takes to execute the tests scales with the amount of changes, and not with the total amount of code.

Posts with text like this really grinds my gears:

chatGPT says that MPTCP has been included in the mainline kernel since Linux kernel version 3.6 and that users can configure and use MPTCP features, but the MPTCP community website says that MPTCP v1 is only supported since 5.6.

Why is it interesting what a GPT has to say about it, if you've fact-checked it and found contradictory information?

Very nice, and well done team!

I've been using v5 in production since beta 20, and it has been working very reliable for us since then. The documentation for how to upgrade has been a great resource, and a great example of how to do breaking changes in a library as large as this one.

TM Sweden AB had a reported 289 employees in 2022, at 10 different facilities.

What are peoples thoughts on sponsoring open source projects as a way to build awareness for dev tools? I think I've seen PostHogs logo in sponsor sections in some READMEs.

I really like this project, and it's fun to see that they are adding their own extra emojis as well.

This really saddens me, RIP.

Congrats Jacob! Mutagen always really impressed me, and is some of the most beautiful code I’ve ever read. Well done!

This intrigued me, and I believe that I've found a solution that's slightly faster for this AoC problem. It's achieved by keeping a running tally/counter for the last 14 characters (benchmark in comments).

https://gist.github.com/zegl/1ce3064c8049fa1b99c1dd202d78588...

I don't know how experienced you are. Yes, you can host "a website" on a Raspberry Pi, even on something tiny like the Zero W. It all depends on your needs, a Pi 4 (if you can get a hold of one) is a great option!

This is genius and horrifying at the same time, I love it!

I don't know how stupid this is on a scale from 1 to 10. I've created a wrapper [1] for git (called "shit", for "short git") that converts non-padded revisions to their padded counterpart.

Examples:

"shit show 14" gets converted to "git show 00000140"

"shit log 10..14" translates to "git log 00000100..00000140"

[1] https://github.com/zegl/extremely-linear/blob/main/shit

You're giving me too much credit. The script [1] is only 50 lines of bash.

[1] https://github.com/zegl/extremely-linear/blob/0011003da13132...

I left some details out of the post to make it shorter.

What I’m actually is doing is generating a 7-digit incremental number followed by a fixed 0. Some UIs show 7 characters and some show 8, this felt like a nice compromise. Plus it’s easier to distinguish between the prefix and the suffix when looking at the full SHA when they are always separated by a 0.

Update: git-linearize now uses lucky_commit as it's backend!

Thanks for sharing, this is really cool! Using whitespace is a really clever trick, and running on the GPU makes it even more impressive.

I've been using githashcrash [1], but it's only running on the CPU, which is why it's a bit slower. :-)

[1] https://github.com/Mattias-/githashcrash

Using SVN doesn't cause your computer to heat up. ;-)

Do not try this at home.

I've been building a lots of what's hopefully "meaningful" software for over 10 years now, at startups (others startups, and now my own), for open-source (zegl/kube-score being my most popular OSS creation), and large enterprises.

I started to become interested in how computers where working when I was ~12, mainly driven by boredom. I didn't know how anything worked of course, but somehow was determined to create my own website, and struggled my way into HTML and free FTP/WWW hosting through various Swedish computer forums and guides. From there I added to my knowledge step by step, I learned CSS to make my sites less ugly, then PHP to be able to "log in", then SQL/MySQL to be able to create a "guestbook", and then some JavaScript, etc etc etc.

After a few years of spending all free time at the computer, I got my first job/internship when I was 14.

During my first 6 years or so as a "programmer", I don't think that I ever considered reading a book on any of the topics. I just went at it, and copy-pasted and brute-forced my way forward until things started to "click" in my head.

I very vividly remember a moment when I realised that I suddenly knew how to create a website that would look exactly the way I wanted, from scratch!

I was building things purely for fun, and started new projects seemingly every weekend. But I kept shipping, and somehow absorbed more and more knowledge.

These days I might read a book/paper/documentation to learn about a new topic, but brute-forcing/learning-by-doing is still my favourite way to learn.

I'm calling it "kringla" ("pretzel")!

Docker is incredibly stable, and since it turns 10 years next year, OP will finally be able to migrate away from having a build step on production servers! ;-)

Oh, tell me about it! I’ve spent this week trying to reproduce the results of a paper from 2019.

Out of the box, the referenced sources doesn’t even compile or run. I’ve been fighting random Python/Java/Scala dependencies, using whatever version was the “latest” at time of publishing usually works, unless of course, it doesn’t support M1…

I built a tool for benchmarking CO2 emissions for Go programs once. It was done as a joke for a meetup once, but is now more relevant than ever.

https://github.com/zegl/co2go