HN user

EricRiese

241 karma
Posts8
Comments115
View on HN

It's so ironic. I've had several Thinkpads over the years and I've repaired or upgraded every one of them, from RAM, SSDs, an upgraded screen, and a new fan/heatsink assembly. I have a first generation Framework 13 and I've yet to upgrade it. And by now this new Pro model has an upgrade for every component. If it weren't for crazy prices, I'd just buy a whole new laptop.

At least I have the option of that CoolerMaster case. But maybe it'd be best to just sell the whole thing.

NASA Force 3 months ago

It's the government. They care more about creating objective standards so they can't be sued for bias than they do about hiring the best people.

NASA Force 3 months ago

The entirety of the government doesn't turn over every 4 years, especially at a technical org like NASA. You're still going to be working at NASA with a team of NASA people. Plus if they're hiring you know your team in particular won't be a target of layoffs.

NASA Force 3 months ago

It's the same hiring process for regular government jobs with references to standard pay scales. So I don't think so.

NASA Force 3 months ago

I answered honestly that I didn't and it didn't block my submission.

I have the specific Computer Science/Engineering degree they spell out in length in one question (30 credit hours CS, 16 credit hours math/calculus/stats) so I feel like that gives me a chance on top of the narrow window.

Glad I skipped ahead on the optional essay section. YOLO.

NASA Force 3 months ago

Experience necessary. From Assessment 1, which you only get to after spending $16 ordering your college transcript...

I have 1 year of directly related specialized experience equivalent to at least the GS-13 level in the Federal service that included: Performing program/project management of space, aeronautical flight systems or experimental aircraft/aircraft systems that involve planning, researching, designing, developing, testing and evaluating, or completing cost analyses; Analyzing, designing, or operating space flight systems, aeronautical flight systems, experimental aircraft/aircraft systems, or structures operating throughout the earth's atmosphere; Developing requirements and integrating aerospace or flight/ground systems (e.g., payloads, hardware/software, scientific instruments, communication equipment, cargo, or any other specialized equipment).

This is a Spring specific gripe and I know this blog post doesn't assume Spring, but I hate seeing `new ObjectMapper()`. Spring Boot auto configures an ObjectMapper for you and you probably want the customization it gives you, including `java.time` handling and classpath scanning. I've wrestled with so many bugs caused by not using the `ObjectMapper` bean.

A more concise language is more efficient for an LLM to produce and easier for a human to verify.

I don't think LLMs have solved the problem of wanting code that's concise and also performant.

Much more complicated than necessary. I just use

git branch | xargs git branch -d

Don't quote me, that's off the top of my head.

It won't delete unmerged branches by default. The line with the marker for the current branch throws an error but it does no harm. And I just run it with `develop` checked out. If I delete develop by accident I can recreate it from origin/develop.

Sometimes I intentionally delete develop if my develop branch is far behind the feature branch I'm on. If I don't and I have to switch to a really old develop and pull before merging in my feature branch, it creates unnecessary churn on my files and makes my IDE waste time trying to build the obsolete stuff. And depending how obsolete it is and what files have changed, it can be disruptive to the IDE.

Location: Greater Philadelphia, PA, USA

Remote: Yes

Willing to relocate: Yes

Technologies: Java, Spring Boot, SQL, Scala, Clojure, TypeScript, Linux, Kubernetes, RabbitMQ

Resume: https://ericrie.se/resume.pdf

Email: see resume

Senior Backend Engineer. 13 years of experience. Excited to work in any interesting programming languages. Keen to step up to a role with leadership and mentorship responsibilities.

Lambdas weren't simple to shoehorn into Java. But most of the recent changes have been implemented as well or better, or as well as you could imagine while maintaining backwards compatibility and Java-ness.

Records/sealed interfaces (ADTs) are quite clean.

Text Blocks are better in Java IMO. The margin junk in Scala is silly.

Having the 5 instances going at once sounds like Google Antigravity.

I haven't used Claude Code too much. One snag I found is the tendency when running into snags to fix them incorrectly by rolling back to older versions of things. I think it would benefit from an MCP server for say Maven Central. Likewise it should prefer to generate code using things like project scaffolding tooling whenever possible.

The development of the first Loongson chip was started in 2001. The aim of the Godson project was to develop "high performance general-purpose microprocessors in China", and to become technologically self-sufficient as part of the Made in China 2025 plan.

-Wikipedia

Right on time