HN user

ntietz

645 karma

Software engineer at Remesh.

Contact details on ntietz.com.

Posts42
Comments46
View on HN
annahope.me 2y ago

Surprises with Rust's `as` (and Python Division)

ntietz
2pts0
www.youtube.com 2y ago

Hanging Out with Imagery [video]

ntietz
2pts0
blog.flowblok.id.au 2y ago

Day 6 of Advent of Code in Hurl

ntietz
2pts0
www.werkema.com 2y ago

We Don't Talk about Semicolons (2022)

ntietz
1pts0
erikarow.land 2y ago

When is an Erlang process a shell?

ntietz
1pts0
www.aadhav.me 2y ago

Building a collaborative text editor in Go

ntietz
1pts0
the.scapegoat.dev 3y ago

Go time's “Neurodiverse Gophers” episode – a critique

ntietz
4pts0
ntietz.com 3y ago

Optimize sprint points to get nowhere fast

ntietz
1pts0
ntietz.com 3y ago

A confusing lifetime error related to Rust's lifetime elision

ntietz
1pts0
ntietz.com 3y ago

Measuring the Overhead of HashMaps in Rust

ntietz
2pts0
www.youtube.com 3y ago

Matt Kulukundis “Designing a Fast, Efficient, Cache-Friendly Hash Table” [video]

ntietz
1pts0
hachibu.net 3y ago

A Tiny Tool for Collecting Website Response Time Statistics

ntietz
2pts0
views.substack.com 3y ago

Rick Wolter: from prison to software developer, building Underdog Devs community

ntietz
1pts0
remesh.blog 4y ago

Breaking Through Scaling Barriers with Bigtable

ntietz
41pts20
remesh.blog 4y ago

Breaking the Rules with Stateful Services

ntietz
3pts1
ntietz.com 5y ago

Where are we going from here? Software engineering needs formal methods

ntietz
139pts131
ntietz.com 5y ago

Drawbacks of Developing in Containers

ntietz
26pts0
www.youtube.com 5y ago

RISC-V Summit 2020 The Next Ten Years [video]

ntietz
6pts0
ntietz.com 5y ago

Lessons from my first (bad) on-call experience

ntietz
1pts0
ntietz.com 5y ago

Load testing is hard and the tools are not great

ntietz
135pts52
remesh.blog 5y ago

Working with people who are smart(er than you)

ntietz
1pts0
ntietz.com 5y ago

What's “good” code and does it matter?

ntietz
1pts0
remesh.blog 5y ago

Learning to Love Idioms

ntietz
1pts0
remesh.blog 5y ago

The Tao of Language Agnosticism

ntietz
5pts0
remesh.blog 6y ago

The Cycle of AI in Product Development

ntietz
2pts0
remesh.blog 6y ago

Refactor vs. Rewrite

ntietz
198pts118
remesh.blog 6y ago

Anarchists, Mercenaries, Farmers, and Ranchers: Engineering Teams at Startups

ntietz
1pts0
ntietz.com 6y ago

Parallel assignment: a misunderstood Python idiom

ntietz
4pts0
remesh.blog 6y ago

Establishing a Mental Model of WebSockets

ntietz
3pts0
ntietz.com 6y ago

Terminology matters: let's stop calling it a “sprint”

ntietz
1pts0

This is great advice! It took me 2 years and many doctors before I wound up at a physical therapist who figured out my nerve issue in 10 minutes. It was wild how they could move my shoulder and reproduce it. Now I’m working on strengthening stuff to make it better—and keeping the setup for a defense in depth against other issues

Various nerve stuff in my arms, limiting my use of keyboards. With an ergonomic keyboard I can get through most days, but I’m having more flare ups lately so I’m doing more voice coding.

I use Talon. It simply doesn’t support Wayland, and I believe its maintainer who says that there are issues with Wayland which make support infeasible. Using it on X makes my nerve pain much less.

I’m in one of the “other smaller groups not included here”: people who rely on accessibility tooling that isn’t supported by Wayland. My options are:

- keep using X and stay healthy

- switch to Wayland and get strong nerve pain again

- switch to Windows or Mac

If Wayland were my only option, I would have to leave Linux for my health. So the technical merits of Wayland truly don’t matter.

Accessibility is an oft forgotten requirement and it’s something that can affect all of us at one time or another. We ought not ignore it.

I had a similar thing happen. I distributed some malware I wrote on the shared drive and had some people run it (it was extremely basic, just locked people out of the computer with no recovery by taking advantage of how locked down they were; but people lost a lot of work). My programming teacher, who was already dealing with me being a distraction in class, went to bat for me so I didn’t get strongly punished but made me clean it off the drive continuously; other students kept putting it back, so I had to monitor for it.

https://ntietz.com

All roughly related to software engineering, weekly cadence. Sometimes philosophical, sometimes technical, sometimes just random observations. Mostly it's about whatever is on my mind re: software at the moment or what I'm playing around with at the time.

I don't read the comments on discussion forums usually, but emails I will always read and respond to emails and I'm always grateful for the feedback.

My understanding is that it's often used as an incentive to get folks to sign NDAs or other agreements on the way out the door. Especially important to them when someone was forced out in less than ideal circumstances, so they'll buy your silence.

https://ntietz.com/

Mostly just has my (tech-focused) blog, although there are aspirational placeholders for the important things in life, like coffee and homemade pizza.

It has been hard to make time to write personal blog posts since my second kid was born, but I have a couple of drafts in progress that I aim to work up soon, at least when I take time off work.

We did consider sharding PostgreSQL and opted for something that would be fully managed for us to minimize our management overhead. Managing sharded databases can be complicated business and that wasn't something we wanted to take on if we could avoid it.

I dug back through our design docs from when we designed this, and we largely chose not to use Cloud Spanner due to unknowns. We were more confident we could predict the read and write performance in BigTable (especially due to the constraints you get when you drop relational features).

I mean, it depends on criticality. If something is critical, pushing further along the formal methods spectrum makes sense (see also: why AWS has done a lot with TLA+). Sure, we probably won’t verify all of Instagram, but super critical portions of the platform underlying it are likely worth it and would save money in the long run by reducing outages, bugs, etc.

There’s a spectrum of formal methods and with the push toward static types in Python coming directly out of industry I would argue that industry is definitely deeming it important in some degree; the question is to what degree. Right now a lot of the time it’s only worth it for the most critical systems (S3, for example, but not my side project webapp) but if tooling improved, it would be worth it for more cases.

When all the software companies went full remote, they just took a break from hiring juniors (!).

This isn’t true at all. Where I work, we hired more junior engineers than ever before during the pandemic. We were hybrid colocated/remote (mostly colocated, plus me!) in the before times. We had certainly hired juniors before, but we hired a lot more and we’re able to source them from all across the country. It’s been fantastic, and onboarding and training junior engineers remote isn’t the impossible task people make it out to be.

This is often a requirement of grocery stores where they intend to sell it, who don’t want to have stock that isn’t salable after two weeks (it can take the big groceries longer than that to just distribute it to their stores).