strickjb9

First NanoBanana came for the artists, and I did not speak out— Because I was not an artist.

Then Claude came for the designers with Claude Design, and I did not speak out— Because I was not a designer.

...

MinIO is a drop in replacement for S3. I plan on switching to this as soon as I can. For now, I just pinned localstack to 4.14.0

The non-answer is anything you want.

For me, it's my diet and workout buddy. It knows my goals, keeps me on track, does meal planning for me, gives me grocery lists, logs what I eat, when I exercise... anything I want so I don't slack off.

I've enhanced Nanoclaw quite a bit. Moved it to Apple containers (shipped with this Skill already). Then I wrote an API for Nanoclaw to use (food log, workouts, etc), then implemented long-term memory using LanceDB (because I was tired of repeating myself!).

This reminds me of this post from 2013 -- https://mikehadlow.blogspot.com/2013/12/are-your-programmers...

Essentially, there are two parallel teams, one is seen constantly huddling together, working late, fixing their (broken) service. The other team is quiet, leaves on time, their service never has serious issues. Which do you think looks better from the outside?

Real question - are you not worried about access to /mnt/c ?

Adding to this: it's not just that the apprenticeship ladder is gone—it's that nobody wants to deal with juniors who spit out AI code they don't really understand.

In the past, a junior would write bad code and you'd work with them to make it better. Now I just assume they're taking my feedback and feeding it right back to the LLM. Ends up taking more of my time than if I'd done it myself. The whole mentorship thing breaks down when you're basically collaborating with a model through a proxy.

I think highly motivated juniors who actually want to learn are still valuable. But it's hard to get past "why bother mentoring when I could just use AI directly?"

I don't have answers here. Just thinking maybe we're not seeing the end of software engineering for those of us already in it—but the door might be closing for anyone trying to come up behind us.

I know this is besides the point but translation libraries are perfect for this even if you aren't creating a multilingual site. You define your singular/plural forms in one place.

I hung onto a Blackberry way longer than I should have simply because I wanted physical keys. I'm trying to hang onto cars with physical controls as well. It seems like automakers are finally get the hint that people want physical controls again.

Great analysis - though I can't help but notice that 2009 is right when smartphones really took off (iPhone in 2007, Android in 2008, then mass adoption). The data showing accidents getting more deadly rather than more frequent actually makes sense if you combine two factors: phones causing more distracted driving incidents, plus our bigger American vehicles turning what would be injuries elsewhere into deaths. That could explain why it's US-specific - other countries probably have the same phone distraction problem, but their smaller cars mean less fatal outcomes. The distraction data might be weak simply because people don't admit they were on their phone after killing someone, but sometimes the obvious answer deserves more weight than we give it.

US East - it's down here

Completely agree. Nuxt is intuitive - convention-over-configuration and auto-imports remove a ton of boilerplate. The key is treating it as an app framework, not a backend solution - within that scope, it handles modern SSR/SPA complexity.

I'm baffled by the doom-and-gloom reactions here. Nuxt remains what it's always been: the best convention-over-configuration framework in existence. It's built on Vue which is opinionated as hell, and you get all the benefits of that. The "vendor lock-in" concerns are frankly overblown. At the end of the day Nuxt produces artifacts you can deploy anywhere - AWS, Cloudflare, your own infrastructure, or yes, Vercel. The alternatives (underfunded OSS maintainers burning out) are way worse than having a well-funded team with aligned incentives. If anything this validates that Nuxt is valuable enough for a major platform company to invest in. I'll take that over watching great tools die from lack of resources.

Don't trust cancelling your card either. I closed my account at Capital One, paid the final balance, and six months later I noticed a steep drop in my credit score. I had a $3 monthly charge that kept recurring even though I had closed my account.

Also, because my account was "closed," I didn't receive any statements notifying me that I was being charged. I only discovered this issue when my credit score dropped by 100 points.

Can we talk about having your account locked from a website because a bot attempted to login using someone's email address?

Agreed. Please get screened first. In Virginia, there are hotlines that you can call first and I'm assuming it is the same in every other state.

NY Times is giving free access to articles re: Coronavirus. You just have to sign up -- even via Social sign-in, it's two clicks.

I'm from the US, specifically Richmond, VA and we've been hoarding your warm air. We broke multiple heat records last week with 98F highs.

I'm not sure if this is a troll post. The "un"adoption of GUI frontend tools has nothing to do with job security. At best, it is a poor conspiracy theory.

There are great answers in these comments that provide good insight. This comment is not one of them.

As an interviewer, I don't ask this question but if I did then you could impress me by asking what a binary search tree is, then I would tell you, then you explain or write how you would do it.

Most of these interview questions aren't designed to be trivia. It's designed because your job IS implementation of technical and business problems.

I can relate to your last paragraph. I used to (and still) source dive to find good workarounds to library issues. But I never asked for permission, I just did it. I also delivered on time.

Nowadays, I'm a team lead and I am guilty of telling people "not to go there" (about half the time). It's funny because it actually conflicts with my opinion that I want people to dig in! The choice to "dig in" is a personal risk/reward. It's a risk that an engineer must take while practicing good time management. Asking your manager is akin to making them take that risk for you (the risk of wasted time, passing deadlines, etc).

My crappy advice is... ask for forgiveness, not for permission. If you're a good engineer, you'll come out on top!

     A reviewer's ranking is determined by the number of helpful votes from other customers.

At least for me, Amazon has been slipping. Product prices have gone up to close-to-retail prices. Quick shipping is great but the cost is baked in to the price more so than the annual Prime membership fee which has been used to extend other prime services that I don't care so much about. And now, I can't trust reviews.

Except, in this scenario, the cab driver is OKWU and the new york times is also OWKU.

It's reasonable for OWKU to make this announcement. They are laying out their expectations for their student body. It is inconvenient but students who dislike their position are free to transfer.

OWKU is a private institution and also a religious one (even greater protection). They are well within their means and rights.

I'm starting to think that feelings are being hurt on HN; hence all the controversy.

The author knew he was being provocative and later revokes his theory due to code not being able to evoke emotion. But I disagree, I've felt rage many of times while code reviewing.

Though for all their steps backwards, this is a big step in the right direction. According to them, they can now develop and improve upon a sole app for all devices. With this move, we'll finally start seeing more features and refinement. See -> "massively improved efficiency when it comes to adding features and fixing bugs"

Well yea. That's no different than that Amazon would have to develop an app for Roku or AppleTV.

Everything else remains constant, the only difference is supporting Chromecast is just implementing an API to your already existing application versus supporting another device is developing a whole new application for that device.

Third-party support is much easier to gain for Chromecast.

You can use your existing apps that you already have on your smartphone and have it "cast" to your TV. "Casting" is simplying saying... take this video link, and play it full screen on my TV. Or if you were using Spotify, "play my music through the TV, instead of through my phone". All the while, you're able to keep controlling the experience (pause/rewind/etc).

Chromecast is a different approach to extending media. Most devices (Roku, FireTV, AppleTV) all requires proprietary apps to be installed on their devices. For example, Netflix developers would have to create a port of the application to be used on each media device. Obviously (or maybe not), you can't install apps on a Chromecast. The only thing it does is receive an instruction from a device on your wi-fi network. That instruction comes from a mobile app (such as Netflix) that implements the chromecast api, a way easier approach than porting the entire application.

It's amazing and simple. Chromecast is on to something...

This is proof that you can counter-argument anything. Just proofread your damn resume (or engineer yourself a spellchecker).

That's called drinking the koolaid and it's very effective. Especially for establishing a career path. Once you "make it", you can loosen up.

If you're only applying for a paycheck and not a career then I agree. You should just keep doing what you're doing.

I doubt Twitter is making deep cuts so they can keep their friends. But it does help to like the people you work with.