Things I've learned throughout my 5 - 6 years as a programmer.
- StackOverflow is full of assholes.
- CMS's are for weaklings.
- The best feeling about waking up in the morning is figuring out how to solve that error in your code.
- You no longer think about normal people things. Your mind is full of code.
- You're practically a computer.
- ALWAYS backup and save your stuff or you WILL regret it. Enable autosave if possible.
- RIP your social life (if your friends don't know squat about programming)
- Darkness is better.
- Being a programmer is amazing.

I've become so numb , I can't feel you there.
#rip

You: Wearing a headset and send pic of you to girl
Girl: Are you a pilot?

You: rip life

RIP both my social life and my phones battery life 😂

In memory of the giant of engineering that was Larry Tesler, today I will be coding solely by copying and pasting. Thanks for making my life so easy, Larry. RIP.

Ever since i was a little boy, i was fascinated by the stars in the sky and what made them shine. I used to wonder how our universe came in to being. What made it what it is today. What will happen to it long after we re gone. Will it die? Will it live forever? How big is it? Why is it big if it s big and why is it small if it s small. "God did it" was never a satisfying answer for me. God does not play dice as Albert Einstein said. So many questions went through my 10 12 year old mind. Until someone recommended to me the book, "A brief history of time". The book answered a lot of my questions and gave birth to more. Computer science is like my crush. I love it as a friend. But Astrophysics, its the true love of my life. It not only quenches my thirst, but it satisfies my curiosity, while making me more curious. Its an endless cycle. It teaches us that we came from the stars, we go back in the dirt, and only to be returned to the stars again.
Stephen Hawking, his work, his books, taught me so much. Inspired me. Made me more curious. And today the world has truly lost, one of its greatest people.
You will be missed Sir Hawking. RIP.

Not sure if this is necessarily a prank, but I was working on a team that was split in 2. We had a group of senior devs in one country, and junior devs in another (god only knows why, and yes I complained about this a lot).

The "lead" of the juniors was very stubborn and refused to adhere to the official standards, as his way was better.

I was working on an app with him, I was fed up with how badly the app was working, how hard it was to find files etc. So I waited for him to be off on holidays and pulled some extra hours to completely re-do the folder structure, rip out his persistence layer and a few other things.

When he came back he lost his shit and complained to the architect. The architect (also fed up with his shit) told him that we don't have the time to invest in reverting back everything, and loosing all the new features I added on top, especially since the app is now adhering to standards.

Never felt such satisfaction in my life.

Github 101 (many of these things pertain to other places, but Github is what I'll focus on)

- Even the best still get their shit closed - PRs, issues, whatever. It's a part of the process; learn from it and move on.

- Not every maintainer is nice. Not every maintainer wants X feature. Not every maintainer will give you the time of day. You will never change this, so don't take it personally.

- Asking questions is okay. The trackers aren't just for bug reports/feature requests/PRs. Some maintainers will point you toward StackOverflow but that's usually code for "I don't have time to help you", not "you did something wrong".

- If you open an issue (or ask a question) and it receives a response and then it's closed, don't be upset - that's just how that works. An open issue means something actionable can still happen. If your question has been answered or issue has been resolved, the issue being closed helps maintainers keep things un-cluttered. It's not a middle finger to the face.

- Further, on especially noisy or popular repositories, locking the issue might happen when it's closed. Again, while it might feel like it, it's not a middle finger. It just prevents certain types of wrongdoing from the less... courteous or common-sense-having users.

- Never assume anything about who you're talking to, ever. Even recently, I made this mistake when correcting someone about calling what I thought was "powerpc" just "power". I told them "hey, it's called powerpc by the way" and they (kindly) let me know it's "power" and why, and also that they're on the Power team. Needless to say, they had the authority in that situation. Some people aren't as nice, but the best way to avoid heated discussion is....

- ... don't assume malice. Often I've come across what I perceived to be a rude or pushy comment. Sometimes, it feels as though the person is demanding something. As a native English speaker, I naturally tried to read between the lines as English speakers love to tuck away hidden meanings and emotions into finely crafted sentences. However, in many cases, it turns out that the other person didn't speak English well enough at all and that the easiest and most accurate way for them to convey something was bluntly and directly in English (since, of course, that's the easiest way). Cultures differ, priorities differ, patience tolerances differ. We're all people after all - so don't assume someone is being mean or is trying to start a fight. Insinuating such might actually make things worse.

- Please, PLEASE, search issues first before you open a new one. Explaining why one of my packages will not be re-written as an ESM module is almost muscle memory at this point.

- If you put in the effort, so will I (as a maintainer). Oftentimes, when you're opening an issue on a repository, the owner hasn't looked at the code in a while. If you give them a lot of hints as to how to solve a problem or answer your question, you're going to make them super, duper happy. Provide stack traces, reproduction cases, links to the source code - even open a PR if you can. I can respond to issues and approve PRs from anywhere, but can't always investigate an issue on a computer as readily. This is especially true when filing bugs - if you don't help me solve it, it simply won't be solved.

- [warning: controversial] Emojis dillute your content. It's not often I see it, but sometimes I see someone use emojis every few words to "accent" the word before it. It's annoying, counterproductive, and makes you look like an idiot. It also makes me want to help you way less.

- Github's code search is awful. If you're really looking for something, clone (--depth=1) the repository into /tmp or something and [rip]grep it yourself. Believe me, it will save you time looking for things that clearly exist but don't show up in the search results (or is buried behind an ocean of test files).

- Thanking a maintainer goes a very long way in making connections, especially when you're interacting somewhat heavily with a repository. It almost never happens and having talked with several very famous OSSers about this in the past it really makes our week when it happens. If you ever feel as though you're being noisy or anxious about interacting with a repository, remember that ending your comment with a quick "btw thanks for a cool repo, it's really helpful" always sets things off on a Good Note.

- If you open an issue or a PR, don't close it if it doesn't receive attention. It's really annoying, causes ambiguity in licensing, and doesn't solve anything. It also makes you look overdramatic. OSS is by and large supported by peoples' free time. Life gets in the way a LOT, especially right now, so it's not unusual for an issue (or even a PR) to go untouched for a few weeks, months, or (in some cases) a year or so. If it's urgent, fork :)

I'll leave it at that. I hear about a lot of people too anxious to contribute or interact on Github, but it really isn't so bad!

I'm in a situation here, I had an idea for an app and I started coding it. Since I'm a front end developer I find it not amusing to do the backend part. I then started to share the idea and such with good classmate (not a coder). I then made him join me on this adventure. After a lot of coding he said he wanted to contribute with something since I'm coding all day and he's not. Then we agreed freelancing the back end part.

Some time later we got a pretty good deal on some Indians doing the whole app. I thought to myself "this feels kinda good!" so we went on with the freelancer.

Days went to months and we finally got the app back. I did a mistake of paying him all the milestones without testing the app in its wholeness, later finding out that one part of the login system didn't work. That lead to a deeper debug to find out that the core function of the app was commented out.. I then wrote the freelancer back with minimal and slow response.

Now the deadline of the app is like in 2 months. If not we miss a whole year.

My classmate knows about this and he's the one who played for the freelancing. Now we have talked about me doing the whole backend myself.

The only issue I have now is that I feel like he's just sitting home doing nothing other than flashing money around and me busting my ass of writing code that I really am not good at. (basically learning more than coding)

But he played a lot of money for this.. So I feel kinda bad for him.

Rip life.

Ahh, Unity’s “Wheel Joint.” Who knew it had “polarity.” I spent good several f*<king hours debugging this $h!+ just to find out I just placed them backwards on a 2-D car. Instead of the joint turning the wheels, they were trying to “turn the chassis.”
This meant the chassis received an impossible force which would rip it in half in real life. Of course, this was a unity game, so what happened instead was the physics engine flipping out which sent the car into the air!
I guess it was good for some lulz, but it took way too long to debug. I guess it’s time to take a little time off of that project.

My headphones went in the washing machine!!!

At a "guided internship".

Task: Develop a complete web application form

Was assigned to a team of 7 where all are "Frontend Developers" who have never heard terms like "bootstrap" or "mobile-first web pages".
That aside, all are seniors in age and qualifications, hence me telling them something to do is "ordering them around". And if I tell them to leave things to me, they be like "No, we wanna contribute and do the Frontend, as these things don't matter, inline css just works fine". 🤷🏻‍♂️🤷🏻‍♂️🤷🏻‍♂️🤷🏻‍♂️🤷🏻‍♂️

Why Lord? Just why?

I haven't felt an urge to post on here in a while just because things have been going so well. But this month, is just not that kind of month anymore.

I'm upset. I'm upset by how I've been uprooted from my routine. I know I shouldn't be that bothered by it and things always change. But what the fuck is this company thinking to be using it's own fucking home baked ticketing system!

WHAT THE EVER LIVING FUCK IS THIS SHIT!

Let's go over the issues it has
1. I can't fucking email my clients through it
2. all emails are not recognized automatically. In other words each new email creates a new ticket if it does not have the tracking number attached to it.
3. I have to fucking hunt around in my inbox that is now bombarded by every email that is created for this ticketing system. Slap on a fucking tracking number. And then HOPE TO FUCKING GOD that the person on the other end doesn't erase the subject and cause the system to create a new ticket just for it.

Let's go over Zendesk which they've decided to decomission.
1. I. DON'T. HAVE. TO. DO. ANY. OF. THAT. FUCKING. SHIT.
2. That's it. It's fucking simple

Seriously. They forced me off of my original platform because this company already had a "ticketing system", if you can even fucking call it that, working.

And just if you weren't aware, all of this change happened because my company got bought out. It got bought out by this behemoth company that isn't willing to let me continue using a system; that has been very efficient, mind you, and instead make me use their system.

I. FUCKING. HATE. THIS.

Every fucking day! I have to do this stupid bullshit of emailing clients from my personal work email instead of on the direct ticketing system.

When I first started using this thing I actually thought I could use it to email the clients. For a solid two weeks I was "communicating" to clients through their ticketing system. Only to find out that the entire time those clients were not getting my actual fucking email! WHAT THE ACTUAL FUCK?

Then these guys tell me after the fact. "Oh that's strange... We never noticed that you can't send emails through it... We always just had used our work emails."

Are you fucking jerking my chain! You guys have literally been sitting in this slimy pit of hell for so long that you don't even know there are better options out there!

You don't have to fucking live this life!!

I don't think I'm going to make it. Something needs to change. And I know upper management isn't going to do it, because I fought hard to try and keep Zendesk. They are not keeping it. After this next quarter it is officially gone.

I'm trying to think of coding solutions to make my situation better... But I shouldn't have to fucking do that! There are perfectly good working solutions out there, and this company doesn't want to budge because "that's the way we've always been doing it"

I'm going to fucking rip out my hair.

i hate you, you and you AHHHHHH

This doesnt have to make sense.
This is a freakin rant for god's sake, not a pull request. I'm not tryna be the best ranter?? Dont mind this rant. Just scroll. B if u can only hear my scream right now from the other side of the world, it sure can cause another big bang.

F u, this sht, (oh ya it's profanity, i got no better term for what im feelin, gahh please rip my head off) and that too, and this one too, all of u

I HATE ALL OF YOU. I BLAME ALL OF YOU FOR ALL MY INCONSISTENCIES. YE, IM TIRED OF TAKING ACCOUNTABILITY. F THAT SHT COZ IT JUST RAISES EXPECTATIONS. I CAN'T EVEN MEET THE DEADLINES I SET FOR MYSELF.

The hell are ambitions and all that "dream life" they tryna sell. Those won't even matter when I can barely get my sht together. UGH. I haven't even seen my friends, the SUN, trees and all normal people things. Dang, I want fried chicken. I haven't had one for a while. I guess I should end this rant here and order one.

I must just be hungry, no?

I didn't choose the iOS developer life, the company chose it for me. RIP

Early on in my freelancing career I learned something important. Even with seemingly tame nerdy stuff, sh*t can get real, real quick. This story describes the very start of my career in web development and hopefully will serve as a warning to newbies out there.

A young teen, I had just learned some basics of wordpress, I was confident I could hack together something that worked and looked okay with minimal effort and knowledge. One day I was approached by a guy who wanted a job board board site. Knowing there were already clones out there I figured this would be an easy gig, man was I wrong.

In addition to the fact I didn't know about contracts or the scope creep from hell, I had somehow gotten myself involved with a criminal business front.

These guys operated a scam business to rip off investors. Me and my designer buddy were used to make the business look legit. What they would do is hold job fairs where people are supposed to pay to rent a booth, but instead they would give everyone a booth for free and then lie about what all businesses were coming. They would then show this info, along with the website and marketing materials to investors. They would take the money from the investors and launder it for drugs.

The real story starts the day of one of the worst hangovers I had ever had. I was at a random friends house sleeping for most of the day.

Apparently one of the guys who was operating the scam business was about to strike a deal with one of the investors when something on the website didn't work (it was working as designed). This guy, Manny we'll call him, had been blowing up my phone all morning. I check my voicemails and there are threats on my life; saying I will be sleeping with the fishes, or if they ever find me, they'll fuck me up. Needless to say this really freaked me out, either way I decided to head back to my dorm.

When I come back home, my designer buddy tells me that some guys were in the house looking for stuff. Apparently this guy hired two nerds to "break into my computer and steal the website", fortunately they didn't know what they were doing.

After a while I got another call, Manny wanted to sit down and "talk things out". Being naive I accepted and we met up. The two nerds were there with one of his body guards. He said he wanted to have those two nerds take over the project. While this was going on, his bodyguard flashed his gun at me several times making eye contact. I agreed to, but I still wanted to get paid. I asked about getting paid and he said we never signed a contract and that he owned the host and domain. I was pretty much screwed.

This is where the story should end, but I wasn't a very smart guy back then. I gave up the site but I created a back door into it. Every week or so, they would get "hacked". Because the two nerds didn't know what to do, they ended up coming back to me for help. This is when I finally got paid. Totally not worth it.

Ok, so I need some clarity from you good folk, please.

My lead developer is also my main mentor, as I am still very much a junior. He carved out most of his career in PHP, but due to his curious/hands-on personality, he has become proficient with Golang, Docker, Javascript, HTML/CSS.

We have had a number of chats about what I am best focusing on, both personally and related to work, and he makes quite a compelling case for the "learn as many things as possible; this is what makes you truly valuable" school of thought. Trouble is, this is in direct contrast to what I was taught by my previously esteemed mentor, Gordon Zhu from watchandcode.com. "Watch and Code is about the core skills that all great developers possess. These skills are incredibly important but sound boring and forgettable. They’re things like reading code, consistency and style, debugging, refactoring, and test-driven development. If I could distill Watch and Code to one skill, it would be the ability to take any codebase and rip it apart. And the most important component of that ability is being able to read code."

As you can see, Gordon always emphasised language neutrality, mastering the fundamentals, and going deep rather than wide. He has a ruthlessly high barrier of entry for learning new skills, which is basically "learn something when you have no other option but to learn it".

His approach served me well for my deep dive into Javascript, my first language. It is still the one I know the best and enjoy using the most, despite having written programs in PHP, Ruby, Golang and C# since then. I have picked up quite a lot about different build pipelines, development environments and general web development as a result of exposure to these other things, so it isn't a waste of time.

But I am starting to go a bit mad. I focus almost exclusively on quite data intensive UI development with Vue.js in my day job, although there is an expectation I will help with porting an app to .NET Core 3 in a few months. .NET is rather huge from what I have seen so far, and I am seriously craving a sense of focus. My intuition says I am happiest on the front end, and that focusing on becoming a skilled Javascript engineer is where I will get the biggest returns in mastery, pay and also LIFE BALANCE/WELLBEING...

Any thoughts, people? I would be interested to hear peoples experiences regarding depth vs breadth when it comes to the real world.

Here we go, the winter is happening #BecauseItsAlreadyComing

The Fcuking Stereotype of MDFK Projects Deadline was not achieve, everybody starts throwing blame words, the management had their heads burned, aaannd... This is nearly 11pm I'm enjoying my chicken Satay and I don't give a fcuking damn with this situation. #MyCodeMyAdventure

lets have a junkie dinner my fellow devRanters! 😂

Welcome to the jungle/dongle life 🙁
I only like OSX, OSX apps and the retina screen.
RIP savings

My AP Computer Science teacher changed my life in 2001. Until then, I wasn’t considering a career in development. He challenged me to write a back propagating multi layer perceptron neural network, and an RPN calculator. Every day made me think about how to solve problems at an algorithmic level. He was brutally honest, and one of the reasons why I’m an team manager now. RIP, your legacy won’t be forgotten.

The moment when you've graduated in computing yet still struggle with grids in CSS 🙃

After two years of being in (metaphorical) jail, I once again was given the a privilege of unlocking and rooting my phone. Damn. Frick Huawei, never coming back to that experience.

I gotta say, rooting... Feels a tad less accessible nowadays than when I last practiced it. All this boot image backup, patch, copy, reflash is crying to be automised, only reason I can think of why that changed and magisk can no longer patch itself into the phone's initrd is that it's somehow locked? Was it a security concern? Or can sideloaded twrp no longer do that?

Oh, and the war... The war never changes, only exploits do - fruck safety net... Good for Google that they now have an *almost* unfoolable solution (almost). The new hardware-based check is annoying af, but luckily, can still be forced to downgrade back to the old basic check that can be fooled... Still, am I the only one who feels Google is kinda weird? On one hand, they support unlocking of their own brand of phones, but then they continuously try to come up with frameworks to make life with a rooted or unlocked phone more annoying...

On the other hand, I do like having my data encrypted in a way that even sideloading twrp doesn't give full access to all my stuff, including password manager cache...

Any recommendations what to install? I do love the basic tools like adaway (rip ads), greenify (yay battery life!), viper4android (More music out of my music!) and quite honestly even lucky patcher for apps where the dev studio practices disgust me and don't make me want to support them...

Not my CS lecturer but my ICT teacher in high school convinced me that it would be a great idea to go study CS at University. It was the best decision of my life as I'm now happily working full time as an Android developer for a startup. Couldn't imagine myself doing any other well paid job and being this happy.

Sadly I never got to tell him where I ended up post graduation but I did get to tell him that I secured myself a good placement year when I was at university when I found out he was sick.

He was so grateful of me getting in touch and I'm glad I managed to get to say thank you to him before he passed away.

Leukemia fucking sucks. RIP.

!dev

Ok, fuck my city. We are fucking freezing here the second day now, no hot water, no heat, it is around 0 degrees outside and THEY FUCKING CAN'T COMMENT ON THE CURRENT SITUATION AND WHAT HAPPEND OR WHEN WE WILL STOP FREEZING? WHAT THE HELL????

It's been just a year and a half, I didn't have Applecare and my Mac now has a logic board fault.

rip life. Webpack is strangling me. You'll turn degen if you came from backend...

Looks like this is my biggest challenge as a dev so far.

All of my favorite mentors pass away too early in life. #RIP Jared Richardson