steeeeeve

If you have an algorithmic edge, eventually it will stop working. If it's a really good one, your trades become someone else's edge. The market is constantly changing and active traders are constantly looking at what's going on and trying to take advantage. The more I looked into trading, the more it was just a sea of "Use these charts", "don't really trust these charts", and "once you lose a ton of money, you'll get a feel for things"

I won't downvote you, but I will die on the other hill - the one over there that has a guy sitting down with his arms folded sporting an angry face every time someone something positive about WSL. There's at least three of us on that hill. And we're not going anywhere.

I too went down that rabbithole. Haha. Anything around that time to get an edge in a fantasy football league. I found a bunch of historical NFL stats pdfs and it took forever to make usable data out of them.

Government is the worst possible solution to every problem.

(not an attack on you. I have to say that every time I see someone say anything along the lines of "the government should do it")

I would agree with you. Dating app data might not be legally protected like some PII out there, but there are easily foreseeable bad consequences from compromised dating app data of any kind. Security should be accounted for from the very beginning.

Old school Zeiss glass is like butter for any camera body. My dad told me to stick with Nikon and spend my money on lenses first. He was not wrong. You can put 25 year old professional lenses on a mid-market Nikon body and the images will be stunning with very little effort.

This is one of those decisions that confuses you when you're on a mac and things just don't work how you'd expect.

This is the kind of thing I would have expected to read in 2600 back in the day. And why I _always_ looked for 2600 at the bookstore.

I find this odd because that's exactly how I thought viruses worked when crossing species and I have no background that would lead me to that conclusion and have almost nothing in my life that would make me ponder such a thing.

I feel like someone explained this in the 80s to me.

Who buys a drill not strong enough for a hole saw? What does that even look like anyways? An electric screwdriver?

That's brilliant

global from day one and circumvent government interference

--- There are banking laws all over the world that need to be considered and followed, the US in particular has a set of banking laws that differ in each state unless you are an actual bank that follows federal regulations.

Ignoring or being purposefully ignorant of the laws is a bad path.

The selling point of Rust was that it protects programmers from doing dangerous things.

The BFF pattern is just "mostly microservices dedicated to a particular client type".

It makes sense when you have drastically different needs between a desktop client and a mobile client (or maybe for a kiosk client or POS interface)

Hosting a microservice is cheap, it avoids unnecessary workload on backend data stores, and teams can operate with more autonomy if they don't have to cooperatively update APIs in coordination with other groups with differing priorities.

This article really just reads like "I figured out how to do authentication with keycloak using OIDC"

Today it is. Tomorrow everyone will look at it like Wish or Temu.

You could displace DeepSeek pretty easily with Amazon Mechanical Turk.

This really seems to me like a big warning that says to avoid hiring people that were laid off.

Better advice. Be who you are. Work for and with people you like. Do what interests you where you are valued. You will spend a lot of time at work. Try to make sure it feels good.

Oddly, yes. A regular bike accident would have been covered. And it would have been covered on a moped as well even though she's too young to have a license.

I _just_ went through this when my child had an ebike accident (AAA, southern california). You need specific ebike insurance. Auto/homeowners doesn't apply for different reasons.

So having clear requirements, a focused purpose for software, and a clear boundary of software responsibility makes for a software development task that can be accomplished?

If only people had figured out at some point that the same thing applies when communicating to human software engineers.

If 150k will get you through six months and then some, take the time. If not, evaluate your spending and increase your savings so that you can take time off.

If you are taking time, expect that you will need or want a new income vessel when you come back, and that will take time to put in place. Few career paths will let you take any significant time away and just jump right back in where you left off.

Also, if you are burned out, start thinking of a clear exit plan.

paywall

Mental health challenges in the bay area tech industry are real for a wide variety of reasons. There's a bigger push in silicon valley for work life balance and mental health care than anywhere else I've been, but more people with serious issues there than anywhere else I've been as well.

Imposter syndrome is high among engineers of all levels of experience and ability. Engineering has it's own set of pressures. Then you add in all the other reasons people can feel stressed or pressured and all of the bay area specific reasons those things are amplified. It adds up.

You would be surprised how many brilliant and highly capable people have broken down. For anyone out there feeling like they are all alone - don't. Even if all the people around you seem happy and confident, I guarantee that a larger portion of them than you realize are struggling.

I learned a trick with flipping coins from a barber at my grandpas shop when I was probably 6 or 7. Since then I've always been able to flip a coin and determine what the outcome is. It's really just being consistent with the flip and the catch.

Honestly I got about a quarter through the article before I decided it wasn't written by a human.

You know there's a software engineer somewhere that saw this as a potential problem, brought up a solution, and had that solution rejected because handling it would add 40 hours of work to a project.

Create a paper trail. Crank out tickets. Document everything. Hit the numbers.

No.

Add value. It's not your job to quantify it. It's not your job to create an understanding of what you do.

If your organization or your manager specifically does not recognize your contributions, be happy to move on.

If you get feedback that says "we recognize your value, but we really need x" that's reprioritization. Respond appropriately. If documenting your value in that way prevents you from actually being valuable, be vocal about it. If it's just a pain and you can still do your job, then suck up the pain like everybody else.

I've been in large engineering organizations. They want to quantify everyones value so that there's "fairness". BS. There is no large scale way to determine of a software engineer is good at his job or productive. Yes, some people have more opportunities to affect the bottom line than others. Yes, some people have easily quantifiable work. That's how the world works.

Have they figured out a way to recognize and effectively incentivize good teachers? Not in my 51 years.

Have they figured out a way to recognize and effectively incentivize good CEOs? Nope.

What makes you think that we should be that easy to stack together and figure out?

I'm senior. I'm experienced. I'm valuable. I'm not always right, and I am not always valuable. In the end, I've had a good and healthy career focusing on the things I'm good at and the things I care about while letting other people figure out if I'm worth what I cost to keep around. Some of those people made good decisions and some bad ones. I still moved forward and my kids have always had food on the table. I say that's enough.

Get skinny and keep my brain? No thanks. At some point this roller coaster ride needs to end.

There was a lot of public debate about this at the time. Kahle's argument made sense.

Sigh. Newton. So far ahead of it's time.