HN user

langcss

233 karma
Posts10
Comments184
View on HN

You need a lot more power. I found gpt4o struggles doing basic OCR of printed text by hallucinating alot, while tesseract engine (old skool) gets it perfect. You need the model to be powerful enough to do everything.

You can work around this by the way by sending the output through a checking stage.

So picture -> gpt4o -> out1, picture -> tesseract -> out2, out1,out2 -> llm.

Might work for sound too.

The built in DB makes this very interesting to me. Although I would prefer sqlite. The low LOC count is nice to know.

Minimilism is something that is hard to get right on the web. The cliche is people avoid django because it is too complex then hand build all its features anyway over time!

However some jobs are minimal esp. internal dashboards so there is a place for it. You may find fasthtml which is also minimal interesting.

Curious: why Java and not Go? Go seems more in line with being minimal. Especially for deployment.

Terence Tao on O1 2 years ago

I believe LLMs decimating the role of a software engineer requires AGI, which the second that happens decimates all jobs.

What it may do is change the job requrements. Web/JS has decimated (reduced by 90% or more) MFC C++ jobs after all.

The programmer doesnt just write Python. That is the how... not the what.

Next is odd because it gives lots of "high preformance" vibes with static rendering and image optimization. It is fast enough but not as fast as tuning up a classic MVC app which caching, avoiding JS bundles and React or deferring scripts etc. Send out the right cache headers and chuck a CDN in front.

Next is ironically fast if you prerender/static generate AND the client disables JS!

A bit like "is this hotdog overpriced" amd trying to binary search the exact cent where it became overpriced.

Best to use SSO for SaaS passwords. This is where your whole team has a Microsoft or Google (or other identity provider) login administered centrally by the company that is further used to authenticate to various services.

As opposed to "login with Facebook etc." logins that are individually administered by each end user for each app.

This is low fruit for many things but often companies require you to be on an expensive SaaS pricing tier to use SSO on their product.

Next problem to solve is Software Engineer's cloud secrets. Use key vaults in your cloud for this. Use SSO to authenticate your team to that cloud.

Enable 2fa as much as possible. TOTP not SMS.

Finally you will need people to save passwords for some stuff. Lastpass or Bitwarden etc.

Avoid shared passwords. Sometimes unavoidable in which case rotate them often and when people leave too.