Details
Joined devRant on 12/16/2020
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
CODING CODING CODING HAHAHA I LOVE PROGRAMMING BEING A LITTLE CODE SLUT. I LOVE SILICON VALLEY IM SUCH A QUIRKED UP LITTLE CODE SHAWTY LOOKING FOR SOME ALGOASS 🍆💦😩.
“Slams fists on keyboard”
I LOVE BEING A CUTE SCREEN TWINK, IMPRESSING PAPI CEO WITH MY FINGER COMBINATIONS. I LOVE PLEASING EXECUDADDY. 🍑😏🫦
“Takes keyboard in hand and slams it against desk until keyboard keys explode everywhere”
I LOVE WATCHING THE AMERICAN GOVERNMENT AND CORPORATE AMERICA FUCK MY ASS IN RETURN FOR PERSONAL PROFITS. 🤑☔️
*digs fingernails into the wall and claws off paint and then snorts it”
*pees and shits pants*
*cries in corner with extra agony*21 -
Becoming an 'almost' decent developer these past few years has made me realize how absolutely undeserved my ego was back in high school when I first joined DevRant and StackOverflow and thought i was 'all that' just because i did some programming thing stupid teenagers found cool in a random school.
At 24 I can say I'm happy for the internet knocking me down a few pegs when my 16-17 year old ego got out of hand. I feel it's really made me better in the long run.
Thank you DevRant2 -
FaceBook, over the years you’ve proven that you can’t be trusted and you still have the nerve to ask for this type of personal data?5
-
Features of any software product development: there is a catastrophic lack of time to get rid of bugs, but always enough time to make them even more. 🤦♂️
-
If Apple made an electric car, they would make all the charging stations incompatible every two years.12
-
If you ++ this post, you will get good developer karma credits for the next 10 years, and every piece of code you write will eventually work.
Trust me this actually works, you can try it yourself.2 -
“One of the biggest mistakes engineers make is spending time on optimising something (a component) that shouldn’t exist in the first place” - Elon
I’ve been guilty of this a few times 😅2 -
Found a very interesting use case of git and github, it seems that even government such as the Washington DC City council uses Git & Github to publish laws! Citizens have even given PRs to fix certain typos through git :p.
https://government.github.com/commu...8 -
Optimizing the queries and backend
OR
Hiding the waiting time with funny animations and weird preloading techniques
Catch: let marketing decide10 -
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.27