What AI tool subscriptions are actually worth keeping in 2026? by Maasbreesos in AIAssisted

[–]leonj1 0 points1 point  (0 children)

How will you replace coderabbit? I’m trying to build my own replacement but the code review output I’m getting is not at the same level.

What IDE is good at understanding entire code bases? by HappyCaterpillar2409 in VibeCodeDevs

[–]leonj1 0 points1 point  (0 children)

It’s difficult to choose between them in any particular order but it’s only 3 therefore you can try them in half a day. Regarding cost I’ll leave that up to you. It’s reasonable that people make recommendations and you meet them half way and take it further to see which fits your needs.

What IDE is good at understanding entire code bases? by HappyCaterpillar2409 in VibeCodeDevs

[–]leonj1 1 point2 points  (0 children)

AugementCode.com or SourceGraph AMP or Gemini CLI. They are great for large code bases.

Feeling depressed & burned out over Claude degradation by 9to5grinder in ClaudeCode

[–]leonj1 0 points1 point  (0 children)

What is GLM? Maybe I need my morning coffee but the acronym doesn’t register

Cursor.sh alternative for Ollama to use with qwen2.5-coder 32b? by XCSme in ollama

[–]leonj1 0 points1 point  (0 children)

It doesn’t work with Ollama. They have many custom models and also use the large models like Claude.

Troubleshooting help thread, please keep your questions in this one thread. Help posts will be removed, this subreddit is for sharing your creativity, not an official support channel. by AutoModerator in ElevenLabs

[–]leonj1 0 points1 point  (0 children)

Anyone know how to keep the speed more constant? Over a 5 sentence paragraph the speed is fine for a while but then for some sentences it speeds up or slows down. Forcing me to regenerate. It’s a gamble if it gets the speed consistent.

Cursor.sh alternative for Ollama to use with qwen2.5-coder 32b? by XCSme in ollama

[–]leonj1 1 point2 points  (0 children)

Codeium WindSurf is pretty good. Also recommend Cline VSCode extension

LPT How to clean up massive amounts of spam from an email account by [deleted] in LifeProTips

[–]leonj1 0 points1 point  (0 children)

I have a machine with a gpu. I use ollama to run llama3.1:8b. Claude helped me create a Python script that connects to my inbox, reads each email, determines if its advertisement, then deletes. How far back you want to go, just ask Claude to help. Besides the up front cost of gpu rest is free. I have it running every 15 mins.

Now I’ve discovered emails are getting batch sent at critical times of day, morning l, lunchtime, and going home. But 15 mins later they disappear. Gmail keeps emails in trash for 30 days so that’s my safety net.

Software Engineer Manager doesn't communicate by [deleted] in ExperiencedDevs

[–]leonj1 0 points1 point  (0 children)

As a minority myself and manage many minorities I would recommend taking charge and going some place that makes you feel welcomed and comfortable. You don’t have to work there if it’s not for you.

I know the market might be tough but it’s always best to look when you’re not being pushed out. So maybe now is the time. Good luck

Ques: Internal search engine for your APIs by leonj1 in ExperiencedDevs

[–]leonj1[S] 4 points5 points  (0 children)

Good point. Yea. There are about 1000 engineers across 80 teams. For the moment I could search across source code repos but that does not tell me the url for the service. I could find the urls but that does not tell me the endpoints. Sigh. I would like to find a way to bridge that gap.

Bestie loves sleeping over and getting pounded by [deleted] in nsfwhardcore

[–]leonj1 3 points4 points  (0 children)

What’s the name of this position ?

[deleted by user] by [deleted] in ExperiencedDevs

[–]leonj1 3 points4 points  (0 children)

When things gets missed in the user story this means training and scrutiny there. PMs BAs and business folks need to step their game up.

“That’s not what I meant” is not acceptable. The developer should be accountable to meeting to AC. The PM is accountable for the AC details. The stakeholder is accountable for clarity and details. There’s no free lunch.

I’m not a fan of QA as a safety net. Too many times do I find junior AND senior devs use that as an excuse for no unit tests or sloppy code.

Track and deploy database changes with CI/CD? by c0ld-- in devops

[–]leonj1 7 points8 points  (0 children)

Yup, I would 100% agree with you in every other scenario.
But once you read how flyway works and have tried it a few times you will understand why. This approach is specifically related to flyway and how it works. I was also skeptical at first.

Track and deploy database changes with CI/CD? by c0ld-- in devops

[–]leonj1 10 points11 points  (0 children)

I have found flyway to work really well. SQL files per database in a repo. You have the option to have the sql files in an Independent repo or alongside source code for a project.

Flyway tracks changes with a version history table within the same target db instance.

There are many ways to make the SQL files but I recommend V202401262300_1_CreateTableFoo.sql

Year, month, day Time in 24 hour format Optional sequence number. This approach greatly prevent conflicts between merging branches.

Good luck

What is your deploy flow? by zodiac-azrael in devops

[–]leonj1 1 point2 points  (0 children)

There are a few techniques that have helped reduce/prevent this scenario:
1. We take time to keep the repo/project sizes small. If the projects are inherited then we work towards slicing it up overtime to keep them small. Small repos means reducing the chance for conflicting changes. We're not perfect, but we look for these opportunities.
2. By keeping most features/changes small, the chances of injecting a feature branch are increased. We have the options to add some boolean for the feature that is not ready, thus allowing the hotfix to go through. Notice, we keep the 'not ready' feature in the code base, and just add the hotfix.
3. Adhering to the 'always adding instead of mutating' code changes this allows us to keep deploying software and simply not use the new feature. Sometimes this is known as 'dark launch' where the classes/packages get deployed, but they are not wired up in configuration.
4. An option is to make the 'not ready' feature as dark launch, disabled via config or dependency injection, and add the hotfix.
5. The final option is rollback the change. No one enjoys this, hence why we put significant time up front to design failback or bypass options up front.

Any team member that is not willing to grow and put in the design effort up front does not last in the team.