Hacker Newsnew | past | comments | ask | show | jobs | submit | atlasduo's commentslogin

Easily explained: when times are tough, delivering growth naturally is hard. Squeezing the customer is the lowest hanging fruit.

Sure, long term reputation is severely damaged, but why would decision makers care? Product owners interests are not aligned with interests of the company itself. Squeeze the customer, get your miniscule growth, call it "unlocking value", get your bonus, slap it onto your resume and move on to the next company. Repeat until retirement.


When times are tough, accept less growth (or sometimes none) so that when times get good again or someone builds a competitor, all your customers don't leave you.


The real big brain move is to be your own competitor, so you extract value from customers either way. If they don't switch, you get to extract value via planned obsolescence and plain old extortion. If they do switch to avoid the extortion, you at least get to keep the price of their new NAS, and you weren't likely to get the extortion money anyway.

America has thousands of food brands but they're all owned by about 6 companies.


This is more about EBITDA.

Serving the needs of customers (practically the quality of the product) sits down in the list of importance. Sales strategy, marketing, PR, organizational culture, company values, ..., basically the self-serving measures come all before that.


I guess times have been tough for a long damn while then…


This is depressing, but feels accurate. How do we collectively get out of this mess?


I think there's actually no point in being profitable, it always seems to lead to even more greed, power and corruption.

Better to have a heart, care more about your customers, don't put profits first, but still make enough to keep the lights on.

I think that would make everyone happier anyways.


Don’t give them money.


Capitalism. It’s why we can’t have nice things.


Capitalism is the reason we have so many nice things. :)


this... it's the only reason technology has advanced so quickly


So, it is "buy made in US products or face sanctions" now? This will end well, I bet.


You are not supposed to treat it as a gospel, following every guideline. Instead, it is a collection of ideas presented to you, so that you can decide if you want to use them (or not!) in your day-to-day work.

In general, software development is not a profession where you learn how to do things and do them, occasionally refreshing your skills. It is a perpetual problem solving field (not without its routines), and a continuous journey. Creativity, personal opinions and exchange of ideas play an integral role in this profession.


User account is an interface between a User and a system one interacts with. If you book a flight, a user is created - no way around that. So, what you essentially demand is to NOT provide you with a user interface to interact with the system. Instead, you would resort to interface through online/offline/phone support.

Your demand boils down to having less options to do actions with the business. Options that already exist and come out of the box.

Having an account is not as scary once you realize what it is and what it represents.


> So, what you essentially demand is to NOT provide you with a user interface to interact with the system.

No, I’m requesting, or demanding if you prefer, the choice. An account is a user convenience, not a business necessity. I’m asking why it is reasonable to force customers to create an account to book a flight?


I am not the original commenter, but when you are firmly set to work with a hammer, everything starts to look like a nail.


Because a lot of people are still in denial, not believing this is a plausible scenario, just like they were in denial that a large war might break out in eastern Europe "because we don't really do wars anymore".

Worst part is, apparently, lots of politicians at the wheel also believe "it won't come to this".

Reality is going to hit like a truck.


This. But reality will hit rather like a missile.


like a JDAM


You should practice your trolling skills. You are being way too obvious. At least, I hope so, because if you actually believe this, then this is something only a professional can help you with.


This has been going on for a while. A year or so ago I remember Tailscale was blocking downloads of their applications from Russian IPs. HTTP 451 means "unavailable for legal reasons" so I imagine this is Tailscale trying to cover its soft spots.


They deployed the 451 during the last 2 days of August 2023 [1][2].

[1] https://github.com/tailscale/tailscale/issues/9158

[2] https://www.reddit.com/r/Tailscale/comments/1672n6k/


DERP and login/control servers reply with 451 since yesterday. Previously, only pkgs were affected.


Could you elaborate? What kind of malware was pre-installed?


Bladabindi and Redline on two of them. Those were also configured by someone to disable alerts and scheduled scans in Defender. On the third it was something to do with bitcoin / wallet stealing and I don't use bitcoin. I can't remember the name. I just boot them up long enough to know it isn't DOA then eventually wipe them with Linux assuming I even keep the tiny NVME they come with. I started running scans after seeing the mini-PC malware issues in 2023 to let others on Amazon know what I find and to steer very clear of those vendors.


Tags can be changed. To actually pin the source code revision, they should pin to a specific commit hash.


Sometimes they get changed for a silly reason (someone just didn't think of the consequences). Sometimes they get changed because they have to - if I remember correctly it was Asterisk that needed to drop some copyrighted music samples and retagged old versions.


That shouldn't matter, then; it should just result in a new release.


You can't distribute the old versions with copyright violation. The problem doesn't go away just because you released a new version.


But then you have two different things (with and without copyrighted data) both with the same version. Wouldn't it be better to just remove the bad release, and publish a new one? They are, after all, not the same things, and shouldn't have the same release.


Good point, that would make sense. But same difference. Why is that not how it works?


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

Search: