<rant>
when you're in a iOS programming class and for the 3rd week in a row we aren't coding. I don't give a flying fuck about steve jobs or apple as a company or their philosophy. Im here to code, not for a fucking history lesson.
</rant>

!dev && rant

Went to the café earlier today to buy some cigarettes, because the nearby beauty/drug store is phasing them out due to what according to the cashier I asked is because "we are a beauty store so cigarettes don't align with that philosophy!"

If they really stand for beauty, they wouldn't have employed you, ugly fucking bitch.

So, onwards to the café which I recall has a cigarette vending machine. Closed.

To the next one!

Me: "Um, do you have a cigarette vending machine?"
Bartender: "Nope."

Some motherfucker who was drinking there: "You know, you could stop smoking and start living healthy-"

Me: "you know how difficult it is to stop smoking? ^^"

Me (internally): YOU FILTHY WASTE OF OXYGEN, THIS IS MY BODY, MY LIFE, I CHOOSE WHAT TO DO WITH IT!! Or are you divine oracle of knowledge about health somehow an authoritative source of advice?!

You know what that sounds like? It sounds like those fucking morons on every Windows rant saying "yOU sHoULd rEalY usE LenOx!!". Or the motherfuckers at every family dinner saying "I am vegan, therefore you shouldn't eat meat!!"

Same motherfucker: "Oh it looks like you're sweating too!"

YEAH YOU PIECE OF SHIT, I REALLY DIDN'T NOTICE THAT YET!!! IT'S 32 FUCKING DEGREES IN MY APARTMENT, MY ASSCRACK IS WELDED TOGETHER, YET YOU THINK THAT I DIDN'T NOTICE YET THAT I'M SWEATING?!!!

If only I could shoot them in their fucking heads and expose them for the brainless pieces of shit they are!!!

Development world is always changing and evolving... It changes before you know it...

So, having the ability to quickly adapt and learn is a must for any Developer... And, this is the one thing that I am sure that everyone knows about or heard about..

But, my advice is quite simple:

"Don't rush into participating in a race, just because everyone else is doing so.

The trick is not to move quickly.. But, to move one step at a time, at the pace in which you are at your most comfortable...

It might seem counterintuitive and a contradiction to what I have said earlier.. But, I hope that by the end of this rant, you will be able to understand my perspective..

This advice is especially useful for people still finding and searching for their place in our world..

Charles Darwin, very wisely understood the philosophy behind 'Survival of the Fittest'..

By 'fittest', he didn't refer to the ones considered to be the strongest or having the most intelligence, but the ones that had mastered the ability to adapt to changing circumstances..

Adaptability is important, but not at the cost of understanding and learning about the fundamental pillars on which this world stands..

Don't rush because when you run, your visions starts to become more narrow.. In your pursuit to reach your goal, you lose the ability to look at the macro details surrounding your goal..

Learning new technology is important, but that doesn't mean that you don't learn about various approaches or how to design a more logical or efficient solution...

Refactoring the code, developing good Testing procedures, learning to interact with your fellow developers are as crucial as learning about the changing trends...

Even, in this ever-changing world, understand that some things will always remain the same, like the adrenaline that course through your veins when you finally solve a long-standing problem...

Curiosity, Discovery and Exploration are the key pillars and hence, when we rush in, we might stop exploring and lose curiosity to discover new and exciting ways to reach our goal..

Or, we might also end up losing the drive that grips us and motivates to continue moving forward inspite of the challenges standing between us and our destination..

And, believe me, once you lose this quality, you might still succeed but the contentment and the satisfaction that you feel will be lost..

And, then, you will remain a developer only through your designation... And, that in my personal opinion, the worst punishment.

Can someone explain the philosophy of the "not for me" downvote?

There are many things that are "not for me" in life, but, presumably, this action executes a global downvote on the post/comment---which is pretty much an expression of "not for anyone".

If this action were to train a recommendation engine---so I get recommendations that like-minded people see---then great. But why should that result in a public downvote?

I don't go up to people in the bar and say "Drinking Guinness? Not for me, mate." As an adult, I understand that my preferences are not universal.

Personally, I can't square the idea of "not for me" with its consequence of a public downvote.

I'm sure this must have been covered before...but all rants, as physiological and emotional activities, are unique. Your rant can never be mine.

I finally came to that conclusion:

Customers doesn’t really know what they are buying.
IT company doesn’t really know what they are selling.

!rant
Will this code be compiled ?

#include<iostream>
using namespace std;
int main(){
int 🥩=1;
int 🧀=1;
int 🥬=1;
int 🍞=1;
int 🍅=1;
int 🥪=🍞+🥬+🍅+🧀+🥩;
cout<<🥪;

return 0;
}

!rant
I’ve just looked into Rust a bit deeper and was absolutely stunned by how many things it has in common with Swift. The Syntax, the features, the concepts, the "philosophy".

Previously I thought that Kotlin is what comes closest to Swift.

Anyway, Rust seems like a beautiful language and it’s no wonder that it is one of the most loved languages out there!

The compile time index out of bounds errors blew my mind!

So, you all may remember my rant about my visual impairment. This dude applied the UNIX philosophy to glasses: They do one thing, and one thing well. He actually calls them "task-specific glasses" but come on now, that's the OG UNIX concept!

No, I will not have to have surgery - supposedly. The glasses he builds are ~$25,000. He said that when we go over spring break, he'll determine if we can go from 98% to 100% positive. If this can be pulled off, my life could be forever changed, for the better, hopefully...

If you're subscribed to me only because of my jokes, feel free to ignore this rant. You won't miss anything.

If not, bear with me.

I was wrong about almost everything I can remember. Preaching so-called “conceptual thinking”, I invented a fantasy world of random anecdotes, which turned into a completely false worldview that shaped my reality. I bashed magical thinking, yet succumbed to it. What I believed to be true was just as magical, wrapped into what sounded like science. In the Dunning-Krueger scheme, I was right there on Peak Stupid.

Random hear-say, stupid concepts I invented, random “knowledge” I picked from YouTube videos, all that was rotting inside my head, one anecdote contradicting another. Ultimately, I think this was the reason of my constant anxiety and pointless, never-ending thought process in background.

If you learned anything factual from me and didn't fact-check it, please forget that immediately. The list includes but is not limited to everything on brain structure, everything on philosophy, almost everything on engineering and architecture, almost everything on systems theory and programming meta stuff (declarative, imperative, etc.)

I admit bashing unit tests. The only reason was me disliking writing them in uni. I wrote like three test cases, disliked it, and the rest was history. Everything else was a rationalization on top. If I was right about something, I was just lucky.

I'm not a CSS prodigy. I know stuff that earns me money and impresses my colleagues, but my knowledge is just one step above basics, in one thousand steps ladder.

!rant

Going through my graduate program I have come to realize that there is more to A.I than just machine learning algorithms. As if ML was not complicated enough, we add more to it such as KRR and other topics that border on the areas of Cognitive Science, Boolean Algebra, Logic and even Philosophy and you know what? I dig it. I dig it because finding some of the information in the course that I am getting is damn near impossible to see in other items. Such is the case as a method for fucking signature unit propagation which afuckingparently was developed by one of my instructors(not complaining, just really fucking impressed)

The thing is, most of these items would normally have a parallel in software development that we use on our day to day basis, all of us, no matter if you do web, systems development, database development whatever, the general concepts are the same: you represent real world concepts, such as that of logic and knowledge in programatic/mathematical representations.

I am really amazed at the content of these items, I really am. I just wish for some clarification on ambiguity, seems like most things are left better if it where explained in a programmer's point of view. Most of the items that I have seen could have easily been summarized in a programmers logic if only they would have preferred to take the time to do it, and I get that there needs to be mathematical intuition formulated before anything, it is better sometimes to learn concepts from an outside point of view, a mathematical point of view, but shit is just strange sometimes.

If anyone can do a 12-week bootcamp to become a ‘developer’, where are the 12-week bootcamps to become a lawyer or doctor? 🤔

That moment I wonder why I haven't wrote any rant for a long time and suddenly realized that it's because I've been coding only about a couple hours a week for the last months.

Basically, I finished all my computer related class and all that is left to finish (before I can get my diploma) are basic courses like philosophy and literature (which at least are interesting).

Now pretty much every day I wake up and I crave to code but I just don't have time to 😐

Step 1:
Promise customer something non-existent
Step 2:
Complain big time that engineering is not co-operating in getting the order out in time. (without which you won't get your end of year sales performance bonus)
Step 3:
Comment about the product being sub standard. Rant about how engineering "great" products must be the philosophy. Blah blah blah...
Offer to provide your fucking support to make the product better despite not being responsible for it.Be the greater person.
Step 4:
Deliver the product. Pocket your bonus. Make jokes about how bad the product is and how you won't sell it again to protect the company brand reputation.
Step 5:
Rinse and repeat.

Fucking assholes.

!rant

What did you do in life before you got into computers/development?

I was mostly a nolife gamer who could play video games 12 hours a day. I was also obsessed with History.

Loved also Philosophy, Politics, Theology, Geography, Biology, Arts and Literature.

!rant Week 82

Eastern philosophy has made me better at programming. I'm not much of a metaphysics guy, but abstract space breeds creativity. I find that programming and zen are alike, wholeness enveloped by nothingness. A new programming language is being an infant to a foreign universe, without any means to make sense of things. Only through your own references can you make sense of this new stimuli. That nascent feeling, being a baby, is an amazing thing. Programming is probably the most humbling task I've ever endured. We all know the feelings of imposter syndrome, and yet they seem distant when a new solution is just burgeoning. Rehabilitation refers to social programs as programming. Criminals spend all day, "programming" in most institutions. Programming as a word becomes a meditation for change. So life and programming then, are forever in twined. And my experience of being humbled as a programmer has helped me in life. And my experiences being humbled by life, have made me a better programmer.

Did you read Sophie’s World? Feels like it’s the introduction to Steven skeina’s Algorithms.

Just why is the question and answer.

!rant
I'm not sure if it's good or bad, but lately I've lost that "love" for code, not coding itself, but the code in projects.

Because most of the time the projects are inherited, there is never enough time, It's always a priority. And let's be honest, most of the time programmers don't like others code. (Is it God Complex?).

What I do notice with this "new" philosophy it is that I do not stress when I do not like some development, I ask the "bosses" if there is time to change it or if we continue with how it is. I learn that it should be done better and I continue my life

#Suphle Rant 9: verbatim exception scare

In multiple rants, I've bitched about laravel stealing suphle features. By some very weird coincidence, it appears I've been given a taste of my own medicine. Let me explain:

We're having a chat this morning on a laravel group chat when someone says he uses their notification component a great deal. Curious, I ask him what he uses it for since I only used it sparingly during my laravel days. To pry an answer out of him, I ask whether he uses them for sending app error alerts to a slack channel, and he responds with an eerily familiar term. I quickly look it up and the results on the docs are chilling: errors can be sent to bugsnag (which suphle has an integration for), sentry and Co. Errors can either be broadcast or disabled. Specific kinds of errors can be caught. My heart sunk. My brother called for something while I was going through it and I was struggling to pull myself together

Their exception component is almost identical to mine and I'm only just realising. It's shameful that I'm just learning about functionality present since 5.8. I thought my creation was novel. BUT! The good news is, the implementation differs

Too many errors went unnoticed during my time there because error broadcasting is optional. Since none of my colleagues read that part of the documentation, we were firefighting by pulling and wrangling production error logs. This informed their abolishment in suphle altogether

A relatively minor difference is in the APIs –their philosophy makes significant use of global functions, violating SRP, etc.

But the most important difference, that still cheers me up, is that they only catch known errors. Suphle has a construct for isolating calls to a decorated service. Any unforeseen error to occur during its execution will do a series of things before control is returned to the caller