HN user

bg4

602 karma
Posts1
Comments220
View on HN
  Location: Dallas–Fort Worth, TX
  Remote: Yes
  Willing to relocate: No
  Technologies: Java, Scala, Python, TypeScript, Kubernetes, Kafka, PostgreSQL, GCP, AWS, learning Go
  Résumé/CV: on request
  Email: bgoldswo@gmail.com
Hello! Fifteen years building backend systems with strict correctness and reliability requirements: matching engines, healthcare workflows, optimization pipelines.

Recently I built a vehicle–passenger on-demand matcher and a Kubernetes job platform for heavy optimization workloads. Before that I worked on distributed systems for chronic-care data (Scala, Kafka). Earlier, I spent a decade in transportation optimization across routing, planning, and scheduling.

I’m at my best when partnering with ML or OR teams, taking prototypes and turning them into predictable, production-ready systems. Strong domain modeling, correctness, property-based testing, and keeping on-call quiet.

Open to senior or staff backend or platform roles.

Happy to talk.

The point of the wedge is to discourage your airway from being blocked. Fwiw, it was recommended to me by my sleep doctor until I was able to complete the process of sleep test and receive/fitted for machine and mask. If you don't have insurance which would cover all of that you should consider it.

I've been treated for it for over 10 years and can't tolerate the mask anymore. I hate it. I've found some relief with a large sleep wedge, you might try that as low cost temporary alternative. In addition, weight loss if that's also a factor (definitely was for me). I'll try to use mask once a week but I usually tear it off in my sleep.

For me, the progression has been: software engineer, software engineer, railroad engineer, railroad engineer, farmer. I will be very interested to see what my son picks and I very much plan to allow him to pursue his own interests.

I think the problem here is you. I've been working remote for years and very much care about them and would take tickets for them to help them out for anniversaries or whatever.

I have a co-worker who takes it upon himself to "discover" and "fix" things that are broken, but to him, "broken" means "I don't understand this, or it's doing it in a way I don't like"

That's a dangerous individual who should be coached (Lesson 1: Chesterton's Fence), or fired.

In my experience, it's easier for many developers to blame the tools and language rather than admit the dumpster fire of a codebase was entirely their doing and their responsibility.

Our school is doing e-learning for 3 weeks then, supposedly, going back to in person. 60-90% of the school population (depending on school) opted for e-learning for the year so when my kids go back there is only 8 or so other kids in the classroom.