working to overcome decades of cultural and educational training (public schools and college lmao) of being an unquestioning slave who does what they're told

to actually think critically with a product mindset and question is missing from a specification

does anybody have tips

Do you prefer to pin dependencies to an exact version or a specified major, latest minor version?

draft a ticket 3-4 months ago, try rereading and don't remember anything

dont recall doing or changing anything to local java 11 install

it's apparently corrupt, i don't see it on my file system either and dont wanna search for it

old existing repositories in intellij don't care and still have syntax highlighting

new repo i downloaded got caught by problem though

the gratitude of not being in your mentor's position of trapped on fixing an unreproducible issue tied to company's KPIs for months

NVD NIST cve CVSS v4 no rating, v3 rating critical vulnerability

description text low severity, no mitigation solution

what the fuck is this , is it critical or not and what the fuck should i do to solve it, what the fuck

failing to get to the pager before the time increment attempts your manager on vacation

Why do I have to work to manually make sure my different repositories, using different versions see the correct java version, JAVA_HOME for their fucking gradle to work

Why do the repositories not have their fucking dependencies under something like asdf set up already, so i never have to think about this shit

i don't even know about the best practices or care about this shit until I run into the brick wall of it

the other joke is i literally did this shit on my local, hardly understood it and barely remembered any of it and have to figure it out again

best practice in java is to mark classes as final (effective java book)

final classes cannot be mocked by Mockito

if only I was good at programming and writing higher level integration or acceptance tests to circumvent this

Acceptance, end to end, integration tests whatever the fuck you call them.

Any tips on learning how to write them and doing it well? Always been tripped up in the past trying to set up databases and other bullshit so it never seemed worth the trouble since I'm so unskilled.

A field stops getting filled after what looks like your unrelated changes get merged in

debugging hell

i deserve euthanasia and merciful freedom from this life

Use identical name for new field based on an existing field , in separate file, in same package, slight difference in new, no required fields

swagger code gen looks to be efficient, overwrites old

fml

default setting isn't to respect the subtle difference of package/object path

idk the setting to tweak this correctly

Use IDE to easily refactor extract methods

Notice it doesn't order input parameters by order it uses them

I don't want to manually update

I hate SVN

When you gotta break the habit of autopilot wageslave zombie, I ask no questions, I will implement the ticket

A Circle?? In the Triangle Factory?? and I Guess We Doin Circles Now

I am very much ok we doin circles now person

AI can do fancy autocomplete and generate code from prompts but the fucking jetbrains IDE needs me to manually set the fucking SDK java version shit in 3 different places? I feel like I don't remember doing this toil in the past.

On the one hand I feel validated to find a slack thread of seniors and up also irritated, remarkign it's not intuitive, and asking about this , and thankful to see the 3 screenshots there.

Yes I'm salty as fuck

Inspired from me getting blown the fuck out earlier, how do you keep up to date about new features and versions of your tech stack with minimum effort?

https://devrant.com/rants/13420296/...

record was introduced in java 14 but this was my first time seeing it

Am I clown who has never encountered it and should be reading about new features in new versions, or am I excused because I don't make version decisions and for being trash at my job.

Thinking about asking a colleague if they remember how they tested some code they wrote over 10 years ago according to source control.

nervously waiting to see if you get the layoff email

unfortunately also need to continue working in the meantime

tax, pension, etc deductions increased so my recent paychecks are less than previous ones, if this stays this way i guess i'll hopefully get a bigger tax refund later

still sadge

the stress of I don't want to lose git history by renaming whitelist allowlist in existing code but i also don't want to get in trouble from people if they catch me using whitelist for new additions to match what's already in the file

i dream of having a working dev and test environment

or being good enough to have my own stuff working

i don't go out of my way to fuck around with any of it, i just want to do my work, clock in, clock out

acquiring ownership of the bitchwork disaster recovery nobody wants to do

There's a petty problem that you're being told to fix, either some other teams to copy sixty something files and update that many filepaths or you can build job to send over sixty million requests.

when the service endpoint only takes in 1 item to update at a time

fml

fix bug

test production

can't reproduce bug

support tickets and people still bitching they have the bug

i think the shit's been merged and deployed long enough it should've rolled over considering the timestamps on follow up cases

needing to fix a bug that may be present in react/typescript when you don't know the tech stack

unsure if update to button broke the form

don't know nuance or difference between FormEvent vs synthetic events

test environments and local development environments broken

let me die peacefully in my sleep

forgetting to undo config changes for your local settings for development on monolith

then months later having to debug and undo them so you can login locally

i fucking hate svn

Being stuck on bitch work like getting infra to decommissioning AWS stuff and figuring out test plans for emergency cutovers