I'm delightful

My teams current process is:

1) Asked by product to create “T-Shirt size” estimates, also known as a WAG (wild ass guess). The process is the mental equivalent of throwing darts while blindfolded, after being spun around in a circle and pointed in the wrong direction.

2) Product make firm commitments to upper management based off these. Ensuring them that all these features will make it out in Q2.

3) 4 days before Q2 starts, product ask engineering to figure out the real estimates based off no concrete information what so ever.

4) 4 Weeks into Q2, product provide the missing information.

5) Engineering inform product that the estimates are out by a factor of 1.5 - 3 times the original estimates.

6) Product sends angry email to upper management that through not fault of product, engineering are unable to meet the deadlines.

7) Everyone shout and complain until 1 week before Q3, then see point 1.

Following this process, you and your team can be just as delightful as me.

That’s the practiseSafeHex guarantee!

Had the Windows Insider Preview for a month or so to get Ubuntu Subsystem early back when it was Insider-only.

Turns out that your license policy changes when you use Preview builds: if your PC isn't updated to a certain build by checkpoints set throughout the year, your license expires and you have to reinstall Windows. No way to recover anything already on the device. So if you get Insider Preview and shut your laptop off for too long...

Thus began a killer combo attack on my Surface Pro 3.

While trying to figure out what was going on and loading up a recovery on a flash drive, the Surface Pro 3 BIOS was sitting idle behind me. On 100% CPU. The only reason I think this is that by the time I noticed the insane fan noise, the screen was hot enough to burn my finger as I tried to turn it off. The heat sensor triggered it to shut off before I could, though.

That heat sensor, however, won't turn it off if it's busy installing Windows, supposedly to keep anything from getting hopelessly corrupted. What followed we're 3 hours of fan whirring from a slab of metal hot enough to cook an egg with.

Windows is back and working. The battery indicator, however, melted during reinstallation. And the battery lasts an hour, max. Thankfully I'm not out of a tablet, but it seems to me that W10 is becoming more and more like malware, just waiting for you to activate one of it's delightful payloads.

Achievement unlocked: malloc failed
😨

(The system wasn't out of memory, I was just an idiot and allocated size*sizeof(int) to an int**)

I'd like to thank myself for this delightful exercise in debugging, the GNU debugger, Julian Seward and the rest of the valgrind team for providing the necessary tools.

But most of all, I'd like that three hours of my life back 😩

Init and Hello. My name is git and this is my story.

I just arrived in this system recently by the apt highway. It's not the only way though. Some for example used the npm hype-train, others arrived from the ssh shore. No matter where we came from the next step on our agenda was time to introduce our self at the event destined for all new-comers to the system.
"As many of you I reside in the usr-bin district. I'm really into history and commitment! I like it when people work together, so I'm always eager to bring all branches together."
"But what is it actually good for?", asked Curl, which I already met at the bus station. Many nodded in agreement. It was odd. Somehow I felt not quite at home. All the others seemed so different based on their field of work.
"We have worked here in a really agile environment for ages. There is no need for any kind of strange bureaucracy.", said another voice.
All attempts to convince them from the beauty of history or a little bit of management were unsuccessful. It was just the beginning of a not so interesting stage in my life - to say the least.

Today was another of 'those' days. I live in this community for quiet a while now and unfortunately nothing really changed - at least for the good. I sat on my branch of the tree with all the others around and there was nothing really to do for me. Again. I mean, actually it's true. I have to admit it. There is just no work on this world for someone like me. All the others seem to be so busy, while I just have to sit around and question my own existence. Since I grew tired asking these questions to myself, I stopped it. I can't do a thing actually. That's not how this world works.
"Hey fagit, anything meaningful to add to our delightful conversation?", nginx shouted over to me from another branch of the tree. Before I was able to give an indifferent answer the voice just continued.
"Oh, sorry. I forgot that you have no purpose after all. Well, never mind!"
Everyone started laughing at me. It was not too bad by the way. Actually, this was quite ordinary. These fucktards completely ran out of creativity. If it wasn't for that mere emptiness gaping right above my guts, I'd actually be disappointed. I even got accustomed to the alias 'fagit'. Quiet sad given the fact that i really like my real name. If only someone would mind using it... First too quiet to notice but growing in intensity a rumbling emerged from somewhere deep within the tree. Out of a sudden everyone stopped laughing. The voices slowly faded while the growling from afar grew louder. It had come. Not more than a shadow reached out from the tree and faster than anyone could comprehend nginx was simply gone. Killed in an instance.

Disclaimer: This story is fictional. No systems were harmed in its creation.

Trying out devRantron for the first time...damn this feels good. Thanks @Tahnik @Dacexi @SirWinfield @PhantomBKB and any other contributors of this delightful application!

Today in development: discovered that it's possible via combination of keys to rename a database in SQL Server Management Studio without as much as a dialog box to confirm.

Shout out to the 2000ish users in production that discovered this delightful nugget of info with me.

Lessons learned:

A) Don't trust Microsoft to create software that makes you confirm potentially catastrophic actions

B) Make sure your user hasn't been granted ALTER DATABASE permissions without your knowledge before you start using it.

Most of the times I really hate typos, coz they seem like carelessness, lack of preciseness. But this delightful method name just made my day:
ReceiveBackendMassage

Was working on a client's project. He had given clear specs. Work went delightful with less or no hacks. Then I get asked to add a extra feature which I had little thought about. Now I think it's a small hack and can be done. But here I am. One hack leading to another. I am too deep into ugly hacks. Maybe I should stop software development and join postal service to sort letters. I feel so incompetent.

I have now turned the name board in my cubicle to hide my name.

Why you ask? Not because I don't like my name, or dislike my name board (there's this little design on it which is just delightful).

It is to make it a bit more difficult for new morons who don't know who I am or where I sit. Can't do much more than that because I have a desktop.

"In a sentence: Technically brilliant, delightful to work with, combined with a self-awareness and strong desire to improve. We also want to make sure everyone is highly supportive of each other; we win as a team."

In short: you're looking for a unicorn, which your company won't be.

Guy really said he wants the charisma of Steve Jobs and the technical genius of Wozniak...

are people really this stupid?

I know this sounds odd, but I really find algorithms things of delightful beauty.

A creative solution to some very deceptively complex problems.

Sure, some implementations aren't the best, but seeing them after just makes me appreciate the time and effort that must have gone into designing things like Merge Sort, Binary Search, Greedy Algorithms, BST, and Dijkstra's Algorithm.

So! If your code is unoptimal, looks terrible, or is a sheer abomination, take a moment to appreciate the little piece of art you've made before you go and make it better.

Me: //trying to fix bugs
IntelliJ: hey you have 2 typos
Me: Where? I can't see typos anywhere what the Hell
Me: //looks up and down my classes/interfaces. It's my name
Me:
Me: Well isn't that delightful

Conference calls are all about playing the thrilling game of "Guess who's speaking?" 🤔🎭
The symphony of awkward pauses, microphone feedback, jitters, and the delightful sound of someone else's breathing into their mic. 📞🎶

"hey, can you please help me out with this, it isn't working"

"What's it say?"

"I dunno, It's giving (not throwing) some exception/error" (no clear distinction between them)

Well, shit. Did NOT expect Java to do that in case of some undesirable flow in code! Stack trace, error message, what was happening when the exception (or actual error) occurred as inferred from logs... Nope.

Great!

"Cutesy tool" is a delightful and beautiful handcrafted tool for doing shit in a slightly different but arguably slightly more elegant way. Our home-grown, pure vegan, batteries-included, framework has taken all the right vitamins to save you time developing so you can spend all that time you saved flossing more. 😬

- Inspired by PWAs, Ohmyzsh, and countless other bullshit cutesy descriptions.

First experience with dotfiles today, absolutely loved working configuring it a bit, also first experience with shell. But honestly also felt very dumb and perhaps incompetent compared to other such repos. Anyhow my terminal is delightful to use now, that's probably somewhat good.

Two fixes in CSS that can either be delightful or dreadful:
- overflow: hidden;
- !important

Isn’t it delightful when you come in to a large project to discover that they have a large underlying core that no one wants to touch but everyone relies on.

Quickly perusing the code you realize that the base was clearly created by someone who found their first tutorials for Java, but were previously a c developer.

It’s funny cause this code is of course from ~20 years ago and in different sections you can tell they were a C developer, a business admin, a Db admin, a junior conforming to pressures from others.

I recently looked at the deep rooted abuses of Java beans, and this entire internally created state management engine that serves no purpose but to create contrived complexity.

The use of propriety tools, that they paid lots for that perform incredibly simple tasks that have long since been solved by the open source community. Many of which are long defunct.

And the constant focus is on monkey patching the engine to solve small issues, which bloat the time to deal with issues. Since everything needs to be tested by their methodologies.

The inability to understand that the underlying structure is the issue and that tackling that, rather than just shifting the entire solution to new languages will suddenly solve the problems(or other underlying systems).

It’s just sad.

Ah, Visual Studio Code—our trusty sidekick in the coding trenches. But wait, what's this? A delightful new feature designed to keep us on our toes: the 'Disable All Extensions for This Workspace' command. Because who doesn't love a good surprise, especially when it involves disabling all the tools we painstakingly set up?

Picture this: you're in the zone, about to format your document as usual. You hit Ctrl + Shift + P, type 'for', and expect the familiar 'Format Document' to greet you. But no! Instead, 'Disable All Extensions for This Workspace' has decided to make a guest appearance at the top of the list. How thoughtful! It's as if VS Code is saying, "Hey, let's make things interesting by turning off all your extensions without warning."

And the fun doesn't stop there. Once you've accidentally disabled all your extensions, there's no magical 'undo' button to save the day. Nope, you get the joy of manually sifting through your extensions list, re-enabling each one like it's 1999. And let's not forget the mandatory restarts—one to unload the extensions and another to load them back up. Because who doesn't love losing their undo history and breaking their workflow?

So, dear VS Code developers, thank you for adding a dash of unpredictability to our coding sessions. After all, who needs stability and consistency when we can have random command roulette?

I swear I touched some weird and complex programming shit in over a decade of programming.
I interfaced myself through C# to C++ Firmware, I wrote Rfid antennas calibration and reading software with a crappy framework called OctaneSDK (seems easy until you have to know how radio signal math and ins and outs work to configure antennas for good performance), I wrote full blown, full stack enterprise web portals and applications.with most weird ass dbs since the era of JDBC, ODBC up to managed data access and entity framework, cloud documental databases and everything.

Please, please, please, PLEASE I BEG YOU, anyone, I don't even have the enough life force to pour into this, explain me why the hell Jest is still a thing in javascript testing.

I read on the site:
"Jest is a delightful JavaScript Testing Framework with a focus on simplicity."

Using jest doesn't feel any delightful and I can't see any spark of focus and simplicity in it.

I tried to configure it in an angular project and it's a clustefuck of your worst nightmares put togheter.

The amount of errors and problems and configurations I had to put up felt like setting up a clunky version of a rube goldberg's machine.

I had to uninstall karma/jasmine, creating config files floating around, configure project files and tell trough them to jest that he has to do path transformations because he can't read his own test files by itself and can't even read file dependencies and now it has a ton of errors importing dependencies.

Sure, it's focused on simplicity.

Moreover, the test are utter trash.

Hey launch this method and verify it's been launched 1 time.
Hey check if the page title is "x"

God, I hate js with passion since years, but every shit for js I put my hands on I always hope it will rehab its reputation to me, instead every fucking time it's worse than before.

used fakeupdate.net for a delightful prank on my irritating PM.

There is little as delightful as opening an old VB.net application to find that there's fifty obscurely named event handlers - each with their own block of largely duplicated (but subtly and crucially different) code

Whether baked or no-bake, a strawberry cheesecake is a showstopper that combines the creamy richness of the cheesecake with the sweet and slightly tangy essence of strawberries. It’s a classic dessert choice for celebrations, springtime gatherings, or any occasion where the irresistible combination of cream cheese and fresh strawberries is sure to be a crowd-pleaser.
No-Bake Strawberry Cheesecake Recipe:
Here’s a simple recipe for a no-bake strawberry cheesecake:
Ingredients For Strawberry Cheesecake:
For the Crust:
1 1/2 cups graham cracker crumbs
1/3 cup melted butter
2 tablespoons granulated sugar
Cheesecake Filling:
16 oz (450g) cream cheese, softened
1 cup powdered sugar
1 teaspoon vanilla extract
1 1/2 cups fresh strawberries, hulled and diced
2 tablespoons lemon juice
Strawberry Topping:
1 cup fresh strawberries, hulled and sliced
1/4 cup strawberry jam or preserves

Instructions For Strawberry Cheesecake:
Prepare the Crust:
In a bowl, combine graham cracker crumbs, melted butter, and granulated sugar. Mix until the crumbs are evenly coated.
Press the mixture into the bottom of a 9-inch springform pan to form an even crust. Place it in the refrigerator while you prepare the filling.
Make the Cheesecake Filling:
In a large bowl, beat the softened cream cheese until smooth.
Add powdered sugar and vanilla extract, and continue to beat until well combined.
In a blender or food processor, puree the diced strawberries with lemon juice until smooth.
Fold the strawberry puree into the cream cheese mixture until evenly incorporated.
Assemble the Cheesecake:
Pour the strawberry cream cheese filling over the chilled crust in the springform pan.
Smooth the top with a spatula and refrigerate for at least 4-6 hours, or preferably overnight, to allow the cheesecake to set.
Prepare the Strawberry Topping:
In a small saucepan, heat strawberry jam or preserves over low heat until it becomes smooth and liquid.
Allow the jam to cool slightly before spreading it over the top of the chilled cheesecake.
Arrange sliced strawberries on top for decoration.

Serve:
Carefully remove the cheesecake from the springform pan before serving. Slice and enjoy! This no-bake strawberry cheesecake is a refreshing and delightful dessert that’s perfect for warm days or when you want a fuss-free, delicious treat.