HN user

theryan

36 karma
Posts0
Comments31
View on HN
No posts found.

The Mythical Man-Month by Fred Brooks is still a good read today and goes into depth about this topic. He called it the second system effect and considered it to be the most dangerous system an experienced developer will create.

His 'No Silver Bullet' theory may or may not stand up to what AI is doing today as well.

Some ventless dryers work really well. We have a Bosch 800 series and it works nearly as well and almost as quick as the electric vented dryer it replaced. On the other hand, we owned a Siemens ventless and I don't think it ever dried a piece of clothing.

We just migrated our massive WPF application to .NET 8 and there are a handful of libraries that are not supported or had to be replaced but overall it was surprisingly smooth. The biggest issue we have is that garbage collection seems to have taken a huge hit and there are bugs in the Microsoft WPF components (any sort of list view in particular) but it's all relatively easy to work around.

Having just done that on a massive monolith (10y+ codebase continuously developed) I would recommend biting the bullet and doing upgrading all of your projects at once to either .NET Standard or .NET 9 where applicable. Pause development of new features or just do minimal changes on the main branch. We had a ton of footguns (EF6 -> EF Core, WPF, WCF, file serialization, multiple web services) and we were able to complete the migration in 6 months.

The printers are fine but this post reminded me to cancel my ink subscription as I haven't printed anything in 6 months.

After my subscription date ends in March, they are charging me one final fee of $6.99 for the privilege of cancelling -- first time I have ever seen something like that.

FWIW, that is the same brand that I use and was specifically recommended for dry-eyes by my optometrist. I still wear glasses most of the time because my eyes also get strained from looking at a monitor with contacts in.

I'd recommend a trial of the lenses to see how they work for you before committing to a bigger purchase.

Yes, it is still 100% possible with the real Chromecast. My TV also has an option to cast to it (not sure what it uses under the hood) but it is similarly restricted.

Is there a replacement device out there for the ability to cast a tab or your full desktop to a TV? We use this functionality all the time and I would rather not deal with HDMI cords.

If you buy a 1/4 or 1/2 cow around here (MI) that is anywhere between $400-$1200 which should feed a family of 4 for about a year. That's getting you a humanely-raised cow that is significantly higher quality than what you would get at a grocery story. It works out to be slightly more expensive or on-par with the grocery store price but you do need a chest freezer.

I used to love my Chromecast but I feel like it's gone downhill significantly. The amount of bloat and ads when you fire it up is annoying. Thankfully there is an 'Apps only' mode now but you are still plastered with ads before you can select an app.

The create account page seems to have incorrect form settings at least for Chrome.

The email field prompts to create a new password (and generates it there) and the password field there is no prompt.

Diesel trucks tow heavy equipment (10k+ lbs) very fuel efficiently which is a common use-case in the states without needing to resort to a semi. Where I live a large number of people also own travel trailers and boats, which also lend themselves to diesel pickups.

I own a smaller truck myself (Ford Maverick) and tow a ~3000lb trailer with it regularly in the summer. My fuel economy goes from 30 mpg -> 11 mpg while towing. If I had a diesel, it would have virtually zero impact on mpg.

Many years ago I was connecting APIs from ~100 companies into our application, they all essentially did the same thing -- update information in our system based on a tracking number. At this time, about half were web APIs and half were WSDLs. The WSDL APIs were by and large the easiest to work with, I didn't have to write much of any code. On the other hand, the web APIs required me to have a custom flow for each and every one and they could break at any point without me knowing.

I've seen a lot of hate on WSDLs throughout the years but they were honestly really productive for getting work done.