Of course this is just my opinion but the job market seems to be quite dire right now. Yes I had two FTE jobs and yes I quit one on purpose. But I casually apply to jobs and respond to recruiters if something sounds interesting. In the past 7 months of this I've gotten to final round and rejected twice. Every other time I was rejected at 2nd round. Now I can be bad at interviews or whatever but its never been a problem before.
the stories are endless. Suffice to say here is a retarded pattern out of a million. can we connect to a mailbox with this shit ass app to scan for attachments to download them then pass to our file management system then upload to a servicing platform. why are we not automating this to send directly to the destination system? also all files are sent via email. ask them to stop handling shit manually and i get blue screen stares. and yes all the dev teams are indians. fucking morons everyone of them.In things that are in source control yes. The problem is that ancient Oracle DBs, MSSQL, and so on don't really have it. There isn't a legacy system really where you build out shit in SQL, store it in git and push to production and it then builds all of those things for you. If you did have that it was the result of forward thinking leadership and it was an in house solution. This is the problem my bae DBT exists to solve.
All of his jank is due to stuff that occurs around the edges in system architecture. Where access and controls are historically very limited. As in anyone can and does do whatever and has for a very very long time. When it comes to system architecture less than half of it really exists in source control or review as you would think of it. This is why network and platform people are big on stuff like Terraform, for example, where your config is all stored as code in git like any other thing. Dealing with all of that bullshit and trying to limit rampant retardation is pretty muchTomServo 's job.
Having the personal phone number of the #2 in the company.How did he have such luck getting another job?


Insane. People think code is bloated now?Adding to that my team is building out a metrics suite on AI usage. It was primitive for 2025 in my opinion but 50% of your performance and thus raises, bonuses, or promotions was solely rated based on your AI use. The initial solution only scored you based on the chatgpt webapp. If you created a custom gpt alone you were a power user which was the highest. It was easily gamed but not many figured that out.
This quarter we are developing a high octane one that measures copilot and cursor use. Lines of code generated, most used models, lines rejected, in line code suggestions accepted, and how much makes it into your git branches and thus into production code. Probably more than 50% performance based on this for 2026.
As in you could have been a rock star at your job but if you didnt use AI to do it you were rated as an under performer. Its that serious.
Bet your asses all of your companies are doing this or worse.
Pretty ironic watching all the "learn to code.." guys staring down karma now.
I still code, not as much as I'd like, too much managerial shit. But just this week I refactored a python function that was throwing multiple linter errors for complexity. You know, too many lines of code, too many branches, too many parameters, etc. Usually I ignore those but in this case I think they're right, it's shit code.
This is the bulk of my work, refactoring existing code. How do you guys use AI and then trust the output enough that it ends up saving you time? In this example, I can't imagine an output where I'm not going through it with a fine tooth comb and testing each function it touched.
What do you in the case of external dependencies that are resolved at runtime? I can't get my IDE to resolve those, so forever they remain red squiggles. In my original example, many of the code paths that I ended up touching were referencing external dependencies.I don't trust anything, I look at the output and then tell it to refactor its own output until it spits out something that actually works.
Yes, this is faster than doing it myself. A lot faster.
But you also don't use AI (or at least shouldn't) to crawl an entire repo or branch and try to refactor the whole thing. I don't use AI that way at all. I use it like I code, modular, one piece at a time.
What do you in the case of external dependencies that are resolved at runtime? I can't get my IDE to resolve those, so forever they remain red squiggles. In my original example, many of the code paths that I ended up touching were referencing external dependencies.
How do you identify the boundaries of "ok, it should be able handle this much"?
Considering the corruption and incestuousness of the AI industry, a pessimistic take might be that your employer is being financially incentivized to do this in order to artificially inflate AI demand and usage.Adding to that my team is building out a metrics suite on AI usage. It was primitive for 2025 in my opinion but 50% of your performance and thus raises, bonuses, or promotions was solely rated based on your AI use. The initial solution only scored you based on the chatgpt webapp. If you created a custom gpt alone you were a power user which was the highest. It was easily gamed but not many figured that out.
This quarter we are developing a high octane one that measures copilot and cursor use. Lines of code generated, most used models, lines rejected, in line code suggestions accepted, and how much makes it into your git branches and thus into production code. Probably more than 50% performance based on this for 2026.
As in you could have been a rock star at your job but if you didnt use AI to do it you were rated as an under performer. Its that serious.
Bet your asses all of your companies are doing this or worse.
I just resort grepping the entire sandbox. Good ol grep and find.How did you resolve it without AI? Do that exact same thing, but prompt AI to do it (or at least attempt to do it) for you. One problem at a time.
AI that exists today is not intelligent at all, but its got a lot of stored data and can access it (like memories) way faster than we can. It doesn't know everything, and its often not quite right, but if you understand the problem you are trying to solve, and can actually solve it yourself, you can use AI to solve it the exact same way you would, just faster.
I think a hurdle lots of folks might have with utilizing AI is thinking there are special commands or secret features or a certain way to use it. Its conversational, have a conversation with it like you would a co-worker. Ask it if it knows how to address a problem you're having. Just don't try to send all your action items to it all at once.
So here's how it works right now. Its a scoring algo. Based on AI usage related inputs. You can imagine it like this:Considering the corruption and incestuousness of the AI industry, a pessimistic take might be that your employer is being financially incentivized to do this in order to artificially inflate AI demand and usage.
You are resolved to a code proofreader and tweaking minor things or examining complex logic where it has the most problems. Then changing that.I don't trust anything, I look at the output and then tell it to refactor its own output until it spits out something that actually works.
Yes, this is faster than doing it myself. A lot faster.