click click...

*reload*
_________________
| |
| This will be wra|
| |
|_________________|

hm.....

ah...

*hits ctrl+s*
*smiling*
*reloads*

_________________
| |
| This will be wra|
| |
|_________________|

what the f..
..
..
hm....
hm....

aha
ctrl+alt+t
*confidentiality*
sudo sublime /opt/htdocs/learning_css/wrapping_text.html

********
o.O but my code ....it's here.....but why wasn't it showing....

*just to be safe*
ctrl+s
*reload*

_________________
| |
| This will be wra|
| |
|_________________|

meh..... what was I thinking

*wastes time restarting xampp*
*searches CSS everywhere*
*steals working code*
*eyes red as hell*
*it's 3 am*
*after 1hr*

*accidentally reloads*

_________________
| |
| This will be |
| wrapped |
|_________________|

o.O
*blinking in confusion*
what the .... how did it work....
I changed nothing.....

*realises*

I. FUCKING. HATE. MOBILE. DEVELOPMENT.

I already manage the data, devops, infra, and most of the backend dev.

We had a mobile guy. He was great. I never had to think about it and kept moving quickly on my work. #SpecializationOfLaborFTW

He left. Why? Because they wouldn't give him a small raise despite being one of the best mobile engineers in the firm. WTF.

I made the mistake of picking up just enough slack on this workflow in the interim such that I'm, apparently, the fucking god-damned release manager, fixer of pipelines, fixer of build configs, fixer of anything where someone just needs to RTFM for a half-hour to not fucking break things.

Now, 8 months later...and, apparently, Fortune 500 companies are too fucking god-damned cheap to pay for someone who actually knows WTF they're doing for a very reasonable thing to have at least one dedicated set of eyes for.

I never wanted to be a mobile dev.
I never will want to be a mobile dev.
And I certainly don't want to manage your HALF-FACE-FUCKED detached expo configs.

There's a reason I never intentionally involved myself in mobile. All the way down, it's just shitty cross-compilation, transpilation, dependency-hell, brittle-as-fuck build processes so we can foot-gun and mouth-gun react-native and expo and babel and whatever the fuck else cargo-culted horseshit into the wild.

And why? What's the actual fucking root cause? The biggest white elephant that ever fucking elephant-ed? It's because Apple and Google decided to never collaborate on a truly-native cross-platform SDK--where engineers could write native code that compiles to native binaries that's simply write-once, run-everywhere. They know they could have done that, and they didn't. So what'd they get back? Expo--a too-cleverly-designed backdoor/hack--more-or-less a way to circumvent the sane release process software has usually followed: code -> executable -> deploy. Or code -> deploy (for interpreted langs). Expo's like "keep your same executable, we're just gonna to do updates by injecting new code into it whenever we want". Didn't we learn anything with web? Shit gets messy real quick? Not to mention: HEY EXPO, WE WERE ALREADY BUILDING NATIVE APPS, YOU SHORT-SIGHTED FUCKS. THANKS FOR LURING OUR CTOs INTO FORCING EXPO DOWN OUR THROATS W/ THE IMPLICIT (BUT INCORRECT) TOO-GOOD-TO-BE-TRUE PROMISE THAT WE CAN HAVE WRITE-ONCE, RUN-ANYWHERE WITHOUT ANY BUY-IN OR COOPERATION FROM THE ACTUAL TARGET PLATFORMS.

And, we just, like, accept this? We all know it's garbage engineering. The principles we learned in the classroom aren't just academic abstractions--they actually yield real-world results--and eschewing them yields real-world failures. Expo is tightly-coupled to high-heaven, with leaky abstractions six-ways-to-christmas, chock-full of foot-guns, and fails the most basic test of quality: does it, "just work?"

Expo is fucking shameful and it should fucking die. Its promises are too bold, its land-mines too many, its future-proof-ness is alway, always, always questionable as fuck and a risk to every project that uses it.

You want a rant? This is my fucking venue, 'tis not? Well, then this is a piss and vinegar rant straight from my blood-red, beating fucking heart:

EXPO FUCKING SUCKS. AND IF YOU'RE A FAN, YOU FUCKING SUCK TOO.

still early to doubt my react skills .-.

So
I wrote a song
About devRant
Don't judge me

To the tune of "Rudolph the Red Nosed Reindeer"

dfox and trogus
Had a very good idea
They worked on it
And out popped devRant
Then one foggy Friday night
They published it
It was an instant hit
Devs everywhere rejoyced

Now the devs love them
As they type out their rants
dfox and trogus
You'll go down in dev history!
(Like Linus Torvalds!)

Coding has changed the way I think. Everywhere I go, I think of algorithms and efficiency.

When I'm in elevator, I think about what algorithm is running in the background.

When I'm at red light, I think about the algorithm that traffic lights are running.

I notice bugs in websites and apps and try to figure out what the dev might have done.

I find problems in UI design and get annoyed.

I spend more time coding a solution to a problem rather than directly solving the problem. I get a kick out of it.

When I see something uses more resources than necessary, it seriously pisses me off.

Coding has taught me to think and has positively changed the way I live.

Nightmare IRL:

Your colleague is in PTO for 2 weeks.

You are in charge of maintaining his project along with yours, CI, code, tests and everything.

Your colleague's code base is a real master piece of shit when you look at it closer. By shit, I mean hardcoded values everywhere, random sleeps now and then, 20 if branches that could be replaced by maps, variables named a b c d everywhere, try catch to silence errors that should not be silenced, etc.

Your colleague left the CI and code broken as shit. Takes forever to run on my goddamn computer.

PMs are spamming you: "What is going on? It's red everywhere. Help! Plz fix this! We are going to release tomorrow!"

FML

C# has become shit.

I work since 2013 with C# (and the whole .NET stack) and I was so happy with it.
Compared to Java it was much lean, compared to all shitty new edge framework that looked like a unfinished midschool project, it was solid and mature.

It had his problems,. but compared to everything else that I tried, it was the quickes and most robust solution.

All went in a downhill leading to a rotten shit lake when all this javascript frenzy began to pop up and everyone wanted to get on the trendy bandwagon.

First they introduced MVC, then .NET Core, now .NET 5-6-7-8.

Now I'm literally engulfed with all these tiny bits of terror javascript provoked and they've implemented in all the parts of their framework.

Everything has to be null checked at compilation time, everything pops up errors "this might be nulll heyyyyy it's important put a ! or a ? you silly!!!" everywhere.

There are JS-ish constructs and syntax shit everywhere.

It's unbearable.
I avoid js like a plague whenever I can (and you know it's not a luxury you get often in the current state of a developer life) and they're slowly turning in some shit js hybrid deformed creature

I miss 2013-2018, when it wass all up to me to decide what to do with code and I did some big projects for big companies (200-300k lines of code without unit tests and yes for me it's a lot) without all this hassle.

I literally feel the need c# had to have some compiler rule you can quickly switch called "Senior developer mode" that doesn't trigger alarms and bells for every little stupid thing.

I'm sure you can' turn on/off these craps by some hidden settings somewhere, but heck I feel the need to be an option, so whoever keeps it on should see a big red label on top of the IDE saying "YOU HAVE RETARDED DEV MODE ON"

So they get a reminder that if they use it they are either some fresh junior dev or they are mentally challenged.

So..there is 2 of us working on a Wordpress site, my job is front-end and make it look nice, the other persons job is to do some backend development(dont ask me what and why, I have no idea). Basically, I was waiting for the other person to finish his part so I can do front end development. I was expecting it to be just a theme, and then I fix it, add new stuff, etc etc, like usually..but the horror I saw, THE FUCKING "BACKEND" PERSON HAS ACTUALLY MADE A FUCKING THEME EVEN THOUGH IT IS MY FUCKING JOB. Now dont get me wrong, I wouldnt mind if I did almost zero work and got paid, but..THE FUCKING THEME WAS UGLY AS A TWO HEADED DICK SMOKING A FUCKING CIGARETTE. There was STRONG RED FUCKING EVERYWHERE, padding between posts was basically -20px. Well ok, I could have just started making a new theme, but there was already some stuff in this one we needed so I went it it and tried to make it look nice. And trust me, it is great now, great colors, fonts, shadows, button animations, everything, even looks great on mobile.

I started making some changes to the header, and I noticed that post title changes also..hmm wonder why..So I inspect element and what do I see, TAG OF THE FUCKING POST TITLE IS <HEADER>???? WHAT THE ACTUAL FUCK, IF YOU TRIED TO DO SOME FRONT END, AND YOU SAY YOU KNOW SOME, WHY DO FUCKING FUCK WOULD YOU DO THAT???????? WHY THE FUCK WOULD YOU DO MY JOB IF YOU SUCK AT IT??? DONT DO MY FUCKING JOB, I SUCK AT "BACKEND" AND I DONT FUCKING DEAL WITH DATABASES OR TRY TO MAKE THEM FOR YOU!!!!! AAAAAAAAAAAAAAAAAAAAAAAARHHHHHHHH FUCK

I'm new here and yesterday, I had the opportunity to create my Avatar, great! BUT, I noticed a bit of Gingerism here! ;)

1) Where is the freckles skin tones? Where!! I have freckles everywhere! I want freckles everywhere!! Well.. not really everywhere...

2) I tried to select Red Hair color, but the avatar still have that grey color! I want Red Hair! (Ok I admit, I don't really have red hair...)

what. fucking. day.

my ex blonde whore got mentally,

T O R M E N T E D.

ripped apart.

absolute, psychological, Destruction.

a great, great Evil, is gonna be born out of what ive done

worse than frankenstein evil

and this evil, will be spread across the entire world

it will infect and affect, you

i cannot imagine how fucked up the future is going to become

this day is completely FUCKED and i cannot wait for the moment till this shit is over

what happened?

too much random fucking bullshit happened! this day is as random as it can fucking get

warning: you'll gonna get a headache reading this fucking rollercoaster of emotions

1) worked

2) was angry at my ex blonde whore cause she doesnt want to block the fuckboy she cheated on me with

3) told her this. argued with her. shes stubborn and doesnt want to block him

4) i blocked her everywhere (for 500th fucking time). this time including ig. she cried at work. barely could focus

5) after work from a fake acc i saw she posted MY fucking bmw

6) second story she posted SITTING INSIDE OF MY FUCKING BMW WITHOUT MY FUCKING PERMISSION

7) WHAT THE FUCK. MAD AS FUCK, I called her on phone asap. she answered. i said i wanna talk. she wanted to go out for coffee. fuck that. lets go to her place. she asked u wanna fuck me. i said i fucking do. im horny too, she said

8) came over. fucked her. discussed. talked. argued afuckinggain. unblocked. i pretended ig glitched out and i saw that story. told her who the fuck u think u is to steal my fucking key of my bmw and sit in my fucking brand new bmw?!!! WHORE

9) then fucked her again. but cuddled her kissed her gently, she said "you're such a fucking mentally ill maniac", while smiling hugging me and kissing me. she loves The Joker type of guy who fucks with her emotions. "you give me rollercoaster of emotions" she said. when she went in shower to wash off my cum i grabbed her phone and blocked her fuckboy she cheated on me with (shes secretly in love with him)

10) when she saw this her whole fucking mood swapped. 180. asked why did u go through my phone. i said why did you fucking steal my bmw key and sit inside of it

11) now we're even. i crossed the red line and blocked your fucktoy from your phone and you crossed the red line stealing my fucking key of an expesnive car and sitting inside it at 7:30am while i was sleeping. Fuck you WHORE

12) she sent the pics of my fucking bmw to chatgpt and asked how much this car costs so she estimates how rich i fucking am. This relation is BEYOND FUCKING TOXIC AND LETHAL THAN YOU CAN IMAGINE

13) "now that hes blocked can you drive me in ur bmw now for the first time" she asked. i was resistent. I FUCKING blocked him not YOU, whore. and you're giving me an attitude now. she looked at me angry, deadly, the look of "im gonna do you dirty for this i promise". fuck that whore

14) at the end i said i can drive u only under the condition that he remains blocked forever

15) deal. i repeated the fucking seriousness of this numerous times. its gonna get more fucked and toxic if she ever unblocks him. we agreed so i drove the bitch whore for first time. she was amazed of my bmw

16) when i thought it was all over and i can relax, as we were driving ANOTHER BITCH CALLED ME ON MY PHONE. AND HER NAME AND NUMBER WAS DISPLAYED ON THE BMW SCREEN. FUUUUUUUUUUUCK. please

17) i completely forgot that i set up a coffee meeting with this new bitch. (this new bitch is fat and ugly btw i just wanted to go out with her cause she has good personality and wanted to talk random stuff so i shift my mind off blonde ex whore)

18) blonde ex whore was not happy. asked me who is that. FUCK. i said some random girl

19) i left my blonde whore home. kissed. then went over with that new girl for a drink. talked. drove her. blond ex attacked me who is she, and to give her phone number so she calls her to check what she has to do with me. FUCK!!!

20) as i was sitting with that new girl i had to explain her all this bullshit. embarrassed. belittled. fuckwd up. whilw i was explaining my blonde whore found her ig and told me to tell her everything or else shes blocking me.

21) the blonde whore blocked me! everywhere! lol. for the first time ever. fuck off. now she knows how i felt, betrayed!

22) fucked up. blonde ex wrote to new girl why did she call me and what do we have between each other cause shes my gf. WHAT FUCKING GF YOU DUMB BITCH YOU FUCKING CHEATED ON ME!!!!! FUCK YOU

23) i told this new girl to write her she needed me for college cause I'm an IT guy and they dumb af dont know how to use word or excel

24) blonde ex bought it (i think)

25) when i got home i called my blonde whore on phone. she answered. her voice seemed like she overdosed on drugs. "did u fuck that girl" she asked. No. i was riding my bmw.

26) explained her the new girl is ugly and just wanted college help. i wouldnt fk her (truth). ex whore unblocked me and said she wants me to cuddle her tomorrow and sleep in bed

Once upon a time in the exciting world of web development, there was a talented yet somewhat clumsy web developer named Emily. Emily had a natural flair for coding and a deep passion for creating innovative websites. But, alas, there was a small caveat—Emily also had a knack for occasional mishaps.

One sunny morning, Emily arrived at the office feeling refreshed and ready to tackle a brand new project. The task at hand involved making some updates to a live website's database. Now, databases were like the brains of websites, storing all the precious information that kept them running smoothly. It was a delicate dance of tables, rows, and columns that demanded utmost care.

Determined to work efficiently, Emily delved headfirst into the project, fueled by a potent blend of coffee and enthusiasm. Fingers danced across the keyboard as lines of code flowed onto the screen like a digital symphony. Everything seemed to be going splendidly until...

Click

With an absentminded flick of the wrist, Emily unintentionally triggered a command that sent shivers down the spines of seasoned developers everywhere: DROP DATABASE production;.

A heavy silence fell over the office as the gravity of the situation dawned upon Emily. In the blink of an eye, the production database, containing all the valuable data of the live website, had been deleted. Panic began to bubble up, but instead of succumbing to despair, Emily's face contorted into a peculiar mix of terror and determination.

"Code red! Database emergency!" Emily exclaimed, wildly waving their arms as colleagues rushed to the scene. The office quickly transformed into a bustling hive of activity, with developers scrambling to find a solution.

Sarah, the leader of the IT team and a cool-headed veteran, stepped forward. She observed the chaos and immediately grasped the severity of the situation. A wry smile tugged at the corners of her mouth.

"Alright, folks, let's turn this catastrophe into a triumph!" Sarah declared, rallying the team around Emily. They formed a circle, with Emily now sporting an eye-catching pink cowboy hat—an eccentric colleague's lucky charm.

With newfound confidence akin to that of a comedic hero, Emily embraced their role and began spouting jokes, puns, and amusing anecdotes. Tension in the room slowly dissipated as the team realized that panicking wouldn't fix the issue.

Meanwhile, Sarah sprang into action, devising a plan to recover the lost database. They set up backup systems, executed data retrieval scripts, and even delved into the realm of advanced programming techniques that could be described as a hint of magic. The team worked tirelessly, fueled by both caffeine and the contagious laughter that filled the air.

As the hours ticked by, the team managed to reconstruct the production database, salvaging nearly all of the lost data. It was a small victory, but a victory nonetheless. And in the end, the mishap transformed into a wellspring of inside jokes and memes that permeated the office.

From that day forward, Emily became known as the "Database Destroyer," a moniker forever etched into the annals of office lore. Yet, what could have been a disastrous event instead became a moment of unity and resilience. The incident served as a reminder that mistakes are inevitable and that the best way to tackle them is with humor and teamwork.

And so, armed with a touch of silliness and an abundance of determination, Emily continued their journey in web development, spreading laughter and code throughout the digital realm.