Got a legit question/semi rant for anyone who may know. I want to start by saying that I'm not really a "network" person, at least on MS systems. I can physically plug cables in and shit like that, but the software side of networking is not a thing with which I can claim familiarity. Anyone who's read my recent rants will know that I am forced to deal with IIS, because my boss is an insufferable microshit fanboy of the highest level, and is easily frightened and threatened by the use of a keyboard for anything other than using facebook.

I've got a couple of microservices running under IIS, and our customers thankfully are able to access them with no issues. Those of us in the "IT department" are also able to access it. No one else in the building, on our network can, and despite me not having set up this network, or really having anything to do with it, the rest of my "team" (LOL) refuses to help me solve the problem, because developer = networking specialist and printer fixer. Does anyone here have an idea? I found a think on Stack Overflow about firewall rules, but those are already set appropriately.

not anymore

Last Saturday, I came across a fellow techie at a house party. As soon as he found out I am a developer, the question
"What is your favorite programming language?"
came bursting not even a nano-second after I told him.

Anyone else finds this super cringe?

I believe that people who dig deep trenches in such a topic will be the root cause for the next software crisis. I mean, look at Javascript. In one of my later posts, literally noone could give me a reason to not think Javascript is a dumpster fire. And yet it spread out like a malignant tumor.

To verify not all is lost, I quickly googled any databases written in JS, and luckily just found one archived repo and nothing else. Because Im calling it, once Javascript reaches the database layer, it's terminal.

HKTOTO88 🧲 Link Resmi Situs Slot Gacor No#1 Indonesia Terpercaya Hari Ini

Hehehehe, you would entertain yourself to some Debian downstream packager drama, wouldn't you? 🕺💃🔥🔥🔥

https://fosstodon.org/@keepassxc/...

guys, i really dont know why i havent been losing weight!!!!

🤡

If you just git add . by instinct, you're already dead inside

Instead, consider checking out the diffs of your changes before staging them, and then stage the files or directories individually

Of course I'm saying this to complain about my colleagues who stage and commit things they shouldn't, it probably doesn't apply to small side projects, but staging individually is probably a good habit to have

I got a crap raise — lowest I’ve ever gotten anywhere, and well below inflation — despite busting my butt, having somewhat better health and therefore productivity, etc.

I complained to my boss about it, and said it was insulting. He said that direct managers have zero say in raises, and instead it’s entirely up to execs and HR. Makes sense, since nothing makes sense at this company.

Anyway, he apparently talked to his boss, who talked with his boss, who talked with the execs and HR, and they decided to give me a raise on my raise, a whole $1k/year more, all the way back up to the usual insultingly-low 3%. Yay.

Their reasoning?
“Money is tight.”

The last all-hands?
“Record profits! Record sales! Record numbers across the board! And most of all: record profits! Give yourselves a round of applause for making this all possible!”

Money is tight, eh?
I hope they get smushed by a meteor, given a snuggle-struggle by a roving Somali gang, or kept warm for the rest of their lives by another Hawaiian/Californian wildfire.

Just deploy your crappy code and enjoy your weekend

The most normal C++ program be like:

// prints "Hello, World!"
namespace{decltype(+*"")(*main)()=[]()->decltype(main()){return{};};}
decltype(main())(main(decltype(main())={},decltype(&*"")_[]={})){
extern decltype(&"") puts;
reinterpret_cast<decltype(::main())(*)(decltype(&*""))>(&puts)("Hello, World!");
return(decltype(::main()){});
}

Average social media experience

Post: Guys, I have such a headache right now ughh.

Comments:

#1. Omg, so relatable haha.
#2. Yeah I literally have a migraine rn. LITERALLY.
#3. I am in the MRI room while I read this thread. You have no idea how easy you've got.
#4. Backenders are only about being an asshole. Also, JS rules and you know it.
#5. I like trains.

why has express always felt like such dogshit always

res.send(...)

ugh, just gives me shivers

I decided to do a daily Blender render just as a creative challenge for myself. I was so excited because I built an awesome computer this year and was eager to put it to use, only to be hit with seemingly random BSODs and crashes a couple seconds into the render.

As it turns out, my CPU cooler is woefully inadequate to handle 32 threads running at once, which was the cause of my crashes. Turning the render threads down to 8 keeps the temps low enough to finish the render.

In a way, it's a relief because the alternative was a problem with my $900 GPU. I've ordered a bigger CPU cooler and well reviewed heatsink paste which will hopefully fix it. If not, I'm going to have to go water-cooled, which I really don't want to do.

The Odyssey of the Tenacious Tester:

Once upon a time in the digital kingdom of Binaryburg, there lived a diligent software tester named Alice. Alice was on a mission to ensure the flawless functionality of the kingdom's latest creation – the Grand Software Citadel.

The Grand Software Citadel was a marvel, built by the brilliant developers of Binaryburg to serve as the backbone of all digital endeavors. However, with great complexity came an even greater need for meticulous testing.

Alice, armed with her trusty testing toolkit, embarked on a journey through the intricate corridors of the Citadel. Her first challenge was the Maze of Edge Cases, where unexpected scenarios lurked at every turn. With a keen eye and a knack for uncovering hidden bugs, Alice navigated the maze, leaving no corner untested.

As she progressed, Alice encountered the Chamber of Compatibility, a place where the Citadel's code had to dance harmoniously with various browsers and devices. With each compatibility test, she waltzed through the intricacies of cross-browser compatibility, ensuring that the Citadel would shine on every screen.

But the true test awaited Alice in the Abyss of Load and Performance. Here, the Citadel's resilience was put to the test under the weight of simulated user hordes. Alice, undeterred by the mounting pressure, unleashed her army of virtual users upon the software, monitoring performance metrics like a hawk.

In the end, after days and nights of relentless testing, Alice emerged victorious. The Grand Software Citadel stood strong, its code fortified against the perils of bugs and glitches.

To honor her dedication, the software gods bestowed upon Alice the coveted title of Bug Slayer and a badge of distinction for her testing prowess. The testing community of Binaryburg celebrated her success, and her story became a legend shared around digital campfires.

And so, dear software testers, let the tale of Alice inspire you in your testing quests. May your test cases be thorough, your bug reports clear, and your software resilient against the challenges of the digital realm.

In the world of software testing, every diligent tester is a hero in their own right, ensuring that the digital kingdoms stand tall and bug-free.

Someone not knowing the docker ps command teaching about docker :S

You ever just get constantly shit on by life, work, and everything for weeks and then, one day, it finally just turns around for the better. After that, you finally feel normal again. Probably all the Christmas cookies I’ve been eating… In the words of forest gump, “I’m so happy I could bust!”

I just scroll past this question asking how to get good at Git commands (https://devrant.com/rants/9997784/...). Figured I'd share my thoughts as a separate rant cause it's a topic I've tinkered with a bit.

So, My initial engagement with git-related queries on StackOverflow dates back to around 2021.. Surprisingly, one of my short and straight-to-the-point replies got a hand full of attention. You can check it here: https://stackoverflow.com/a/...

Now, about mastering Git commands – from my own trial and error:

1). Instead of trying to cram everything into your big brain, scribble down notes. Trust me, it’s more practical. I kept a cheat sheet of sorts as notes on my PC, noting down the commands I used day in, day out. Super handy beyond just work stuff.

2). You gotta get what each command does, but you don't need to nail it all at once. Spend a day diving into the basic commands. Leave the trickier ones for later; they start making sense as you get more into it.

3). I had this aha moment when dealing with a merge mess using a GUI tool. Switched to the command line, and bam! It made way more sense. The command line's like a secret passage to really understanding Git.

So, if you're wondering how to tackle Git commands, my take is: *notes, *baby steps, and *lean into that command line magic. Mix them up your way and see what sticks for you!

so now they even have a name for not being an idiot...

its called a "composible" architecture as apposed to a "monolith"

what if i told you it's all the same?

(i'll even throw in a bonus and say that a "microservice" architecture is still a monolith - because you need all your damn microservices working together for the full product or service anyway!!! and thats a monolith!!!!)

wow, you've "decoupled" your frontend from your backend? with this fancy thing called an "API"? well, what the hell else was anyone doing in the past decade? ITS THE SAME THING YOU DUMBASS

god i swear its 🤡 all the way down, just inventing new words for the same thing over and over again. idiots. idiots everywhere

i'm just so happy we have "composible" architectures now ❤️ thank god for that

I am in jvm hell. I have been given a task to add mockito tests. All the existing documentation concerning junit 4 is out of date. Need to use junit 5. All mockito tutorials are out of date. I thought mockito was stupid before junit 5. Now it is “really” stupid. The tutorials I am reading are shit. We have wandered into bleeding edge fucktardness. Kill me now.

Mam you're not listening to me !!!!

I said DO NOT REDEEEEEEM !!!!

My lovely team and I inherited a legacy app written in Angular 14.
We love it when we get fucked by Pajeets like this.

We love tons of `any`-s in the codebase.
We love unreadable code with 5 levels of nested ternary operators.
We love the lack of a README on how to actually build/start the app.
We love the outdated dependencies.
And we absolutely love it when you use a paid package that costs $1755.

when you run lighthouse on some tech "guru" with 50K subscriber's website and can laugh when they don't even have alts on images

hahahahahahahaha clowns

to be brutally honest, you need to know the basics before attempting to teach anyone anything, i don't care how boring it is

🤡🤡🤡🤡🤡🤡🤡🤡🤡

Mushrooms are dope

Do you guys still see the relevance of using code freezing instead of just properly managing versions, repositories and branches in a cyclical manner, given how advanced software practices and tools are supposed to be?

To give some context, the company I work for uses the complete trash project management practice of asking teams to work on a sprint basis, but there is still a quarterly milestone and code freeze to commit to and it's where shit hits the fan.

Development teams rush features at the end of the quarter because they had to commit at the very least to a 6 months in advance planning (lol?) and turns out, not being able to design and investigate properly a feature combined with inflexible timelines has high chances to fail. So in the end, features are half-assed and QA has barely any time to test it out thoroughly. Anyways, by the time QA raises some concerns about a few major bugs, it's already code freeze time. But it's cool, we will just include these bug fixes and some new features in the following patches. Some real good symver, mate!

Of course, it sure does not help that teams stopped using submodules because git is too hard apparently, so we are stuck with +10Gb piece of trash monolithic repository and it's hell to manage, especially when fuckfaces merges untested code on the main branches. I can't blame Devops for ragequitting if they do.

To me, it's just some management bullshit and the whole process, IMO, belongs to fucking trash along with a few project managers... but I could always be wrong given my limited insight.

Anyways, I just wanted to discuss this subject because so far I cannot see code freezing being anything else than an outdated waterfall practice to appease investors and high management on timelines.

Please stop using cache as an integral part of the system.

Just... don't...

The horrors persist, but so do I.

Dear laptop vendors, stop wasting so much precious device estate on nothing!

This wasted physical space could easily fit in six USB ports, or four USB ports and two HDMI ports, or four USB ports and one HDMI and one LAN. Or four USB ports and two SD card slots.

> "Who the heck needs 6 USB ports?"

You don't need more USB ports… until the day you do need them comes.

> "HDMI and LAN are feature creep!"

It's "feature creep", until you need it.

> "Ever heard of USB hubs?"

While better than nothing, they are tedious to carry around and can hardly support more than one external high-power device such as an external hard drive or blu-ray drive, except if you have an external power adapter, which is even more tedious to carry.

Also, have fun closing programs until the operating system stops whining "volume is busy" just so you can unmount your external SSD and then reconnect it through a USB hub. Sounds like fun, huh?

You were playing audio from your external SSD? Too bad. Now you need to close the media player to be able to unmount the SSD, then later restart it and seek the last position. And all of that could be avoided if your laptop happened to have one more USB port.

me irl

Please don't mutter your ideas on calls or trail it off mid sentence to mouse level's of sound 🐁.
It's so awkward having to ask what you've said every few moments.
*Especially* if we work together all day all week

N.B. speakers on max volume + auto-captions are already on so I can piece together what you said.

Conversations are so difficult otherwise

That is all

ticket so large it can be divided into multiple subtasks with their own sizes

also divided into MRs big/substantial enough to be annoying to review

can't finish it all in time for vacation, rip