adobe digital editions is dogshit software that works poorly with a kobo reader

github makes it hard to find unresolved conversations in a big PR

javascript is a dogshit language

typescript makes a valiant attempt to make it better but it's contrived on top of a rocky foundation so it can't quite get there unfortunately

yes i am trash at programming and appreciate strongly typed languages for any heavy duty work, in most cases those languages designed for it from the ground up, don't feel as frustrating to deal with

accidentally deleting hours of tedious front end work by accident while trying to get rid of the error generated garbage by the build system when you are trying to commit just the relevant things while iterating

fail to comprehend code

dig through debugger

make change expecting only to fix one of two test cases

it fixes both test cases, not just one,

pain ensues, code makes less sense to me

Opinions or resources on how to do good abstractions, encapsulation and separation of concerns

import legacy project on new laptop

some gradle shit is broken and i dont understand why

i dont remember having to deal with it years ago and and i have no idea how to fix

cant see the settings difference between it working on old laptop

jetbrains there is no situation i want wildcard import (or at the very least the people i work with who know better than i do)

disable that shit by default

intellij why do you no longer have a default sensible junit test runner config out of the box?

fucking project view neeeded to be on

homebrew, asdf, pre-commit, pip, pkg_resources, setuptools

as a group i have no idea what the fuck is broken with you all trying to work together

UX didn't design with localized strings in other locales being up to ~40% longer in their mock ups

trying to make sense of code you wrote more than half a year ago

it's easier to minimize interactions or use of emails to avoid phishing than deal with sorting it out especially since most companies do in house fake phishing for training

I don't understand CSS and am shit at it, moving forward I plan to treat CSS more like old legacy code I don't want to fuck with and preserving any existing working stuff.

Burned once trying to freehand off an example thinking I knew what I was doing versus preserving what was there.

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/...