Show newer
Hawk0 boosted

it's always both fun and depressing when a new engineer wakes up to how "everything is terrible" in the tech industry: tonsky.me/blog/disenchantment/

Interesting how the new code of conduct removes focus on quality of code and emphasises irrelevant things like "feelings". This is being touted as a win for the influence of women in stem, but if I was a woman in stem with focus in a software development project being taken away from code quality, I'd be mortified this was being pinned on me!

Hawk0 boosted

Okta partners with Yubico to offer free security keys: zdnet.com/article/okta-partner <--- This is super cool! Excited to see my company @oktadev@twitter.com working with @yubico, one of the best key providers out there. I <333 my Yubikeys.

Hawk0 boosted
Hawk0 boosted
Hawk0 boosted

"We are long past due for the fulfillment of Keynes’ prophecy [that people in developed countries would work 15 hours per week]. Around the year 2000, countries like France, the Netherlands, and the United States were already five times as wealthy as in 1930. Yet nowadays our biggest challenges are not leisure and boredom, but stress and uncertainty."

Show thread
Hawk0 boosted

I've made a deliberate choice against a quoting feature because it inevitably adds toxicity to people's behaviours. You are tempted to quote when you should be replying, and so you speak at your audience instead of with the person you are talking to. It becomes performative. Even when doing it for "good" like ridiculing awful comments, you are giving awful comments more eyeballs that way. No quote toots. Thank's

I learned most of what I know about docker from the official docs, experimenting, and reading Dockerfile and compose.yml files with functionality I liked off . Start with the things you are using (aka ) before branching off into hopes and dreams. Stay up to date with the engine direction / .

Hawk0 boosted

Hey so any Docker experts out there want to answer this question without judging my approach? Here's what I'm after:

- I run `docker-compose build` with a new config file ( github.com/ashfurrow/mastodon/ )
- I run `docker-compose up -d`
- Something goes wrong, I need to roll back to the old images
- I run [you tell me commands] and that tags the old images as latest or something so that when I run `docker-compose up -d` again, I've rolled back and booted old images.

I've looked and can't find this. Suggestions?

Hawk0 boosted

Great news! The new Docker images with jemalloc are working on staging 🎉

Saturday's maintenance window (see @announcements) will include that move to jemalloc, and we can find put these memory leaks behind us.

Show thread
Hawk0 boosted
Hawk0 boosted
Hawk0 boosted
Hawk0 boosted

boosting a toot sounds like what 80's Wall Street guys did in the club bathroom

Hawk0 boosted

# introductions

I'm Ben and I've been a software engineer for 25 years. I know a bunch of languages and systems and techniques and I like building stuff that handles millions of users.

It's important to me to pay it forward, to guide others, to pass knowledge along and welcome them to do the same.

Building any significant system is a social activity and we are social animals. We're not robots, we affect each other. Don't be a jerk, or a prima donna: lift each other up and build great things together.

Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!