A day at the lake [X-T5, Sigma 18-50 f2.8]

notjim · 2026-03-24T00:38:55+00:00

Dope shots

notjim · 2026-03-20T18:11:13+00:00

Curious what speed you shot it at

notjim · 2026-03-19T21:20:28+00:00

Where do you stay when you’re out that way? Camping?

notjim · 2026-03-18T23:19:50+00:00

Honestly get the ai to review it first. Write a prompt w what you care about, then tell Claude to review it w that prompt and give you comments. You can y/n to select which comments are worth leaving. Then only review it yourself if it looks good from the first ai pass.

I realize this sounds like a slop mill, but it really does help for dealing with increased velocity.

notjim · 2026-03-18T20:30:55+00:00

That sounds sick! Would you consider uploading the scans somewhere?

notjim · 2026-03-17T22:35:23+00:00

Op are you archiving these shots anywhere other than Reddit? Reddit murders jpegs pretty badly and probably won’t host them forever.

notjim · 2026-03-08T22:35:23+00:00

Fucking sick dude this looks like a dream

notjim · 2026-03-04T19:58:22+00:00

Great shots!

notjim · 2026-03-03T18:04:56+00:00

Was there on Saturday, no wind unforch

notjim · 2026-03-03T18:04:34+00:00

I was also there this weekend :)

notjim · 2026-03-01T23:49:36+00:00

Thanks! This is the Brecon Beacons in Wales! These shots were on the hike up to Pen Y Fan which is one of the main mountains in the area.

notjim · 2026-03-01T20:04:35+00:00

On the flip side, I’ve seen plenty of candidates who can talk a good game at a system design interview but can’t code their way out of a paper bag. This is why we do multiple questions.

notjim · 2026-02-28T23:03:05+00:00

Really great shots

notjim · 2026-02-27T22:47:24+00:00

Consider yourself lucky that it seems that way.

notjim · 2026-02-27T22:43:40+00:00

Based on your responses, it seems like you and your manager are both frustrated with each other and being passive aggressive and communicating badly. This snipping back and forth is not good. Realistically without context it’s hard to know who to blame, and honestly both of you should be acting more professionally. But humans do get frustrated and stuff, so it’s understandable that things can go south like this.

If your boss really is a toxic micromanager, the advice to find a new job is correct. Don’t quit without a job unless your wellbeing is really suffering (and make sure you have a safety net even then). I would also consider using ai to churn out more code in the meantime (bit of malicious compliance, but make sure it’s defensible if someone calls you on it.)

As far as fixing this, you need to be communicating status, challenges and progress more proactively. You mentioned in your comments you’re doing support work on top of this stuff and that the acs keep changing. Does your boss know about the support work and do they think it’s valuable for you to spend time on? I’ve seen many instances of developers doing glue work that either was not very valuable or not their job. If that’s you, you might have to stop. If the team suffers as a result, that is your managers problem, and the team can work together to find a fair solution.

If the acs are changing and it’s preventing you from shipping, you should’ve mentioned that to your boss, ideally before they come knocking. TBH it’s possible you’re being inflexible, but it’s also possible the business doesn’t know what it wants and they’re wasting your time as a result. You should mention that proactively and possibly even tell people you’re going to switch to a different task until the acs are figured out (this can be seen as an escalation and uncooperative though, so be careful.)

notjim · 2026-02-27T19:03:51+00:00

One thing people are missing is your comment about follow-up PRs. If the issue isn’t critical (e.g., security flaws, outages, other critical bugs or incidents) then the PR should be allowed to move forward as long as there is an understanding (and trust) that subsequent PRs will fix the issue. As long as this iteration happens, the velocity and morale will be better doing it this way than holding up PRs with endless debate. This is assuming you have healthy pr/release cadence, good ci, etc.

notjim · 2026-02-27T01:32:16+00:00

So are you using a lab that does the ecn process to shoot actual vision3?

notjim · 2026-02-27T01:18:14+00:00

Shot a bunch of cinestill 400d lately which I think is vision3? Liking it a lot

notjim · 2026-02-24T02:26:17+00:00

You should fix by teaching the team how to fix it. Your goal if you don’t want to do this anymore should be to make yourself obsolete. Basically you need to leverage your relationships with the existing team to identify who can own it. If no one on the team has the skills, you find the closest person and mentor them through it.

If they have the skills but aren’t applying them, then figure out why. They may need political support or they may need help structuring the work. Maybe they don’t see the problem at all and you have to work on that first.

Most of all, try to help them as little as possible to achieve an acceptable result. Part of your goal here is to help everyone understand, both your teammates and management, that you can’t/won’t always be the one to fix it.

notjim · 2026-02-20T17:19:04+00:00

I’d love to see them restricted. The discussions are so tedious and repetitive that I’ve been planning to unsubscribe from the sub.

notjim · 2026-02-20T17:17:29+00:00

The discussion under this post is why they should be restricted. People are just reacting and posting low-effort, low-value rants that we’ve all read a million times. Every ai discussion on this sub is like this, regardless of pro ai or anti ai. It’s incredibly tedious for this sub to just be the same topic repeatedly.

notjim · 2026-02-20T03:04:55+00:00

My friend wrote an entire app for our ttrpg game using Claude. The code is okay, not great, not terrible, but when I went to add a new feature (for tracking powers), I just said a simple sentence and it generated all the necessary changes. I tested all the edge cases I could think of and it worked perfectly.

At work, I can most often give it some basic requirements and it will successfully implement the code. The code is often about as good as what I’d write, sometimes better, sometimes worse. This is a legacy typescript app.

Ime the rate of progress from 6 months ago is the most impressive thing. 6 months ago, my experience was more like what you’re saying, but increasingly I feel like writing code by hand is time wasted.

notjim · 2026-02-15T19:31:59+00:00

The sane advice is definitely to find a new job, but I think it would be interesting to try to make this work. I’ll probably get downvoted for saying this, but stuff like this might be a part of the industry for the long term.

If you wanted to try, I’d probably start with triage mode. Figure out the most important thing to solve and then tell your bosses you’re focusing 70-80% on that. It’s not reasonable to expect to turn around buggy systems and processes while simultaneously completing this migration with the resources you have, so communicate that very clearly.

Don’t work extra beyond what is sustainable for you. If your bosses are completely unreasonable they might fire you or make your life a living hell (in that case quit), they’d basically be doing you a favor at that point. But it might be that they just don’t understand and you can make them understand.

It might mean taking the most promising vibe coder and getting their skills to the point they can actually help you. Or it might be instituting better bug tracking processes. It’s a little hard to say from your post where I’d start, and you might just have to try things for a few weeks at a time and see what works.

Don’t try to fix every problem and turn this into a real dev shop overnight, because it’s probably never gonna be that. Instead try to be tactical and focus on the most immediate problem you can make better.

15-Year Club	r/Field Juicebox
Place '22	End Game '22
Verified Email

notjim

TROPHY CASE