I've joined a Java company and I constantly feel not happy. It's not that I'm that picky but I have a constant feeling of *sigh* and I'm unsatisfied.
There are countless bugs and we don't have PRs, the founder committed 2500LOC vibe-code commit which broke some things and then went for vacation. I fixed it but I feel like I'm constantly dragging my feet. It's not good.
Any thoughts about it?
bro don't cover for the AI
Run
If they manage to run a company based on vibe code and even are able to hire employees probably that isn't too bad, idk. If things are going on even with these practices, maybe you just need to relax a bit... and start to look for a Clojure job 😉
Something told me it is not about java :)
well... add some code and tell nobody... and use it's JAVA api in the rest of the app
pom.xml
deps.edn
src/martynas/gonna/show/you/better.clj
you're just using a java library after allI jest, but only because I can empathise... seems like PEBCAK in the managerial layer, honestly.
Depends on how much influence you have, what stage the product / company is in, and how much energy you wish to invest in changing the situation for the better.
Is the company sustainable for the next 3-5 years? If yes, what do the customers buy? maybe those countless bugs never bother the customers. Focus doing things that makes your customer satisfied, like improving a really small set of capabilities. If not sustainable, your frustration is justified.
> Weak developers will move heaven and earth to do the wrong thing. You can’t limit the damage they do by locking up the sharp tools. They’ll just swing the blunt tools harder. https://vanderburg.org/blog/2009/07/13/sharp_and_blunt.html
It sounds more like a 'cultural challenge' than a programming language one. There are plenty of interesting aspect to the Java language and libraries to explore. Do enough work to keep your job whilst you look around for other opportunities.
I once worked at a company for a whopping 2 months and that was enough for me to take a break from any job for half a year. The practices were abysmal, I think I was questioning whether I wanted to keep being a programmer after quitting that job. It would've been much more effective to just immediately quit and seek something else instead of trying to tolerate it all.
Not having PRs is a low-hanging fruit to introduce them. Yes, people will moan, but it's often the case at smaller companies and one can use the opportunity into growing healthy habits and get mid to long term respect for that very naturally. Next up, making PR reviews mandatory, introducing linters, etc. Step by step over the months it's very easy to show progress and impact and measure the decrease in issues. Even easier if you can point at issues and use them as a reason to introduce the processes, to not be blamed when things take more time to production in the short term.
> Not having PRs is a low-hanging fruit to introduce them This doesn't work when I'm not in power. I'm not higher than the CEO's decision.
It would've been much more effective to just immediately quiNo it wouldn't. I already had a break where I was looking for a job and nobody hired me. This was terrible and I used up an incredible amount of money. Last two years were really really bad and the situation is still bad. E.g. look at Germany: https://fred.stlouisfed.org/series/IHLIDXDETPSOFTDEVE And US is even worse: https://fred.stlouisfed.org/series/IHLIDXUSTPSOFTDEVE