module0000

>> 1. "Just following orders" isn't now and has never been a valid excuse

Yes it is, see: https://definitions.uslegal.com/c/corporate-immunity/

That said..I agree with the spirit of your post. The only officers that cannot receive corporate immunity are the CEO and CFO - they can be held liable in criminal and civil litigation.

I imagine the electric "bonus" at higher altitudes would be similar to a turbo prop's bonus. You can get more efficiency at higher altitudes, but it all goes away if you climb further.

>> My fuel not burning in my wings wouldn't change anything, as I'm constrained by takeoff weight not by landing weight

I realize every pilot's job is different...but it's routine where I've worked(not as a pilot, but as a LIDAR operator), to skimp on fuel so we could still make weight & balance with our equipment on board. I've never heard(same as you) of anyone counting on that decrease in weight from fuel consumption though.

>> what the end user does and does not do

You hit the nail on the head, I couldn't possibly agree more. People have to think(ahead - sometimes quite a ways) before they act.

For the most part...yes.

Also: This means there is enormous potential to pollute their signal with tons of false noise. I hope(dangerous word) that this has already happened, or is in progress.

`ip` and `openssl` are both mega-guilty of this! At least the man pages for the `ip` sub-commands are sanely named though..

example:

`man openssl` to find how to use `rand` sub-command, instructs you to reference `man rand`.

`man ip` to find how to use the `address` sub-command, instructs you to reference `man ip-address`.

You need a (good) programmer/architect for this to work in my experience. If you don't have someone who can accurately keep the entire 500-piece workflow in his/her head, success is much harder to achieve. If you have that person though, the 500 developers will feel very focused, and you end up getting where you intend to go. That architectural role is clutch from my experience.

I get this experience using non-netlify-specific tools and processes already. I've also been doing this type of work professionally for 15+ years. If I was just starting out today, netlify would be a huge time saver, at the cost of a ton of knowledge you gain doing it yourself.

"But wait...there's more". If you're a new to development or operations, you might be tempted to use something like netlify. If your project has a high probability(>75%) of generating real income, then DEFINITELY use netlify. Anything that stands between you and deployment is costing you money. But... if your project is a hobby or non-serious-revenue-generating endeavor: please please please do it yourself. Learn apache syntax, learn nginx syntax, explore why `setenforce 0` is for hacky amateurs. You'll learn marketable skills, that will help you in your future career endeavors.

Netflify creates a skilled "user of netlify". Doing it yourself creates an "engineer". Which of those two would you rather be?

To the Mint guys: thanks! I don't use Mint, but I have in the past, and hundreds(thousands?) of people try it each day. Packaging open source software is a labor of love, and the community appreciates the work you are doing. No one ever says "good job!" when it works, but they raise hell when it doesn't.

Keep doing what you are doing, because while you may not get to perceive it often: people really, really, really appreciate the fruits of your work!

My post is only concerned with income tax. Government revenue up until that point had been provided by sales tax and tariffs. Income tax for 99% of Americans did not exist. Income tax is just another revenue stream, promised to be temporary. This isn't a general gripe about taxation, touching anyone's bank account, or generating revenue. There is zero misunderstanding of economics. The post was about a special tax for the general populace, that was introduced as temporary. That "temporary" part is a lie.

Day trading will teach a very similar lesson, in no time flat :)

>> Fuck the Vessel

Or, the author could do something about it other than whine. Make an ADA case regarding the limited floors accessible by elevators for instance - that's a freebie.

Presumably he means a noise-laden prospectus detailing the financial instruments in use for a particular fund. If you have a money manager, are you paying him/her to read that paper, and it's not millions of pages.

They look something like this...think of it as a set of rules for what the manager does with your money:

1) We invest you stocks/bonds rated <N> and above

2) We exit positions under <XYZ> circumstances

3) We enter positions under <ABC> circumstances

4) Past performance by following rules 1-3 is N%

No one failed to read these in the past, instead they focused on the potential profit, which blinded them to the potential downside. This is an investing 101 lesson, that continues to be taught to money managers each time their profit chasing occludes their risk management.

If you, a regular working class citizen, were burned by this(perhaps in your 401k), then it's worth reading the prospectus your fund manager sent you. When you see the list of funds included in your fund, you should have received a prospectus for each of those as well. Look for which funds make up the majority of your funds holdings, and read those prospectuses. If you find(and are uncomfortable with) one of those funds being a triple-leveraged ETF backed by 30-year mortgages, then you should talk to your fund manager about that.

>> Animals also take care of their young, they often mourn those who died.

Many animals also eat their young. Taking care of their young is just as ingrained in their evolved behavior as eating them.

Otherwise, I agreed with the rest of your post. The whole "do <x> organism 'love'" concept is a bit of a mind bender as usual.

>> We, as beings, are irrelevent: just hosts for a game that is being played at a different level.

Careful there, you'll bring out a whole cadre of people dragging you over the coals with that sort of opinion. They'll call you "godless" or something else, which translates to "I can't debate your opinion, so neener-neener".

>> It rather surprises me that software, a creative and digital medium like the above, is not futile and that you can still make a good living at it.

Anyone can write a story, create a drawing, or take a picture. It may be a bad story, a crude drawing, or a poor picture, but they can be done. However...software cannot be made by an novice. You can't wing it, have beginners luck, or stumble through it. No amount of "can do attitude" will make your code compile. Hence, you can still make a good living at it. If writing software was easy, everyone would be doing it.

I haven't experienced this failure with AWS. I've had good experiences with both GCP and AWS, and a handful of terrible experiences with Azure. I don't know your particular use-case, but I end up being clean-up for AWS disasters, and each one's root cause was poor planning and/or execution. Likely the result of an over-ambitious employee or contractor trying to implement by the seat of their pants.

Holding politicians accountable for their actions is very difficult in practice. Occasionally someone pulls it off though, from a book depository window.

The internet needs more of you. Thinking about your problem and a question to solve it leads to introspection, which is sorely lacking in most StackExchange questions. Most posters just let their stream of consciousness out, post it, and curse the lack of answers.

>> I have found myself flying the black flag again

I'm in the same boat(no pun intended), and also still pay for the subscriptions. I thought that more streaming services and more maturity(time passed) meant this situation would be improving - not degrading.

Apache is a robust piece of software, capable of more than the vast majority of users ever suspect.

That's fantastic! I was never able to hold over long periods myself, but that's an excellent success story you shared.

At times like now(bullish), do you continue to grow your position or wait for dips? I think there is great long term profit to be had in people allowing fortunes to grow in long term index funds, I just wish I was one of the people who could take advantage of it. My niche revolves around VIX futures contracts and their effects on equity index futures - so very short term(intraday).

Trend following is exactly what it sounds like. Pick a trend(over a time frame you choose, using a set of indicators you choose), then join the market on the side of the trend. To be successful, you must join the trend early, and be vigilant and disciplined enough to cut your losses when your trend fails to gain momentum and/or reverses.

I disagree - if "The act of you buying drives prices up", then you are making the market, not speculating about the future.

Trying to predict markets has a high risk of ruin.

Commodity futures trader here... this article reminds me why I got into futures: because I don't have patience to hold positions for days, weeks, months, or years. If that's what you are doing, and it's working for you - keep on doing it.

All the bloomberg articles in the world won't help you trade profitably nor consistently. At the end of the day(for me), success is a very repetitive set of tasks that rely on math and probabilities to succeed. Inside information is great(no really, it is great when you have it), but discipline was the most important skill for me to master. Before I began, I was sure I had it - and was entirely wrong.

>> The 50 year olds who complain are the ones that offer no value

So by your logic, anyone who is 50 or older - that complains - has no value? Real robust rating system you have there kiddo!

Enter something like..

>> while true; do rotate_mac_random.sh; done

Running on hundreds of devices with their radios turned up to maximum power.

I think the message is "don't trust yourself to interpret ads, it's really complex and you should just take your gospel(no pun intended) from us".

Not what I expected, it seems to me the CEO did the right thing. I'm not a customer of Instacart, my only knowledge of it comes from following the various HN stories about this whole ordeal.

The "right thing" he did:

1) Apologize, explaining that he made a mistake. Self-deprecation is good here.

2) Make it right, not just going forward - they are retroactively paying the delta to the impacted employees.

Hanlon's razor at work...

"Never attribute to malice that which is adequately explained by stupidity"