Remote: Remote (Preferred), Hybrid

Willing to relocate: No

Technologies: Expert level C# skills, Golang (want to get into it more!), SQL Server, PostgreSQL, Docker/Podman, Cosmos DB, AWS, Azure, Cloudflare, .NET Maui / Blazor, Bootstrap CSS, Vim, Linux, Windows, Entity Framework, Kubernetes, Terraform

Email: greg+hn@gregd.org

Linked In: https://www.linkedin.com/in/k9cts/

Github: https://github.com/farmergreg/

Résumé/CV: https://www.gregd.org/resume/hacker-news/

I LOVE: Creating well designed, maintainable, high performance systems.

Example Code: https://github.com/farmergreg/adif processing Ham Radio log files at more than 2x the speed of other comparable parsers.

  Remote: yes

  Willing to relocate: no

  Technologies: c#, go

  Link: https://github.com/hamradiolog-net/adif

  Email: please look for it in the git commits

Principal software engineer with 20 years of c# / .net experience. I am looking to pivot to golang, but would also entertain c# related positions. My resume is available upon request. The link is to recent software I’ve written that demonstrates my abilities.

As part of that, I made an ADIF (ham radio logs) parser to learn go. It's more than 2x faster than parsing the same data in json format with the go standard library.

https://github.com/hamradiolog-net/adif

I could tell you some horror stories about how my current employer does C#. It is very strange.... can't use var, nuget packages for _every_ class library... and it gets stranger from there on out... unfun!

i’m learning golang and made this library that parses ham radio ADIF logs. my goal was to match the speed of the golang json parser. i managed to surpass it by about 2x!

i’m currently employed writing c#, but looking for a job elsewhere and golang seemed like a good way to level up :)

incidentally, i’ve also had the tesla dodge a deer successfully!

autopilot has improved in BIG ways over the past 2 years. went 700 miles in one day on autopilot thru the mountains. no issues at all.

that said expecting perfection from a machine or a human is a fools errand.

for example, I recently hit a deer. The dashcam shows that I had less than 100 feet from when the deer became visible due to terrain to impact while driving at 60 mph. Keeping in mind that stopping a car in 100 feet at 60 mph is impossible. Most vehicles need more than triple that without accounting for human reaction time.

1) Everyday Driving / Commuting: Much like an ICE vehicle where one thinks about 1/2 tank, 1/4 tank, etc... we think about percentages. For us, a round-trip to the in-laws is 50% in the summer and 60% in the winter, for example. Commuting round trip is ~15% in the winter, and ~12% in the summer. This combined with the fact that the car starts every morning charged to 80% means that we really don't ever worry about super charging in our day-to-day life.

2) Road Trips: The navigation software on the tesla automatically add charging stops where needed, and critically, it is very accurate when predicting range as a percentage when it knows your destination. We typically charge until it say we'll reach our destination/charging stops with 10%. That reserve has always been more than enough even on 1000 - 2000 mile road trips.

My general advice to anyone with a Tesla who has range anxiety: 1) Put the round trip into the trip computer. (e.g. Home => Place I Want To Go To => Home) 2) Always make sure you'll get to your next charging stop with 10 - 15% left according to the trip computer. 3) Relax and enjoy the auto-pilot :)

We've never owned a gas vehicle that met it's EPA range and the Tesla is no different. No one takes EPA MPG * GALLONS of gas and expects it to be a real life estimate of range.

Wind resistance increases EXPONENTIALLY with speed. Drive a little over the speeds the EPA used to determine range, and the observed range will drop significantly as a percentage when compared to the EPA range for any vehicle.

If you do have a Tesla, you'll quickly find out that the trip computer is very accurate. The worst I've seen is a cold January day in Wisconsin (-10F) while on a road trip with a head wind. In that scenario, the trip computer was off by 7% mostly due to the head wind. In the summer, it is spot on usually within 1 - 2%.