Preferences

kevinqi
Joined 152 karma
Software engineer at Gridmatic

  1. I think there are profitability requirements, right?
  2. +1, very polite way of saying it. of course there's a difference between the two posts. open source is interesting but not enough with a financial app, since it's all about trust + usefulness.

    landing page needs to look good and communicate the value prop super effectively. If it doesn't look good you'll lose people's interest in about 2 seconds.

  3. probably the "slapping steamOS" part of that
  4. my only minor critique is using lorem ipsum examples. It tends to make me want to gloss over instead of reading; I prefer seeing realistic data. other than that, it's a really cool post
  5. right, it is just syntactic sugar, but if that wasn't helpful then why have it in dev either? I find it more confusing to have asserts be stripped, which creates an implicit dev/prod discrepancy
  6. really? it's pretty but I find it unreadable/unusable
  7. I didn't think much of it until I canceled Cursor to try out copilot, which is slower and yet also worse quality. I reluctantly resubscribed to Cursor.
  8. interesting, I didn't know that corollary. sounds about right though.
  9. duplicate code is not that bad. reduce duplication over time as you find the common patterns/abstractions, instead of trying to build abstractions too early
  10. very cool. btw, I also love that "sorry" is the "any" equivalent in Lean
  11. as someone who hasn't seen Lean before but was curious from alphaproof, love the intro! curious if you can mention what you're working on in Lean?
  12. I mean, why do systems go down at all? a lot of big outages are simple misconfiguration or cascading failure from what seemed like small changes. It's rarely due to the physical constraints of the world
  13. I made a web microtonal keyboard a while ago which does support this! different format though

    https://www.microharmonic.com

  14. yeah, the benchmarks are just a proxy. o3 was a step change where I started to really be able to build stuff I couldn't before
  15. just based on how long it takes to produce these images, and how much text responses cost, I wouldn't be surprised at all if it was close to cost
  16. Gridmatic | Senior fullstack software engineer, Senior backend software engineer (ML infra) | Full-time | Hybrid (Cupertino, CA)

    Gridmatic uses ML and weather data to forecast energy prices in the US, which can get really volatile as extreme weather becomes more common with climate change. We’ve been using those price forecasts to e.g. optimize very large batteries, which help make the grid more stable.

    On the fullstack side, we're building tools to apply our forecasts to automated battery storage optimization and energy volatility risk mitigation. On the ML infra side, we're working on infra to be able to scale to larger and more complex models, and to apply better (but more computationally intensive) weather models in our forecasting.

    Our stack: python, react/nextjs, kubernetes, GCP, postgres, bigquery

    Our goal is to help accelerate the adoption of renewable energy on the grid. It's super interesting, the team is incredibly smart, and we're profitable.

    If you're interested, DM me or email me at kevin@gridmatic.com, and please answer the following question: what's the most impressive thing you've built? (include a link to code if possible)

  17. I don't disagree, but since the quality of AI is largely a function of the quality of human content, there's always going to be value in well-written human content. If humans stop producing content, I think the value of AI/LLMs drop significantly as well.
  18. ah interesting, that makes sense witas an explanation given the heavy Tesla base
  19. yeah I've had a similar experience with a bike and do the head bob thing now too. glad to know it's not just me
  20. good tip, thank you!
  21. Aside from the distracted driving part, which is real, there are two physical aspects of the model 3 that I find to be safety issues as well-- the two front windshield beams are thick and add a sort of blind spot, and the side mirrors don't give you great field of view.
  22. 30-40 people; not much TPS but we're not primarily building a web app; we have event-driven data pipelines and microservices for ML data.

    If you're primarily building a web app, a monolith is fine for quite a while, I think. But a lot of the stuff in the post is still relevant even for monoliths - RDS, Redis, ECR, terraform, pagerduty, monitoring/observability.

  23. I work at a startup and most of the stuff in the article covers things we use and solve real world problems.

    If you're looking for successful businesses, indie hackers like levelsio show you how far you can get with very simple architectures. But that's solo dev work - once you have a team and are dealing with larger-scale data, things like infrastructure as code, orchestration, and observability become important. Kubernetes may or may not be essential depending on what you're building; it seems good for AI companies, though.

  24. "No" seems easy to say right now, but technology is accelerating at a breakneck pace. If AGI can happen within a decade, I reckon 2030 self driving is not a crazy bet at all.
  25. Loved the article! Really well written, thoughtful, and actionable advice.
  26. Thanks, fixed!
  27. Gridmatic | Senior full-stack software engineer | Onsite in Cupertino, CA (hybrid)

    https://jobs.lever.co/gridmatic/ee0f4882-10aa-4c92-b0bb-1497...

    Gridmatic is a profitable early-stage climate tech startup that uses ML forecasting to help decarbonize the energy grid. We use ML to help with grid-related operations like optimizing battery farms and being a retailer of 24/7 carbon-free energy.

    We’re looking for an experienced full-stack engineer with 3+ YOE with the ability to build product from zero-to-one to work on our retail energy initiative. You’d work across the stack on a wide range of projects — building out a web app for energy customers, working with third-parties to pull in energy usage data and public renewable energy data, integrate billing and other key operational systems, and help improve automation and scale up to hundreds of customers. We value the ability to push through uncertainty and take ownership of the retail web platform.

    Our stack is Python, React, Postgres, Kubernetes, and GCP. Having Python and React experience is preferable.

    Gridmatic has a hybrid policy of "50% in-office”. Most of the company works in our Cupertino, CA office 2 or 3 days a week.

    Apply here: https://jobs.lever.co/gridmatic/ee0f4882-10aa-4c92-b0bb-1497...

    Leave a comment if you have any questions!

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal