uzername

At work we call this implicit steering. To use webdev metaphor, if a non-technical person describes making a web page with a big block at the top and some things to click on and then my pictures below that, that will eventually get somewhere. Meanwhile, if you know industry jargon, you might describe a hero, with call to action buttons, and then below a 3x3 grid of images of my portfolio photos—that's likely going to generate something entirely different and likely richer. It can assume things about you (it doesn't think), it can ask you specific questions a web personal might know, it can infer domain context that is otherwise omitted with a basic conversation. Everyone wants to capitalize on corporate vibe coding but the tech literacy is hardly there, let alone more advanced topics.

I would love to hear more about your advice and the coaching you are giving to management. We also have a strong push to prove evidence of climbing productivity with clearly state future staffing goals. I would like to advocate for this, at even partially, enhancement and quality of life improvement for IC folks.

I use a CICD tool called Vela.(No relationship to the k8s tool also called Vela.) It's mostly docker all the way down. Reminds me of bit bucket pipelines. Maybe worth checking out if GHA is just too opaque.

I had immich running great for a while, maybe for months. It would seamlessly sync photos from phone to local home server. I was going to setup nightly outbound sync too (1 is none, 2 is some).

I updated the container for usual appliance maintenance. Entire thing is toast. Metadata files can't be read, mounted, permission issues and more. It's been four months since.

On some previous version of Samsung's UI, they followed the Apple trend of splitting the swipe down interaction, one side for notifications and one side for setting. It was extremely confusing. Luckily Samsung included a toggle to revert that change.

Lurking, occasionally commenting, rarely posting. I've read HN everyday since I started working in the industry since March 2016. I appreciate what HN is and the shared culture.

Thanks all, and have a great day.

The loss of Google Reader really does feel like the beginning of the end in retrospect.

Missing search and weird ssh control character issues are my blockers. It's great otherwise!

My team is worried about that too. We've been a java and spring shop for years. We're looking at micronaut, it's similar enough.

When I had someone from another team take a look at broadcom and what they could do to spring, they said the licenses are permissive, it will be fine. Likely not that simple.

I've been paying for NYT for five years. I remember the NYT paywall before that. I've been interested in local news so after my 5th hit in recent memory hitting my local newspaper's paywall, I finally bought a year subscription.

On the other hand, my mom used to read the physical newspaper. She would buy it at the gas station. She refuses to buy any type of news online. So it's unfortunately all Facebook and YouTube news shorts slop for her now.

We used SML in my undergrad compilers course. I really loved the language and I started exploring other languages outside of class after that.

I've used mine as a personal knowledge base that happens to be public. It's silly how many times I've come up in search results months or years later after I'd forgotten having solved this problem before.

A semi-related story: Freshmen year in college, I was about a week ahead in the sci curriculum and I blogged regularly about novel errors I encountered and how I fixed them. During lab late in the semester, I happen to look up into the next row. I found the duo there reading my blog post.

It's unfortunate that the pbtest.org tool links out to a service with an expired cert.

That's probably the same bootcamp that my friend took. I was really excited for them, but unfortunately the bootcamp was of poor quality. No enforced gates, no meaningful feedback on code quality, too little explicit mentoring on tech skills and soft skills, no support finding work at "graduation". That was in 2019, before the markets churned. Those courses were branded as UMN but we're reskinned Trilogy bootcamp materials, and there was ultimately no UMN staff involved except maybe an admin somewhere.

Good riddance indeed.

Our design team has been charged with making a refreshed, design system. That's all in Figma so far. Nothing has touched a real browser or a real device (tablet, phone). I've coached them to _try_ their design system in code sooner than later, to see if it even makes sense in real scenarios. I've coached them that they'll need multiple implementations.

At a technical level, there have been previous attempts for these shared design libraries with reusable components. We're mostly using react. The first generation the design system ended up putting all of these complex components like "Product Display" or "Order Builder" and so on, all driven by props. That resulted in prop explosion and increasingly unreasonable maintenance burdens. It also became effectively locked to the versions of React that were available when it was made - teams could not afford to upgrade either their own apps which caused the library to freeze. A second generation of repeated many of those same mistakes, not composable enough, too tied to a definite version of react, too tied to a definite version of mui, and so on. The tech piece, in addition to the people-problems, is just as hard and important too.

Adoption will be driven by funding, value and time.