rongenre

I'm an experienced individual contributor who's done a lot of work building and scaling distributed backend systems in a bunch of different industries. I've worked for both startups and large enterprises.

  @book{Kuhn1962,
    author    = {Kuhn, Thomas S.},
    title     = {The Structure of Scientific Revolutions},
    publisher = {University of Chicago Press},
    year      = {1962},
    address   = {Chicago},
    note      = {Often cited with various editions, e.g., 50th ed. 2012},
    keywords  = {paradigm shift, normal science, scientific revolutions}
  }

Curious if anyone would find this useful: https://github.com/rbagchi/git-dataframe-tools

If AI is roughly where IT is in the 60's, we might see actually decreased productivity for a while until people (yes people) figure out how to use it effectively.

1. Brainstorming building something. Tell it what you're working on, add a paragraph or two of how you might build it, and ask it to give you pros and cons and ways to improve. Especially if it's mostly a well-trod design it can be helpful.

2. Treating it like a coach - tell it what you've done and need to get done, include any feedback you've had, and ask it for suggestions. This particularly helps when you're some kind of neurospicy and "regular human" responses sort of escape you.

I miss that girl.

I mostly do commuting, grocery runs, etc. EVs are great for that. But then I do road trips about once a year, and an EV just adds to the complexity of planning currently.

What they really didn't understand is that software sells hardware: The OS was so far ahead, but in terms of basic productivity software? Even the Mac was ahead.

And [IMO] markets can maintain a leader and one strong competitor. But just one. So it became PC/Mac throughout the 90's on the desktop.

Incredible, though, how the relatively cheaper Windows NT machines and 3dfx cards and graphics software just killed them. I was a little sad when I wandered around the campus of an employer in Mountain View and noticed the fading sign that had what was left of the SGI logo.

Remote: Yes, will travel within 30-45 minutes

Willing to relocate: No

Technologies: Python, Java, Spring Boot, Relational Databases, Kubernetes, public clouds

Résumé/CV: ask me

Email: in my profile

Mostly a backend developer, but I've done full stack before and I'm open to doing more of that. I also have a strong interest in AI and LLM (like everyone else here)

When I was being courted by a startup for an IC position, the best question I asked was "What does your churn look like?". It was really low, and despite some other reservations I ended up taking the job, and we had an awesome exit. Because our customers really loved us, and we worked hard to make them successful.

In my native language (English), I can twist and weasel with the language to keep from committing to... anything. It has -- too many degrees of freedom available to me.

With German, though [where I'm intermediate], I don't have that flexibility. My conversations are really straightforward and what comes out is simple enough that I can express it. I'd say that this does come at the cost of understanding and expressing nuance and condition, but maybe that's actually helpful.

I was really pleased to add it to my toolkit.

There was a place (in Berkeley of course) where I was pretty sure that if the barista didn't like your tip, they'd boil the milk for you.

I decided to try again today, we'll see.

When I deposit money from my bank, it takes a full week for it to be available for withdrawal.

Oddly, I have my employer put $20 into it every pay period (honestly on a lark), and it showed up on the expected date, and was available for withdrawal.