It’s crazy how direct Remarkable is about what their devices are and then the number of people who buy them and wish they were something else.
I understand it probably comes from the original motivation, but the name seems unfortunate since you can totally use it to convert to Spotify from e.g. iTunes if you do have Spotify but just not one of the dozen competitor subscription services
It's not wrong to wonder about your career trajectory, but it's telling to see someone pretty nakedly talk about optimizing for changing their level at a company, before they've even landed there and evaluated if they can help / how they are helping their team. I'm not naive, and I recognize those people exist and can acknowledge that they can do good work. But if someone came into my workplace with the mindset of "aggressively [seeking] to showcase my leadership within the first few weeks" and their goal was going "from Senior Manager to Director in ... 12 months", I'd be skeptical that they weren't going to damage peer relationships and optimize for being recognized at the expense of their direct reports, even if I thought they could be a valuable asset in the short term.
And then of those underperforming teams, what percentage of those would the team members identify themselves as part of underperforming teams?
Personally I can’t get enough of AI and AI hype. It’s nearly certainly going to be the biggest technological leap forward of my lifetime and it won’t be particularly close.
https://opentext.wsu.edu/theoreticalmodelsforteachingandrese...
OK so just avoid this tendency.
This is definitely not a universal truth.
I know that if I had done better in every interview then I would’ve moved ahead and gotten the job. I guess that’s a different way of saying I was “bad” (not good enough). And it doesn’t affect my motivation in a negative way. I find that it actually helps me want to improve more.
Dead Comment
For large pieces of work, I will iterate with CC to generate a feature spec. It's usually pretty good at getting you most of the way there first shot and then either have it tweak things or manually do so.
Implementation is having CC first generate a plan, and iterating with it on the plan - a bit like mentoring a junior, except CC won't remember anything after a little while. Once you get the plan in place, then CC is generally pretty good at getting through code and tests, etc. You'll still have to review it after for all the reasons others have mentioned, but in my experience, it'll get through it way faster than I would on my own.
To parallelize some of the work, I often have Visual Studio Code open to monitor what's happening while it's working so I can redirect early if necessary. It also allows me to get a head start on the code review.
I will admit that I spent a lot of time iterating on my way of working to get to where I am, and I don't feel at all done (CC has workflows and subagents to help with common tasks that I haven't fully explored yet). I think the big thing is that tools like CC allow us to work in new ways but we need to shift our mindset and invest time in learning how to use these tools.
But you’re saying it can be half-decent?
The problem is that about 75% of HN commenters have their identities tightly wound up in being a (genuflect) senior engineer and putting down PM/tech-lead type roles.
They’ll do anything to avoid losing that identity including writing non-stop about how bad AI code is. There’s an Upton Sinclair quote that fits the situation quite nicely.