4,247 karma · joined February 17, 2015
I've had success playing the markets in these specific cases. I did fritter away a lot of my gains from the financial crisis thinking I was a genius market timer. But I learned my lesson and didn't waver once I jumped back in after covid.
In both cases I got out before a bulk of the crash and timed the bottom almost to the day. Lucky I know, but I had reasons for both. For the financial crisis it was when Bill Fleckenstein closed his bear fund and put it all in MSFT. For covid it was when it looked like the lockdown was working and NYC hospitals weren't going to completely fall over like Northern Italy or Wuhan.
For any non black-swan scenarios, I assume I'll never get one up on the masters of the universe and just leave everything in blended age-appropriate funds.
I'm very concerned about an AI crash and the future of white collar work in general. But it feels more like a slow death to me than a black swan. So I'm just hedging with bonds and cash and stocks that hopefully don't crash as hard in a recession.
But what happens when new requirements come in for just one of the things? If you left them separate, it's an easy change of a few lines. If you created an abstraction, now you either have to add a bunch of if statements, or spend time undoing the entire abstraction that you spent X amount of time creating.
If a bunch of other code has built up around that abstraction, undoing it can become a serious chore. I've worked on apps that had way too many premature abstractions, and we just had to live with it because it would be too risky and onerous to try to undo them.
In my experience, it's generally an order of magnitude easier to add an abstraction to a mature app when you get tired of making changes in multiple places, than to remove one when the app evolves and you realize these things aren't actually that similar. Also when you wait to abstract, you might see a better way to do it, or how to reduce the scope so that you're using composition to share a bunch of smaller pieces vs. sharing the entire page/object/interface/endpoint/etc.
Obviously, this isn't a blanket rule. There's an aspect of soothsaying to guess which things might diverge and which are likely to spawn a lot more similar copies.
There's also an art to how you do it. It's important to build up trust that you won't tell the client something is impossible or really hard just because you don't want to do it. You try to explain to them how much complexity this is going to add, how that will make it harder to add new features in the future, and most importantly offer some alternatives that get them 90% of what they're trying to do. Most clients will appreciate that approach IME, especially if you've already thrilled them a few times.
This is one of the reasons I'm not so worried about Claude taking my job in the immediate future. But I am still extremely worried about the industry as a whole and by extension the future of the middle class.
The best is when a site uses the exact same date picker for birthdate as for some date in the future. Yes, I'd love to click backward 50 years to get to my birthdate. Thank you for reminding me how old I am.
Maybe this was true when Programming Perl was written, but I see the opposite much more often now. I'm a big fan of WET - Write Everything Twice (stolen from comments here), then the third time think about maybe creating a new abstraction.
It's tough to remember the commands for thumbnail view since you only see them for a second. Maybe a little chicklet that stays in the upper right would help.
If I was doing this, I would start in thumbnail view, then go to slide view when an image is clicked. I'd add clickable left or right arrows in addition to the key navigation, since it won't be immediately obvious that the viewer is in slide mode. Maybe an up arrow, and also the escape key, would take the viewer back to thumbnail view (instead of the chicklet I mentioned).
As far as the image sync I'm not sure how that works. Maybe NASA has an API where you can filter on keywords? If not you might have to just keep syncining until they're done posting pics of Artemis, and manually curate them.
If you're looking for future expansion, you could add other categories too, maybe groups of thumbs based on mission or something.
There was no HTML email in the early 90s. The font was the display font of whatever you read it on. Sheesh NYT.
When I do code, it's almost always something novel that I don't know how I'm going to implement until I code a few pieces and see how they fit together. If it's a fairly routine feature based on an existing pattern, I assign it to one of the other devs.
You just described 90% of young country for decades now. I keep waiting for its fans to get tired of being pandered to with formulaic lyrics, but they seem to be an endless well.
But it fits with the general trend of MLB being openly hostile to their fans for a while now.
This happened a long time ago in the US. Drive through California's Central Valley sometime and sample the fruit sold fresh along the side of the road. It's a completely different experience than the version you get at Safeway.
The recent article where the AI companies are paying experts in the field to help train the models makes me wonder if they're also manually fixing a bunch of post-processing errors as they come up.