[-] PoisonedPrisonPanda@discuss.tchncs.de 3 points 5 months ago* (last edited 5 months ago)

for such things like shared documents/database entities also a shared test dataset should be available.

Then they cannot play around and modify those outputs anymore without noticing of others. (because their unittests would fail)

my assumption here is only an example. I dont know what youre dealing with.

While I understand the rant. And am on your side regarding those jerk moves. its a management issue. even when they do not act, its up to you to bring this to attention if this seriously conflicts with your work.

And in the long run its a win win for everyone.

edit: I am working myself in early development and despite being an engineer by background Im coding. So I know quite well how difficult it is to make it properly instead of quick and dirty.

this readme is very nice.

company wide policies.

building a proper ci/cd goes with that.

rules and delegations for each teammember.

some has to be the head and reviews.

time consuming probably. but professional in the long run.

we built this shit. thus we are always to blame.

appearently when people call they do no like to text. because they have no hands free or whatever

so voicemail is the better option than simply be pissed because i never called back.

Lets stay at LLM and not AI.

Cheesus.

Fuck me. Why I didnt thought of that before?

Its always something isnt it?

I too had issues with some stuff at first. But until I dive into org mode its the best i was getting.

(Im telling this from stumbling through many apps like tiddlywiki, obsidian, joplin, qownnotes, trilliumnotes, standardnotes, and probably more)

I'm not a bot.

Thats exactly what bots would say, right.

Jokes aside.

i think deletions are not immediately due to the federated nature of lemmy.

I will never understand the hype about nft pixelart....

well summarized write up.

I am working on a 50 year old codebase which little documentation since "tHe COdE iS tHe ManUaL"...

its in the academic field although this does not mean that people took care about it.

and due to porting to newer language styles this thing is near impossible to get into.

I understand that times have changed much.

however to maintain this stuff progress has to be put on halt until a system is established to clean up this mess of 30 years of spaghetti code (assuming for 20 years it was alright)

view more: ‹ prev next ›

PoisonedPrisonPanda

joined 2 years ago