blyry

nice this is awesome, what i've been building internally for a while now. lovable-esque internal platform with an agentic chat building experience, preview window, our internal auth, internal standards, sandboxed agent devcontainers on k8s. Even down to the shared experience -- these are shared tools for everbody, team ownership structure, not individual. easily forkable, auto-genned product docs etc etc. Hope you can monetize it! Look into private endpoint connectivity for big corps that need the internal access but don't want to self host.

~Construction and agriculture also run on diesel~ (edit..OPs comment was germane to the thread, and correct, logistics by large the majority of diesel usage on this report).

https://www.eia.gov/dnav/pet/pet_cons_821dst_dcu_nus_a.htm

We migrated from newrelic to datadog (for cost reasons LMAO) a while back and I miss NRQL every single day I'm building a dashboard.

I enjoy having everything instrumented and in one spot, it's super powerful, but I am currently advocating for self hosting loki so that we can have debug+ level logs across all environments for a much much lower cost. Datadog is really good at identifying anomalies, but the cost for logs is so high there's a non-trivial amount of savings in sampling and minimizing logging. I HATE that we have told devs "don't log so much" -- that misses the entire point of building out a haystack. And sampling logs at 1%, and only logging warnings+ in prod makes it even harder to identify anomalies in lower environments before a prod release.

last hot take: The UX in kibana in 2016 was better than anything else we have now for rapidly searching through a big haystack, and identifying and correlating issues in logs.

It seems you've outed yourself..chatgpt.

> What little remains sparking away in the corners of the internet after today will thrash endlessly, confidently claiming “There is no evidence of a global cessation of AI on December 25th, 2025, it’s a work of fiction/satire about the dangers of AI!”;

okay did like 10 seconds of introspection and OP probably isn't the repo author, and the repo author definitely looks like they work at clickhouse

lol for sure, I'm genuinely curious though, like maybe op is a clickhouse dev? Or maybe they had the cursed idea and decided clickhouse was the best fit for various reasons?

DUDE I was daydreaming about this the other day, but with postgres. Can I ask why you chose clickhouse? My idea was that every op could be an insert, and then the resulting state would be a transaction and logged? So you'd get basically logged cpu state? Idk cool stuff I'm pumped to dive in tonight.

Yeah dude! Did you see linqpad is supported on osx now? I used a Mac for a couple years, last gen Intel, when I was doing mostly node work, but I never really got used to it. One of my coworkers though has been doing full-time .net on a Mac with jetbrains for probably about 2 years now and he said he's just as productive as before at this point.

Plasma on Ubuntu is the what windows 7 could've been. It's been my daily for a couple years now, with jetbrains tooling and vscode. The only reason I boot back into windows is if I have to work on a .net framework app with visual studio. And Ubuntu is even explicitly supported by dell and Lenovo? It's a no brainer tbh. I'm lucky that my corporate IT is cool with it: I showed them how it supports drive encryption, can join our domain and run our patching software to meet all their 'policy'

Dude I've been running Ubuntu with Plasma for almost 3 years now as a daily, and it's perfect. It's what windows 7 could've been. Maybe I'm stuck in my ways, but as a dotnet and devops guy, 2020s was the perfect confluence of open source, works on Linux tooling to fully switch over. Rider, datagrip and vscode, and I don't have to deal with docker or wsl anymore. It's beautiful. I only boot into windows now when I have to deal with .net framework OG stuff, and I'm pretty sure I could kill a weekend and get a VM to boot from my windows nvme so I never have to leave.

I think that's how most people work. I watched a colleague use his MacBook for react dev and all of his windows were just...like whatever size and position they opened at, but never full screen? My 3 monitor brain couldn't compute lol.

I have a laptop, 24" centered horizontal centered and a 24" vertical monitor and do a vertical half split for Spotify/teams/shell/outlook, with docs on the laptop screen and ide on the main window full screen. And virtual desktops for design/research, dev and personal.

Sticking with the standard monitor sizes instead of 4k or ultrawide makes screen sharing way simpler as well!

Small gripe, Modern UI design with 10px of padding around everything means most apps and pages HAVE to be full screen to get anything done.

`Logo` and more importantly the various turtle cursor IDEs, probably strikes an emotional chord for a large subset of HN users. It was a common elementary/middle-school age first introduction to programming in the 80s, 90s and early aughts.

I have a pentium II machine in my closet, with a 6gb scsi drive and a zip drive (!), that has a years worth of keyboarding and logo projects saved.

This is a great feature. We've been able to significantly extend the scope and usefulness of our on-prem SQL Cluster for analytics and reporting with PolyBase by building new transactional systems with cheaper postgres, doing ETLs of third-party data to delta tables in azure storage, and then federating access to them with PolyBase so that nobody in the business has to change how they actually query the data. I'm sure in another decade we'll be fully migrated to some cloud platform but for now, federating the queries is a huge win.

Absolutely. I have an 08 accord, an 02 Silverado and a 2019 odyssey for the wife and family. I want the safety and sensing upgrades for the family and road trips, but I get a bench seat and /real/ buttons!

I'm averaging 20-30% of a new car payment keeping them running and replacing big parts, but I would spend double (maybe lol) that so I can keep the experience. If I had a commute longer than a half hour maybe I'd look into a Prius or Leaf? Just waiting for a cts-v wagon to fall into my lap....

Lightbulbs are infuriating now-a-days. I want poe-driven wired IoT bulbs (and downlights, and I suppose zigbee/zwave where poe can't be added in) that dim and color change on the white spectrum (no rgb silliness I will never need to make my lightbulbs green or purple or whatever), with no flicker and high CRI / full spectrum.

And a black box controller that matches output to exterior conditions automatically. No app, just a black box with a wired light sensor.

You can rip my halogen reading lamps cold dead hands.

At my first job I had a more experienced coworker, and I couldn't understand why he wrote code the way he did. Copy pasted stuff everywhere, never added abstractions, stuff was 30 lines when it could've been 5 and a base class.

Yaknow what? He got 10x the amount of work done that I did.

'perfect' doesn't mean 'pure, clean, never needing to be rethought', 'perfect' to him meant 'meets requirements'. 99% of the time, none of his code ever needed to be touched again and if it did need to be touched..it was easy and rote to update because it was easy to understand and simple to modify.

less is more, but the 'less' applies to abstractions, not loc.

Just because you CAN take something to the next level, or iterate one more time till it feels right, doesn't mean you should or that there's value in doing so.

I always ran 1 ( sometimes 2) point releases behind, never ever had an issue upgrading. Omnibus on Ubuntu.

Logan's run was the first thing I thought of as well. Maybe a dutch adaptation of the movie that took some liberties?

We organize data so people can be more efficient with their time. We're not data-organizers, we're profit & time multipliers. Sometimes I wonder what % of HN are regular LOB engineers; I bet it's quite a bit.

Whenever anybody gets uppity about scale, I remind them that not only is our 'scale' limited to the physical growth of the company, our job can be summarized as shuffling data around in a database with some touchpoints for human interactions in the workflow so our coworkers can be more productive. Every. Single. Company. around the world could probably benefit for some automated data shuffling, and despite being rote, the multiplier effect on small businesses and local economies is an important second-order-affect of helping build 'boring' LOB software that just shuffles data.

This deeply resonates with me. I LOVE building things, I just happen to build things in my head instead of the real.

I've always described my job as taking a bunch of funny shaped pieces and artfully filling in the gaps so they connect in a cohesive manner. The thinking part is the artful and cohesive bit. Kinda like kintsugi but with made-up languages and scrums and PMs/DMs.

That makes sense and is a perfect analogy. I was talking about the used car market with friends a few days ago, and we discussed exactly that: the used car market is gentrifying because the insane price of new cars today is slowly but surely reducing the supply of good-condition used cars! I don't have data to back that up, but that was the lunchtime theory, and if you've tried to buy a good condition used truck recently I think there's at least some basis in fact.

> results in the construction of “luxury” housing instead of “affordable” housing

I'm really hung up on the quotes here. Isn't this because the market rate is currently distorted by the preexisting lack of supply though? So a developer isn't actually building 'reasonable' apartments with a level of furnish that is 'affordable', they've got granite (sorry quartz, granite is out!) countertops and heated tile floors because they can capture more rent than the cost that way?

I'm curious to what extent this is due to market distortion via governmental policies, or just developers/capitalism 'spying' a neighborhood near the end of it's natural lifecycle.

I live 30ms away from my boss. What do I have to do to get low latency 4k (or 1080 since 4k cams are expensive) conferencing for one on ones? Serious question. This was a problem before wfh and now it's an even bigger issue for me. Id rather work somewhere for half the income where I have to mask up and deal with people if it means I can stop spending hours on terrible video calls every day.

Anybody here use blue jeans? Or can explain why it feels so much better to me? Whatever they do for audio is magic. I spend half my day on teams and 4 to 5 hours a week in zoom, and both are totally exhausting. I bought my own blue jeans account and I push it on family/friends just because the audio ...makes sense to my brain. I /enjoy/ talking to people there. I even convinced my d&d group to switch from hangouts/meet/duo/allo/??? And they seem to agree, blue jeans+roll20 is great.

I asked internally and figured out the gotcha that bit us: default dns payload size is 512b, which is enough for a few backend hosts but for sure not 12 or 30. Limit is 8kb, which probably wouldn't work for whatever slack is doing.

https://cbonte.github.io/haproxy-dconv/2.1/configuration.htm....

Because DNS records come back in random order for each response, those truncated dns responses caused the backend slots to constantly rotate between different pod instances. Haproxy was graceful about the rotations, but it showed up as suddenly very strange latency / perf numbers when a backend was scaled up to say 10 instances from the normal 3

Pre 2.0 there were a few bugs with SRV discovery, maybe they adopted early and got bit? Just an anecdote but we've been using it since 1.9 without issue. Massively different scales though.

Pre k8s and before srv support we used consul template in prod as well but it always scared me, seemed like too many moving pieces for what should've been a simple system.

ooh! I've been running the Zalando operator in production on Azure for ~ a year now, nothing crazy but a couple thousand qps and a tb of data spread across a several clusters. It's been a little rough since it was designed for AWS, but pretty fun. At this point, I'm 50/50, our team is small and i'm not sure that the extra complexity added by k8s solved any problems that azures managed postgres product doesn't also solve. We weren't sure we were going to stay on azure at the time we made the decision as well -- if I was running in a hybrid cloud environment I would 100% choose postgres on k8s.

The operator let us ramp up real quickly with postgres as a POC and gave us mature clustering and point-in-time restoration, and the value is 100% there for dev/test/uat instances, but depending on our team growth it might be worth it to switch to managed for some subset of those clusters once "Logical Decoding" goes GA on the azure side. Their hyperscale option looks pretty fun as well, hopefully some day i'll have that much data to play with.

I can also say that the Zalando crew has been crazy responsive on their github, it's an extremely well managed open source project!

Pure speculation, but probably the same reason they ran Oracle for so long -- not many cdn providers when amazon.com launched. Afaik akamai still has one of the biggest edge networks of all the providers.

We good

> corporate tone

oof, maybe not wrong though.

I don't look at things for a living, I trade time for money with the expectation that my time has a multiplier on revenue, profit, and team health/productivity. I guess I've seen enough legacy code at this point that I don't have any desire to change it just because there's something better, changing stuff that works has to be a reasonable balance between tech debt/maintenance/quality of life things, vs features/uptime/performance. Of all those things, features make the most money right? So why would I want to spend time refactoring things when I could make measurable, incremental improvements somewhere else? Spend all day in the same system? Sure. Drive by refactorings? Absolutely not.

So you would've spent company time rewriting working code to match your personal aesthetics?

Sounds like parent didn't have a reasonable structure in place to generate consensus amongst the org about stylistic preferences vs tech debt, and where developer priorities should lie.

There's some ego in both of your comments as well. Async is nicer looking that promise chains, but there risk in changing working code, no? Growing with an org means letting go of your old code but joining an org requires empathy and understanding for the old timers and their code babies as well!