This is a fun conversation I had:

Test Engineer: 😑 The test bench burst into flames.
Me: 😪😲 Do what now?
TE: 😐 The test bench burst into flames. It made a pretty impressive fire ball.
Me: 😮 . . . How are you so calm about this?
TE: 😐 Well it's not on fire now.
Me: 😶 Good point.
TE:😧 made me mad as hell though.
Me: 😕 why's that?
TE: 😬 Cuz I only had one damn step left in that test procedure and it was to turn the damn test bench off.
Me: 🤔 Correct me if I'm wrong but the test bench is off is it not?
TE: 😐 Well yeah.
Me: 🤔 and you caused it to be turned off by your actions no?
TE: 😕 . . . yeah . . .
Me:🤔 sounds like you turned it off to me.
TE: 😒
Me: 🙂
TE: 😐
Me: ☺
TE: 😑
Me: 😎
TE: 😐 but it won't turn on again.
Me: 🤔 do you have a requirement to be able to turn it on again after you turn it off?
TE: 😑 It's implied.
Me: 😐 not what I asked
TE: 😧 No not explicitly.
Me: 😎 sounds like you completed the test procedure.
TE: 😑
Me: 😎
TE: 😑
Me: 😎
TE: 😧 that's not how it works.
Me: 😎 doesn't it?
TE: 😑 No.
Me:😎
TE: *walks away* 😧😧😧
Me: *turns back to computer* well I was just trying to help YOU out 😒

I am the best at interpersonal communication.

A programmer and a business analyst are sitting in the break room one day eating lunch when suddenly the microwave catches fire. Thinking quickly, the analyst leaps up, unplugs the microwave, grabs the trash can, fills it with water from sink, and dumps the water on the microwave to put out the flames.

A few weeks later the two are again having lunch in the break room when suddenly the coffee maker bursts into flames. The programmer leaps up, grabs the coffee maker, shoves it into the microwave oven, and then hands the trash can to the business analyst, thus re-using the solution developed for the previous project.

I was working in a small startup with very cool people as a GameDev. One day I turned towards my colleague to tell him about a joke I just read and I saw flames coming out of his CPU. He was so focused on his work that he didn't notice.

I yelled "OH, SHIT' and quickly reached to the main switch and turned it off. Everyone turned towards me to yell at me, but then they saw the flames and everyone ran outside.
After few minutes the flames died. My colleague was in shock to lose his work as the HDD was completely burned.

After my previous PC bursting into flames when I changed my input voltage to 120v on the power supply my dad never bought me one again this happened when I was aged 12. I was so much in love with computers that I would visit my friends who had ones at home and not leave till their moms asks me to. I remember collecting my lunch money and buying a Pentium 4 mb for dog cheap at a local store and as soon as I plugged in the mb short-circuited and died (I had the other parts as I was scavenging the junk yard for them). I'll never forget the moment I burst into tears seeing my hopes for a PC dieing. So after all the years passing when I was 16 I spent my whole summer vacation working in a construction site doing so much heavy work. There were days that my body couldn't bear and I just fell but somehow by the end of that summer I managed to collect enough money to assemble this 3rd gen dual-core. This is my baby. I'm using it till this date.
**Sorry about the bad English

Recipe for a Great Programmer:

Ingredients:
-Books for a computer science curriculum from a top university
-Computer
-Headphones
-Internet
-Stress ball
-Pillow
-Lighter fluid
-Food

Directions:

1. Cover computer science books with lighter fluid
2. Light books on fire
3. Use flames to cook an energy-rich meal for the thousands of hours ahead
4. Pick an IDE
5. Choose a project beyond current capabilities. Good ways to push boundaries:
- Unfamiliar domain (e.g. large scale data processing, UI programming, high performance computing, games)
- Exotic programming language
- Larger in scope than any project before
6. Shut up about your IDE
7. Attempt to build
8. Stop procrastinating on Hacker News
9. Re-attempt to build
10. Squeeze stress ball and scream into pillow as necessary to keep sanity
When stuck:
- Paste stack traces into Google
- Find appropriate mailing list to get guidance
- Realize that real learning happens when you are stuck, uncomfortable, and/or frustrated
- Seek out books, classes, or other resources AFTER you have a good understanding of your deficiencies
11. Repeat #4 to #10 for at least 10 years
12. Results guaranteed! (to the same extent static types guarantee bug-free programs)

source: nathanmarz.com

I really hate this company.

The code is a disaster. Every single other employee is a salesperson. Nobody has any bloody clue what I do or how difficult it is. They don't care about stability (unless things are crashing), maintenance (until crashing), code quality (until it delays features), or anything apart from shiny new features they can sell. The boss (the king salesman, if ever there was one) doesn't know how to manage, but tries to by acting like his "nice asshole" self -- he's an asshole that gives you passes, makes sure it's bloody obvious that he's doing it begrudgingly, yet everything is still absolutely your fault. If he arbitrarily decides it's too much your fault, he stops being "nice" and flips out on you in front of everyone. That's a "nice asshole": an asshole who can barely even pretend to be nice.

Fuck him.

And you know what? I really hate having to work next to these fucking birds, too.

Today was our weekly conference call, and I was both late and unprepared. I was too focused on my work, and got a ping 4 minutes into the meeting, so I obv didn't have time to prepare. Boss was also pissy today, and I didn't have much to show for my week, thanks to lots of little "OMG NEED ASAP" shit projects that all took too long, pushing back what I was actually supposed to work on. Which didn't get finished, of course, and today that project was "the most important" -- I suspect simply because it wasn't finished. AGADJFSKL. Cue the birds fucking screaming and never fucking shutting up no matter what I did. Blanket? No effect. Spray bottle? SCREAM MORE! Boss was yelling at me, the birds were screaming, and I couldn't think. Goddamn fucking disaster.

and yes, we have a macaw. A macaw and over 20 cockatiels. Said macaw decided today was a lovely day to just fucking SCREAM non-stop, and the tiels were doing their best to keep up. Thinking clearly during this cacophony? Not gonna happen.

Wait, "go elsewhere," you say? Somewhere quieter? Where is this "elsewhere?" We live in a fucking tiny house, and during the call it was (and still is) filled with sleeping people, and surrounded by a fucking desert. Who the fuck thought living in the desert was a good idea, anyway? Like, seriously. What brainless moron thought "You know what? This is a great place! Let's settle down right here," while trudging through the scorching sand and dust, looking at the basically lifeless horizon filled with large, hot, dry, dusty, barren rocks (aka "mountains"), and fucking dying from thirst? Probably someone so delirious from heatstroke they never actually recovered, and continued raving that it's a goddamn paradise to their heat-addled imbecile followers. I really hope they hallucinated a la-z-boy in place of a hedge of teddybear cholla and died an excruciating and prickly death. Fuck that guy/girl, too.

But I digress.

I seriously need an office that isn't a 30 min drive into gang-central. I'd work outside, but I live in the middle of the bloody fucking desert, and get heat exhaustion within about half an hour. Everywhere else in the house people bother me almost incessantly.

just. FUCKING FJASKLDFJGAG.
I HATE THIS PLACE SO SO SO MUCH.

'I've had such Zen lately,' Alex said. Maybe then, but lately? I've just been too exhausted and burned out from putting up with all this shit to get angry. Days like today? I could pour kerosene over everything and laugh as it all just burned to ash.

So, continuing with the story, I decided to quit today.

I'm not even a month there, and I'm running out of there in flames.

I've got 2 panic attacks in one week, I'm not sacrificing my mental health for some idiot's scam.

Continuing the trend,
The algo strikes again

Fuck you and your bullshit Teams meetings.
I hope you die a painful and slow death while your servers burst in flames and you hang yourselves.
You schedule 4 of them, then bitch about how developers aren’t getting any work done.
Maybe if you didn’t suffocate them with your bullshit meetings they would.
I am looking forward for the contract to expire or in this project so I can finally get some peace.

Fuck your stupid meetings. You deserve to be arrested and shot by the Gestapo (or KGB, whichever you find more evil).

I have rather been enjoying MS Visual Studio Code of late. Ten years ago when I was deep in my Linux phase the thought of anything Microsoft would make me burst into flames.

Question - Am I now evil, having turned my back on sublime text, atom and a plethora of other editors?

Got new stickers today. They say stickers make your computer faster, how'd you explain if you paint a car with flames it runs faster? Check mate, atheists.

So we've been on our Christmas holidays/vacation and decided to spend New year's eve at my place barbecuing.

Yes needless to say that we got somewhat intoxicated, had steak etc and then fucking fell asleep on the floor outside.
In -3 C°.
Woke up like 20 minutes later according to my friends.
Decided to continue barbecuing but since the fire turned into half dead embers I decided to fucking chop up some wooden planks laying around.

Short recap.
New year's Eve.
Barbecuing.
Intoxication.
Fell asleep.
Woke up.
Chopped up planks in the dead of night.

Continued barbecuing afterwards.
Fire ablaze again, roasted the remainder of the meat and since it was too boring for me I decided to pour fucking Korn, (German alcohol) over the flames.
Needless to say my arm hairs burnt off.

Friend comes out, sees me, fucking dies of laughter.

All promised to stfu about it.

Anyway the flamed steak and stuff were still delicious.

There comes that dreaded time in the life of a developer working in a conservative, borderline medieval corporate, where darkness sweeps over the land and the evil lords rummage through every peasant's hovel searching for the forbidden - AKA software audit.
So I made a list of all the unauthorized open source code we desperately rely on, and we decided as a team to go down in flames and gloriously fail the audit, a legend of sacrifice that shall be passed on in hushed voices.

Oh look. The monitoring channel is in flames, smartphone is vibrating so hard it's having a seizure.

Hm. Nah it's fine. Not my...

Damn it. Incoming call. -.-

I'm actually on vacation (more like you need to trim down overtime before management get's angry).

They decided to test the new hardware / os stack I set up in the last weeks. I'd actually be happy about it If I wasn't on vacation and would be part in something that I invested a lot of time...

Well now I am. Guess what. It's running too good.

And that's not a joke. It's partly due to an upgrade in infrastructure (got rid of some last remaining 1 Gbps networks)… but also because I changed quite a lot on the OS / VM side plus we changed from XEN to Proxmox... With major tweaks, too.

The whole stack can now handle peak traffic where it would choke before, and even go beyond the old peak traffic.

Enough of introduction, the simple reason why shit burned down was because they tried out the current development branch and let it ran.

The development branch had an currently unfinished ratelimiter framework, since I didn't had time for an full burn in and didn't knew what the maxima / limits were. And since I hadn't finished that, I didn't finish the traffic shaping either.

Hm. Guess it's not good when you let a bunch of heavy parallelized data generators / analyzers run for free....

In the end, we simply shotgunned the docker development machines, because thanks to network congestion / retransmissions and feedback, they were not really cooperative via network / REST.

But hey: To infinity and beyond. XD

Sins? I don't want to keep you up all night, so here are some highlights.

Fucking with clients and employers who fuck with me first, or waste my time.

Occasionally not documenting my code (I'm actually pretty good about this), then bitching about poorly documented code.

Honestly wishing other people in the office would *actually* explode, or die engulfed in flames.

Working drunk and/or stoned.

Getting pissed off when I have to do something in a stupid way, or use a workflow that I don't like.

Seriously fucking up out of either arrogance or stupidity, then blaming it on something else.

Zoning out, skipping work, or sleeping in and billing for it (see sin #1).

But my greatest sin? That honor's got to go to becoming a developer in the first place.

I wasn't always a professional asshole, but I fucking am now.

Woohoo! Upgraded again and nothing went up in flames!

Biggest hurdle I have overcome is <b>myself</b>.

All my expectations, worries, fears, and doubts definitely caused major hurdles I had to crash through, trip and fall into, or they downright exploded into balls of fire as I would stand dumbfounded and burned by flames of regret.

Learning I was the blocker to greater achievement, success and ultimately happiness was a very hard lesson for me to learn, and a lesson and discipline that I still battle with today.

It is difficult to climb the seven story mountain of madness with heavy burdens, plodding with little progress.

Free the weight, and the natural warm air currents will lift high the spirit, and the body will follow.

"Angels fly because they take themselves lightly" ~GKC

Just saw someone ranting in an App Store review that Snapchat is crashing for them so they can’t collect Snapchat flames and that flames are more than just a number.

World is doomed.

Wanna know how to piss off an entire dev team?

Agree that progressive isn't good enough, must be native.
And supporting ie7 & 8 won't take much extra time or effort...

Late post because drinking:

I’m going back to work, got a verbal offer this afternoon after being laid off two weeks ago, thanks mainly to a referral from a former direct report that I once went to bat for. Gave myself a nice 3 weeks of chill time before start date.

But the funny thing was a company who gave me a take home assignment that I breezed through in half an hour, only to say “we’re going with other candidates” after the follow up interview calling me a few hours after I accepted said verbal offer elsewhere.

They wanted me to redo the take home assignment but with different acceptance criteria and requirements than the first time.

Fucking lol.

I told them, verbatim “I think I’ve done enough to satisfy any questions about my skills from the prior assessment. If you have more questions about design and implementation choices I’m happy to schedule a call.”

Hiring manager said he’d reach out next week.

Because even if the verbal offer gets redacted, I’ve got three other final rounds coming up and this particular place just sounded way too fucking chaotic and disorganized for my tastes. If everything else flames out and I’m left with no other options for work, I’ll consider giving them some more time out of my day, but as is, redoing a coding assessment with different criteria because you can’t decide wtf you want from a job candidate?

Not gonna lie: this is not a good look for you.

A QA engineer walks into a bar.
Orders a bear. Orders 0 bears.
Orders 99999999999 bears.
Orders a lizard. Orders -1 bears.
Orders a ueicbksjdhd.

First real customer walks in
and asks where the bathroom
is. The bar bursts into flames,
killing everyone.

After drilling yourself with links and resources, documentation and cant execute what you want. You leave it.

Some time later you go back and you are like why the hell didnt I understand this it's so simple :/ and it literally says what to do.

This is when I became a calm developer. Don't rush yourself. If you want to quickly do something. READ dont just look 🙃

Also, don't persist with understand the official docs. The third party explanations will show you flames 80% of the times if you are learning something new.

My superpower: having the flu will not affect me whatsoever...but it will get everyone else in my vicinity SICK af.

Which is why my sexy ass was sent home since Monday and I have been living life at home this week. I haven't taken a vacation in so long, and this feels nice. HR fucked up and their dumbasses said I was not "cleared" to work from home. Yet I have over 200 hours accumulated of sick leave.

My department is in flames because I am needed there. Of course, every other department thinks I don't do shit all day, the only one that knows how much I do is my boss, bless him. But for every other motherfucker that thinks that I am here just playing with my thumbs all day: eat shit...und die.

client: I want a flash website, with like flames that open to the menu!"

Hitting a really deep, deep low in the manic-depressive roller-coaster of the development cycle:

There comes the crunch time. No meeting goes by hearing the odious: "We don't have time for that." - One critical component needs to be finished for Big Sur and instead of addressing the real issues we keep changing design and goal. One main dev already gave up fighting the PO and team lead(!) - and now I'm next. So that dev build this really clean and minimal library as the core part. But now it's just like, yeah, take that nice Porsche engine put it on the old rusty bicycle from the shed,.. but maybe because that's so shitty we need that specially formed exhaust pipe to tune it. Yeah, very 'agile' - Only thinking about it makes me shudder in disbelief and anger. I shouldn't take that shit so serious, be emotional about shit code, I know, but I can't. Let them drive some rounds around the block, if it runs at all,.. because until now we still didn't make it run on the fuckin' street. It's all so insane. Will make some nice fireball, when it goes up in flames.

Well, I have been part of quite some shitty projects. Real suicide commandos set out to fail, and somehow stood them through or made it even "work" though it should never have. But what enrages me here is, that it needn't to be that way. We had plenty of time. Our team was often rowing along in good rhythm. And now I just feel drowned in resignation and sarcasm.

there is nothing more annoying than plugging the usb cable to the real android device for debugging, but if you move that cable 1mm the whole fucking connection breaks, the beep sounds of connected/disconnected phone rings, the fucking laptop explodes, phone explodes, dick explodes, the house gets on fire, my dog gets on fire, i run out of house while burning in flames alive and the whole house fuckin explodes like a nuclear bomb

Title: The problem with "good enough" code

Body:

I'm a software developer, and I've seen my fair share of "good enough" code. You know the kind of code I'm talking about: it works, but it's not pretty, and it's not very maintainable.

The problem with "good enough" code is that it's a slippery slope. Once you start writing "good enough" code, it's easy to fall into the trap of always taking the easy way out.

Before you know it, your code is a mess of hacks and workarounds. It's hard to understand, it's hard to maintain, and it's a nightmare to debug.

I've seen projects go down in flames because of "good enough" code. The code was so bad that it was impossible to fix, and the project had to be scrapped.

I'm not saying that you should never write "good enough" code. Sometimes, you just need to get something working, and you don't have the time or resources to do it perfectly.

But if you're going to write "good enough" code, you need to be aware of the risks. And you need to make sure that you're only writing "good enough" code for a short period of time.

Once you have a working prototype, you need to start refactoring your code and making it better. You need to make it more readable, more maintainable, and more testable.

If you don't, you'll eventually regret it. Your code will become a liability, and it will hold you back.

So next time you're tempted to write "good enough" code, think twice. It might save you some time in the short term, but it will cost you in the long run.

Suggestions for a good speech to text program for someone who mumbles and talks too fast?

I sliced my thumb while washing a knife and typing on my computer without it is getting annoying

Okay, it's getting a bit annoying to _hear_ my graphics hardware (NOT the fans. The circuits) working when I'm doing something on the screen.. Sometimes it feels like it's gonna snap and burst in flames or smth..

"If it’s a good idea and it gets you excited, try it, and if it bursts into flames, that’s going to be exciting too. People always ask, ‘What is your greatest failure?’ I always have the same answer—We’re working on it right now, it’s gonna be awesome!" - Jim Coudal

I remember when my sister borrowed the original Sims from one of her classmates. She would play and i would watch. One time she recreated our entire family as well as our home. Everything was fine and dandy until she tried cooking something. The kitchen burst into flames and burned the whole family alive so me, being 5 or so, literally cried for the rest of the day and never dared to play the game again. The end.

This was initially a reply to a rant about politics ruining the industry. Most of it is subjective, but this is how I see the situation.

It's not gonna ruin the industry. It's gonna corrupt it completely and fatally, and it will continue developing as a toxic sticky goo of selfishness and a mandatory lack of security until it chokes itself.

Because if something can get corrupted, it will get corrupted. The only way for us as a species to make IT into a worthy industry is to screw it up countless times over the course of a hundred years until it's as stable and reliable as it can possibly be and there are as many paradigms and individually reasonable standards as there can possibly be.

Look around, see the ridiculus amount of stupid javascript frameworks, most of which is just shitcode upon vulnerabilities upon untested dependencies. Does this look to you like an uncorrupted industry?

The entire tech is rotting from the hundreds of thousands of lines of proprietary firmware and drivers through the overgrown startup scene to fucking Node.js, and how technologies created just a few decades ago are unacceptable from a security standpoint. Check your drivers and firmware if you can, I bet you can't even see the build dates of most firmware you run. You can't even know if it was built after any vulnerability regarding that specific microcontroller or whatever.

Would something like this work in chemical engineering? Hell no! This is how fucking garage meth labs work, not factories or research labs. You don't fucking sell people things without mandatory independent testing. That's how a proper industry works. Not today's IT.

Of course it's gonna go down in flames. Greed had corrupted the industry, and there's nothing to be done about it now but working as much as we can, because the faster we move the sooner we'll get stuck and the sooner we can start over on a more reasonable foundation.

Or rely on layers of abstraction and expect our code to be compilable on anything the future holds for us.

So I want to build myself a custom buttonbox for star citizen and warthunder, my hotas really doesn't have enough or fittingly placed buttons for either of those games. What would be the best approach for this?
My first thought was to take an arduino or some AVR chip on an USB connection and write a custom JoyStick driver but that would be a major pain on the buttocks.
Also would I buy an Arduino or go full custom stuff and buy some chip from TI and DIY the board completly?

On the other hand if I'm gonna tinker with stuff on my own time I propably should pick up an ARM processor so I get familiar with the architecture, but that's propably overkill.
But 8-bit AVR is so constrained so maybe if I want to expand and create something like an MFD the poor 8266 would propably just go up in flames.

Has anybody a better idea or knows some ready to rock board for this kinda stuff? Best case scenario with a Joystick driver or something?

Small chaotic startup that never grew up (15 years atm).
Hosts/maintains a number of apps/sites for various customers.

At some point, someone decides that a CMS would be usefull to maintain the content across all products. Forgoing all sense, reason and the very notion of "additional maintenance and dev" it is decided that one should be built in-house.

Fast forward a number of years.

Ops performs routine maintenance on prod-servers. A java-patch accidently knocks out one of the pillars a 3rd party lib the CMS uses for storing images. CMS basically burst in to flames causing a.... significant incident.

Enter yours truly to fix the mess.
Spend a few days replacing the affected 3rd party lib. Run tests on CMS in test and staging environments. Apply java-patch. All seems fine.

When speaking to frontenders and app-devs, a significant hurdle present itself:
All test/staging instances of all websites/apps/etc ALL USE PRODUCTION CMS. Hardcoded. No way around.

There is -no- way to properly test and verify the functionality of any changes made to the home-brewed CMS.
My patch did indeed work in the end.

But did the company learn anything? Did they listen to my reasoning, pleading or even anguished screams for sanity?

No.

Some bitch posted a story "Fear God and obey God's commandments, because thats the only thing asked from mankind ❤️"

This fucking story fueled me

It enraged me

Blood boil

So fucking much that i had to let this shit out here

First of all, "FEAR God..."

If you fear someone who is supposed to love you, does that look like a healthy relationship to you?

"I love you so much", said the boyfriend to his girlfriend, "but if you dont love me back then I'll set you on fire so you can burn in flames and torment"

In that case do you love him because you genuinely truly love him, or do you HAVE TO love him because of fear from burning alive in fire and torment?

Think about that fucking scenario for a while. Imagine if that scenario happens in our world. The guy would be labeled as a psychopath and get arrested IMMEDIATELY.

But it's completely ok when God does THE EXACT SAME THING, just because hes God?

I'm a christian and even this fucks me up when i think about it. The more logical mind and critical thinking i acquire the more i see through the non logical bullshit.

My faith is shaky.

Im genuinely starting to think over 50% of religious people believe in God not because they genuinely believe, but because of fear of being set on fire and torment forever.

It smells to me like its a fucking MIND CONTROL FEAR DRIVEN CULT.

I'm literally one junior developer building a front end stack for a company that uses the waterfall method of building shit...

My application has not been fully tested and none of the real user base has actually tested it. I have no clue what potential egde cases exist in my application. I did as much testing as possible but it's keeping me on edge that there is potentially something broken lurking underneath that I don't know about.

If it is broken it's all erupting into flames and there's nothing I can do about it because the application will have to go through a whole beuacratic process to allowed to be fixed.

Need some advice here.

So hello everyone! I recently moved abroad for work, for the sake of the experience and the excitement of learning how developers in Latin America tackle specific problems. To my surprise, the dev team is actually composed solely of Europeans and Americans.

I work for a relatively new startup with an ambitious goal. I love the drive everyone has, but my major gripe is with my team lead. He's adverse to any change, and any and all proposals made to improve quality of throughput are shot down in flames. Our stack is a horrendous mess patched together with band-aids, nothing is documented, there are NO unit tests for our backend and the same goes for our frontend. The team has been working on a database/application migration for about a month now, which I find ridiculous because the entire situation could have been avoided by following very rudimentary DevOps practices (which I'm shunned for mentioning). I should also add that for whatever reason containerization and microservices are also taboo, which I find hillarious because of our currently convoluted setup with elastic beanstalk and the the constant complaints between our development environment and production environments differing too much.

I've been tasked with managing a Wordpress site for the past 3 weeks, hardly what I would consider exciting. I've written 6 pages in the past two weeks so our marketing team can move off of squarespace to save some money and allow us more control. Due to the shit show that is our "custom theme" I had to write these pages in a manner that completely disregard existing style rules by disabling them entirely on these pages. Now, ironically they would like to change the blog's base theme but this would invertedly cause other pages created before I arrived to simply not work, which means I would have to rewrite them.

Before I took the role of writing an entire theme from scratch and updating these existing pages to work adequately, I proposed moving to a headless wordpress setup. In which case we could share assets in a much more streamline manner between our application and wordpress site and unify our styles. I was shot down almost immediately. Due to a grave misunderstanding of how wordpress works, no one else on the team seems to understand just how easy it is to fetch data from wordpress's api.

In any event, I also had a tech meeting today with developers from partner companies and realized no one knew what the fuck they were talking about. The greater majority of these self proclaimed senior developers are actually considered junior developers in the United States. I actually recoiled at the thought that I may have made a great mistake leaving the United States to look a great tech gig.

I mean no disrespect to Latin America, or any European countries, I've met some really incredible developers from Russia, the Ukraine, Italy, etc. in the past and I'm certainly not trying to make any blanket statements. I just want to know what everyone thinks, if I should maybe move back to the states and header over to the bay/NY. I'm from the greater Boston area, where some really great stuff is going on but I guess I also wanted a change of scenery.

Long time nothing from Mr. Gitmaster, somehow made my peace with him as the project moved out of my focus and he actually seemed to be contributing.
But now some pull request exchanges burst into flames as if they were on LKLM before Linus got castrated. Actually it's with the guy who is jamming out most of the front end code trying to make a really shiny UI with lots of animations that turn our macs into heaters.
Well, debate was over JS code styles or lack thereof and how commented out code should be removed (would actually support Mr gitmaster here). They have me a bit lost there, as I expect the freestyle JS code we produce without any agreed Coding Style Guideline to be an even greater clusterfuck than our C++ code base.

Anyway, hope they come to terms again, like at the start of the project when they jokingly attributed one another as assholes. Their opposing characters could actually benefit from each other.

Hello all, I know we can search in git lab for the labels(easy, first commit etc) to find open source projects that suit me, but as a rookie it gets a bit frustrating not understanding the project and so on. Does anyone know a better way to contribute to open source and learning at the same time?

How many virtual box servers will it take for this desktop to go up in flames

Oh lord, may all GUI's come alive and eat their users, disintegrate their dev's and finally burst into flames and leave nothing but ashes.

Flames don't hurt as they used to
After once hearts went colder than the breath we take in
No matter how the lightning briskly strikes
We don't feel nothing since we already have a voice inside of us which never sleeps
Or take a rest, there are memories

Flames don't hurt as they used to
But they will never go away too
When our hearts want only some one
You don't get to choose
That's why when we love
We need to pay, Faith

Ok so I decided to do some Vue + Vite + Tailwindcss
OMG.... the flames I saw setting up tailwindcss in Vue 😢😢😢

A whole bunch of docs where all about setting it up in react
even after 24 hours I then found a doc that was specific for Vue
same commands for react as well where used
then I had to copy the last step and override the tailwind config file with those specific configurations

why tha fuck couldn't they just create Vue specific commands that generate configurations for Vue
WTF 🤨🤨🤨🤨

Does anyone knows what the hell is "coala" that's used for liting and fixing code? Cause I am pushing something and they said I need to fix my code using "coala" but I can't seem to figure it out what it is, how to install... I even tried to install in atom as plugin but that shit gives errors.

Trying to run AA games on a dual core Core2Duo without a graphics card is so fun. We try and try till we succeed right? Well trying is probably going to make my PC go up in flames😂😂

Hah. I was cleaning my screenshot folder and saw the bitbucket dying one night. It was after midnight and was in 'the zone'.

But still i love them :)

Guys. I am in deep shit. Literally. I am shitting on my brown throne and the shit was going out normally. Felt good. But i couldnt stop shitting. There was so much shit. I was such a shitlord. The volume of my shits was so large an entire amazon warehouse wouldnt fit. Then at one point my asshole started burning🔥 i had to clutch and close my asshole. The more i shit the more it burned. Then my shit piled up. It felt very liquid. Then i realized it was diarrhea💩💩💩💩💩 fuck. I kept my asshole closed at all costs but something went wrong in my stomach. The liquid shit kept piling up and i dont know why or from where. How can so much shit be stored in my body is beyond me. The shit i shitted was longer than average sized snake🐍 then at one point the pressure and force F=ma 2nd newtons law kept making it harder because holding the shit hurt, but shitting the shit also hurt cause it burns🔥💩 but heres the best part. As i was at war with my shit i remembered what I learned in school: 3rd newtons law Each action has an equal and opposite reaction, then i realized if i just let go of my shit and suffer the pain of having the asshole on flames, the reaction of the opposite newton's force would throw that shit to the other side so i dont have to suffer holding my bullshit inside me! And so i did. I let go of my asshole and liquid shit was FLOWING like a fucking waterfall 🌊💩🌊💩🌊💩 asshole burned for 3 seconds but the relief i felt from not holding so much bullshit inside was WORTH IT💯 Now, if you excuse me its time i get off my brown throne and IMMEDIATELY run to my chair or else im gonna collapse to the ground. My legs are literally NUMB from shitting for over 20 minutes on my throne. Thank you school for teaching me all about bullshit! I would have exploded and died if i didnt study bullshit in school. My degree of bullshit is just as valuable as bullshit, and they were right. I am glad i studied shit in school. Never knew shit could be useful to learn

Can anybody point me to some really good resources, guides, videos etc for umbraco website development.

Our firm has inherited a couple of these sites from another company and your's truly has to somehow or other maintain them. I've set up a windows host and migrated the sites and everything is running fine but I'd love to know how I go about making an umbraco site from new. I've got visual studio etc and am willing to learn ASP.net, C# etc.

I've always been an PHP/MYSQL dev using open source stuff, and always thought that I'd burst into flames if I touched anything Microsoft but this stuff looks like it might be useful. Whoever would have thought eh?

My head is going to burst into flames 🔥🔥🔥🔥🔥