@jawnsy@mastodon.social
@jawnsy@mastodon.social avatar

jawnsy

@jawnsy@mastodon.social

I'm here to learn. He/him. Interested in containers, computers, and human beings. Urbanist living in San Francisco.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

anderseknert, (edited ) to random
@anderseknert@hachyderm.io avatar

Met with an ex-colleague recently who told me he’s relying more and more on co-pilot for coding at work. Not just “autocomplete” but the chat where you tell it what you want and it can write hundreds of LOC from that. Not for me but to each their own. But what really stuck with me is how he told me how he’d been asked to explain something in a PR he submitted and… he couldn’t. He had no idea what the code “he” had written did in that location. What the actual fuck. I’d die there and then.

jawnsy,
@jawnsy@mastodon.social avatar

@anderseknert It's a good idea to use someone else's name in commits for this reason. Sorry if you get emails asking about bugs in my code, Anders 😝

charlieegan3, to random
@charlieegan3@hachyderm.io avatar

Amazing team event with Styra in Cancún this week! 🏖️

image/jpeg
image/jpeg

jawnsy,
@jawnsy@mastodon.social avatar

@charlieegan3 lmao of course @anderseknert has his laptop, even at the poolside, and of course he has GitHub open 😂

jawnsy,
@jawnsy@mastodon.social avatar

@anderseknert @charlieegan3 "But manager, code is what I enjoy"

You look happy, Anders! Cheers

norootcause, to random
@norootcause@hachyderm.io avatar

Two of the biggest sources of incidents I’ve seen are:

  1. Legacy code
  2. Migrating away from legacy code

The conclusion is clear: you should only write non-legacy code

jawnsy,
@jawnsy@mastodon.social avatar

@norootcause @stuartmarks While we're at it, we should also be more clairvoyant so we never need to deprecate anything

jawnsy,
@jawnsy@mastodon.social avatar

@stuartmarks @norootcause Sprinkle some AI on it! Yaaassa

Salty Salt Bae GIF

bagder, to random
@bagder@mastodon.social avatar

In early 2010 we documented the option --ftp-ssl as deprecated, you should use --ssl instead.

When 8.6.0 shipped 28 days ago, I accidentally broke --ftp-ssl. It took until today until someone found out. Now we know that the option we've been trying to get people to stop using for fourteen years is still used.

We will have it restored again in the next release.

jawnsy,
@jawnsy@mastodon.social avatar

@bagder @colin_mcmillen This reminds me of Linus' "Never break userspace"

I'm always really impressed when people stay true to their values like this, even when it's hard or inconvenient. Thanks for your work and also I'm sorry you have to maintain this old option, lol

anderseknert, to terraform
@anderseknert@hachyderm.io avatar

While I’ll be following the #Linkerd / #CNCF drama with interest, this isn’t a rug pull like the #terraform license switch. #OpenSource means the source code is… well, open. That’s all. I’ve said it before: there’s no “spirit of open source” that always seems to put a ton of obligations on maintainers but never on users.

Doesn’t mean anyone has to be happy about the change, and I fully understand those who aren’t. But if it’s not in a license — OSS or commercial — it’s not an obligation.

jawnsy,
@jawnsy@mastodon.social avatar

@anderseknert When I evaluated these, I think Istio had dramatically more market share than linkerd or other service meshes, so it seemed like the better choice. It also meant no single-vendor dependency; I think these rug pulls are always a risk in that case.

Plus, Istio is nicely integrated to other systems :)

johncarlosbaez, to random
@johncarlosbaez@mathstodon.xyz avatar

So much of what we're suffering in the US - and elsewhere - is due to the capture of income by the rich. To quote:

"How big is this elephant? A staggering $50 trillion. That is how much the upward redistribution of income has cost American workers over the past several decades.

This is not some back-of-the-napkin approximation. According to a groundbreaking new working paper by Carter C. Price and Kathryn Edwards of the RAND Corporation, had the more equitable income distributions of the three decades following World War II (1945 through 1974) merely held steady, the aggregate annual income of Americans earning below the 90th percentile would have been $2.5 trillion higher in the year 2018 alone. That is an amount equal to nearly 12 percent of GDP—enough to more than double median income—enough to pay every single working American in the bottom nine deciles an additional $1,144 a month. Every month. Every single year.

Price and Edwards calculate that the cumulative tab for our four-decade-long experiment in radical inequality had grown to over $47 trillion from 1975 through 2018. At a recent pace of about $2.5 trillion a year, that number we estimate crossed the $50 trillion mark by early 2020. That’s $50 trillion that would have gone into the paychecks of working Americans had inequality held constant—$50 trillion that would have built a far larger and more prosperous economy—$50 trillion that would have enabled the vast majority of Americans to enter this pandemic far more healthy, resilient, and financially secure."

https://time.com/5888024/50-trillion-income-inequality-america/

jawnsy,
@jawnsy@mastodon.social avatar

@johncarlosbaez I do sometimes idly wonder whether our historically low inflation is because of this, since the wealthiest people are more likely to save rather than spend their income, having already gotten everything they want

jawnsy, to random
@jawnsy@mastodon.social avatar

Periodic reminder that this repository of Resilience Engineering resources, papers, talks, etc. is incredible.

If you build, operate, or use large-scale software systems, take a few minutes to peruse this library: https://github.com/lorin/resilience-engineering by @norootcause

bynkii, to random
@bynkii@mastodon.social avatar

I will say this until it is no longer true:

If a non-admin user clicking on a link or opening up an infected word file damages anything on your network your security is shit.

Periodt.

jawnsy,
@jawnsy@mastodon.social avatar

@shortridge @bynkii @saraislet Can't get phished if you never check your email

Big Brain GIF

jawnsy, to random
@jawnsy@mastodon.social avatar

Reading this while reflecting on "big rewrite" type projects in software is, well, ouch:

"His seminal work on big projects can be distilled into three pitiful numbers:

• 47.9% are delivered on budget.
• 8.5% are delivered on budget and on time.
• 0.5% are delivered on budget, on time and with the projected benefits."

I think the solution is simple, but not easy: smaller, more frequent deliveries. Progress over perfection.

https://www.wsj.com/arts-culture/books/lego-megaprojects-bent-flyvbjerg-big-things-11675280517

jawnsy, to random
@jawnsy@mastodon.social avatar

A great preface to a great article:

"The naive approach to securing software is to blindly implement a checklist of security features. But a deeper understanding of security will quickly uncover that perfect security is impossible; you have to make trade-offs and prioritize the most likely scenarios."

https://www.macchaffee.com/blog/2022/k8s-secrets/

jawnsy,
@jawnsy@mastodon.social avatar

@anderseknert Yeah. It tracks with my own experience, too.

I often wonder about these "last mile" problems - the tools are great, but require more effort to use effectively than many teams are able or willing to invest, which results in situations like this.

In the end, no technology or process is perfect: it's tradeoffs all the way down...

jawnsy, to random
@jawnsy@mastodon.social avatar

Very few software projects are successful over long periods of time. I think one explanation is that it is very challenging to evolve systems in ways that respect the needs of new users ("better" approaches to things, temptation to make backwards-incompatible changes) and existing users (backwards-compatibility is a virtue.)

In this respect, I think about these talks often:

https://youtu.be/2y5Pv4yN0b0 by @briangoetz

https://youtu.be/pEYpvYVlgQc by @rkatz & Carlos Panato

jawnsy,
@jawnsy@mastodon.social avatar

@stuartmarks @briangoetz @rkatz Something that I find interesting about the various communities of experts (IETF, KEP, JEP, PEP) is the insights that people have, particularly around non-obvious interactions between features. Following the JDK development lists is a great lesson that implementing things hastily can really cost you enormously later, and I think often about all the avoided mistakes, too.

Also, Josh Bloch's Golden Rule of API Design, "when in doubt, leave it out," is so wonderful

JenMsft, to random
@JenMsft@mastodon.social avatar

🥲

jawnsy,
@jawnsy@mastodon.social avatar

@JenMsft It really does make you appreciate good documentation, though!

jawnsy, to random
@jawnsy@mastodon.social avatar

Embedded devices are cursed.
Windows is cursed.
USB is cursed.

And yet...

@jberi is unafraid! 🙌

Thank you, Jonathan, this guide is amazing!

https://blog.golioth.io/usb-support-in-wsl2-now-with-a-gui/

stuartmarks, to random
@stuartmarks@mastodon.social avatar

As a matter of fact, there is such a thing as too much garlic.

jawnsy,
@jawnsy@mastodon.social avatar

@stuartmarks Why, are you a vampire?

bagder, to random
@bagder@mastodon.social avatar

I'm too stupid to figure out cmake.

jawnsy,
@jawnsy@mastodon.social avatar

@bagder This makes me wonder if cmake embeds libcurl

jberi, to random
@jberi@hachyderm.io avatar

People who complain about SQL have never used AT commands.

jawnsy,
@jawnsy@mastodon.social avatar

@jberi We get it, you're old 😜

jawnsy,
@jawnsy@mastodon.social avatar

@jberi Backward compatibility to rival x86? 😜 I've always found it interesting how much our modern machinery contains echoes of the past

jberi, to random
@jberi@hachyderm.io avatar

Ooh, a nice GUI for USB devices with WSL on Windows. 👀 https://gitlab.com/alelec/wsl-usb-gui

jawnsy,
@jawnsy@mastodon.social avatar

@jberi (butterfly meme guy) Is this Dan-Mangum-bait? 🤓🫱🦋

mrcranky, to random

Today we celebrate the birth of Sir Isaac Newton. Without his invention of calculus we would have no way to stop people who are bad at math from becoming engineers.

jawnsy,
@jawnsy@mastodon.social avatar

@mrcranky I'm terrible at math and still became an engineer haha (EE & CS double major)

anderseknert, to random
@anderseknert@hachyderm.io avatar

With both kids running a fever, we had no choice but to stay home. Not the best Christmas (which is celebrated the 24th here, as Santa intended), but we tried our best to spoil the kids, and I think they’ve had a great day. Luckily they’re too young to know/remember how Christmas is supposed to be spent with the extended family.

jawnsy,
@jawnsy@mastodon.social avatar

@anderseknert Sorry to hear that the kids are feeling under the weather, hopefully everyone feels better soon!

The pics of your family are so adorable. 😍 That triple juice box game inn particular! 🧃🧃🧃

anderseknert, to random
@anderseknert@hachyderm.io avatar

Honestly impressed by seeing so many here aren’t just talking about moving off , but actually doing it. You’re all the real deal!

jawnsy,
@jawnsy@mastodon.social avatar

@anderseknert It always seems like such a Sophie's Choice:

  1. Self-host something open source, and now you've given yourself a job to maintain some junk in perpetuity

  2. Use a hosted service, but be forced to migrate every few years

Maybe using hosted open source services is the way?

I haven't been paying attention: why are people migrating off substack?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • megavids
  • tacticalgear
  • magazineikmin
  • thenastyranch
  • Youngstown
  • mdbf
  • rosin
  • slotface
  • InstantRegret
  • khanakhh
  • Durango
  • kavyap
  • osvaldo12
  • DreamBathrooms
  • JUstTest
  • GTA5RPClips
  • ngwrru68w68
  • everett
  • tester
  • ethstaker
  • cisconetworking
  • cubers
  • modclub
  • provamag3
  • anitta
  • normalnudes
  • Leos
  • lostlight
  • All magazines
    •