Hacker News new | past | comments | ask | show | jobs | submit | kaydub's comments login

It honestly gives me a warm fuzzy feeling thinking about how blazing fast personal computers are these days.

It's instantaneous compared to the 90s and even the 2000s. It wasn't until 2010-2012 that I remember switching to SSD, which is when I feel the turning point was.


I had a netbook around this time and putting an SSD in it was a HUGE upgrade (similarly the upgrade from 2 to 4GB RAM).

I still have it, and when I put an 32bit version of Debian on it a couple years ago, it was molasses. Somehow I used it for years with no complaints.


When I upgraded my Windows laptop (running Windows NT) from something like 64 MB to 128 MB, it made a huge difference. Most of the benefit was that it stopped using swap. Sadly, I was borrowing the the DIMM from my boss and I had to give it back. It was like flying back on coach after getting there in first class.


I have a pretty poor sense of smell and I've had terrible food poisoning a couple times in my life. If it's past expired I throw that shit out. I make sure to do a decent job meal planning to control waste.


This sounds like a nightmare


Nope, this sounds like really really common problem outside of top 500 IT companies.


I have a workshop laptop, Lenovo Thinkpad X1.

But I did have a System76 until I fell down the stairs and it came with me.

The System76 is built for Linux Pop OS but the Thinkpad ran Ubuntu fine... it may have been Kubuntu even, I can't recall.


We're in the business of making money. Our product makes the money. Not our skills and abilities to manage hardware and IT infrastructure.

They have a decent business case, but I don't feel like they executed well to meet the real objective. They don't want to be in AWS since they're an uptime monitor and they want to alert on downtime on AWS. But they have a single rack of servers in a single location. A cold standby in AWS doesn't mean a ton unless they're testing their failovers there... which comes at quite the cost.

I've worked on-prem before. Now I work somewhere that's 100% AWS and cloud native. You'd have to pay me quite a bit more to go back to on-prem. You'd have to pay me quite a bit more to go somewhere not using one of the 3 major clouds with all their vendor specific technologies.

The speed is invaluable to a business. It's better to have elevated spend while trying to find good product market fit. I didn't understand this until I worked somewhere with a product the market wanted. > 50% growth for half a decade wouldn't have been possible on-prem. > 25% growth for a full decade wouldn't have been possible on-prem.

I've been with my current company from $80MM ARR to $550MM ARR. We've never breached more than 1.5% of income on total cloud spend. We've been told that's the lowest they've seen by everyone from AWS TAMs to VC/PE people. It's because we're cloud native, we've always been cloud native, and we're always going to be cloud native.

You've gotta get over "vendor lock-in". With our agility it's not really a thing. We could move to another cloud or on-prem if we really wanted. Wouldn't be a huge problem moving things service by service over... though we've had a few more recent changes that would be troublesome, we'd be able to work around them because we're architected well.


Don't forget, some of the worst outcomes per dollar spent


But best outcome if you do have the money. I've been waiting 38 months for an elective surgery in Canada.


Canada is all kinds of mixed up on this front. On paper healthcare is pretty much perfect but if you dig in a bit you find a whole raft of things that simply don't work. Canadians don't go bankrupt because of a medical mishap, but they're much more likely to die while waiting for something they need.


As someone that works somewhere that goes AWS first and is 100% cloud native, you'd have to give me a massive increase in salary to deal with hardware.

Been there, done that, don't care to return to that life.


Kevin still red teamed all the time through his other company.

I seriously doubt he ever tried to hack SCN.


I assumed it was due to the height of the ships that typically passed. Probably costs more to build the bridge higher so you don't have to raise it as often, so they fight about lowering costs and minimize the number of times they raise the bridge.


I can work harder and take on more responsibility for a $20k-$40k increase in salary.

Or I can take it easy, let some of the team take on some of the load, and make sure I do enough.

Working harder and working for someone doesn't make you rich or wealthy. It can make you comfortable. I'm already comfortable.

The real money is in ownership. So I'll put less hours in working for someone else and keep my mind fresher and more open to opportunities of ownership that may arise.


Also, it't not even a bad deal for employers. Binding time spent to money taken home like everyone is a blue collar worker where output is approximately linear (or, an a moving assembly line, actually ideally linear) doesn't work for knowledge based jobs, especially if they involve creativity. Productivity goes down the longer you work.

I switched to a 32 hour week and I don't feel like my productivity is impacted beyond not being able to attend some meetings, most of which were superfluous anyway. If it's really important I will make the time elsewhere, but that has happened once or twice in ~8 months.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: