sbdncuvh

Every single HP, Acer or Asus laptop from those days I saw in the wild had major issues.

I'm not sure what the cause was. Could have just been users.

Too cheap / uneducated to value extra ram or storage, then as a result of it being crappy and slow they didn't care about it and ended up tossing it around. Them on top of their other issues they would have problems like busted screen hinges, batteries that don't charge. Mouse pads that don't work etc.

Every ThinkPad I saw tended to be solid without any issues.

Or the IT industry is just full of participation trophies and the new grey beards just cbf participating in a toxic community that can't handle a single opinion outside their own narrative.

So simple you can fix the problem in one line but me pointing that out as bad design is arrogance. Gotcha.

Ah yes. Configuring my scroll wheel sensitivity per app just like hidpi. Just what I want...

I tried to transition from years of loose txt files to obsidian.

When I opened the folder the app showed me 1-2 files from years ago.

Apparently it only supports .md files.

I literally laughed out loud and deleted the app from my computer.

You've got a damn knowledge map but handling txt files is beneath you?

That app is doomed to obscurity.

You could start by saying smartphone, but that was probably intentional.

Getting off fossil fuels is a necessity. Don't kid yourself what the result of that really means.

"Transitioning to renewables" what does that even mean? Like it's so simple?

Solar panels aren't going to ship you cheap iPhones and mountains of plastic trash from china for pennies, nor will it fertalize your crops or maintain USD as the reserve currency.

Look I don't mean to be rude. I'm not a climate denier. I'm not even arguing against transitioning off fossil fuels. I'm just not naive about it. Poverty, starvation and mass death is the only way we transition off fossil fuels. That's if we're lucky.

> What’s the downside of getting off fossil fuels anyway,

Poverty?

I had to learn some low level memory models before I could really grok rust. I understood a bit of C++ but it wasn't until I found the talk about memory structures for rust/c++ that I really caught on. I can understand why knowing existing programming techniques might cause a struggle.

https://youtu.be/rDoqT-a6UFg

Your mistake was to pay the customs duties and receive the goods.

What you should have done was taken them to tribunal for the missing warranty item they owed you.

You can pair that with hefty fines. The US is in a good position to place them on international players too.

Want to work with USA companies? Great, pay your fines and you can.

This is unlikely the spam problem is too hard to solve at the small scale for you to ever be relevant.

We have a mix here in aus.

The recruiter does the recruiting and provides access to an umbrella company but it's optional and up to you. The umbrella company is a separate entity that provides the service to the recruiter, 99% automated so fees for it are basically nothing.

The umbrella handles witholding tax, super payments, pay slips and a few compliance things like confirming you've watched your OSHA video quota for the year.

Just what I want from my css frameworks. A sticky footer that doesn't properly stick on mobile.

I find there is a time and a place for this in your work though. You don't have to use obscure words nonstop, use them where people can learn or figure out just from context. Sometimes thats not possible but it usually is. If you think it isn't, maybe you've got a new writing skill to learn and improve on.

Writing for the reader is important if you want your work to be read.

Write to think all you want but don't expect other people to read your unedited drafts.

I hardly ever do unit testing. It's almost always integration testing with code that uses real implementations against a testing db. This is only possible because my code is decoupled in the right places to enable this sort of no mock style testing.

I don't strive for 100% coverage and I hardly ever do TDD unless I'm working on something hard to solve.

Tests give me confidence and results in less time repeating the feedback loop. I might have a slower "coding speed" but I have fewer regressions during refactoring. Less bugs to fix while iterating. And less back and forth with stakeholders to ship something. Overall I'm way faster with tests than without.

Why is everyone in this thread forgetting what tests actually do?

Tests force you to write better code. Code that is easier to change. Code that is more robust.

You don't need 100% coverage or perfect tests to gain this benefit.

A good test suite enables you to make large refractors safely and quickly.

The most scary refractors I've ever had to do are ones that involve large changes to code that has no tests.

Often those refractors that allow company level pivots require adding huge amounts of tests to a legacy code base before I can even get started.

Adding tests to code that has none is the worst. The code is coupled all over the shop and requires 100 times more mocking and stubbing to get under tests when you add this stuff retroactively.

Tests speed up development velocity and improve your codebase.

Just don't get stupid about it and you won't negatively impact startup performance.