I am a passionate software engineer.
That means that I strive towards excellence, in all aspects of software engineering. It also means that I cannot abide impediments towards those goals.

In practicality, it means that I will try as hard as I can to make the best possible solution for any specific problem. And that if I can make an improvement to the codebase that will make it easier for the next developer to work with it, I will absolutely make it.

I used to believe that my immediate manager had an understanding of my philosophy and why it was important not just to me personally, but to how the company had to move forwards in general also.

I just had a conversation today that completely flipped my perception of him and his role in the company.

I need a new job. Again. Because business people do not understand software, even if their entire business is based on software.

Electric cars are not better for the environment. All petrol cars combined are only responsible for 7.9% of CO2 emissions. If your electric car is charged from a grid that is powered by a coal-burning power station, it contributes nothing to dealing with climate change. It only provides you with the false sense of security, and you can look cool telling your friends that “you know, I drive a Tesla, I’m environmentally conscious, your gas car is bad”.

Electric cars are lame. When I’m out of fuel, I can refuel fully in minutes. With electric car, I’ll have to wait at least five hours. Let’s be realistic, superchargers aren’t common, and will never be.

Gasoline is 46.4 MJ/kg, or 34.2 MJ/l. Li-Ion is 0.36–0.875. Let’s be generous and say it’s 0.9. To match 1 kg of petrol, I would need 51 kilos of batteries.

Average gas tank is 18 gallons, or 68 litres. To match that, my battery must have a weight of 2.5 metric tonnes. Bear in mind, empty battery and full battery has the same weight. Also, bear in mind, batteries perform worse in the winter.

As per energy density and practicality, things don’t get much better than petrol. Liquid hydrogen has higher energy density, but to store it, gas tank has to have very, very thick walls, to withstand the pressure. And, hydrogen is a bitch. It’s extremely dangerous. You can’t smell it until it’s too late. Hydrogen-air mixture will explode if you look at it the wrong way.

All that “electric cars good for climate” hype is merely Elon maintaining his stock bubble.

"Practicality is the serial killer of dreams." - Rasha Hamdan

I don't understand privacy advocators.

Am I the only one who wouldn't give up practicality in exchange for "potentially more secure"?

I don't understand so much what the deal is with people who avoid Facebook, or don't trust Google or Microsoft, just in the basis of "privacy" or "security".

Websites tracking you to serve ads? Well, it's pointless because I very rarely buy something from the internet or let myself be influenced, ads are waste of time, just use an adblocker.

I can pretty much upload my whole life or documents on Google drive, even if I made it public no one would really care or read it all. It's like that GitHub project you uploaded but never documented, so no one cares. I usually use alternative software not because of "privacy" but because it has features other software doesn't have.

In reality you realize people aren't that interested in your life more than their own life.

I have met a game developer today who genuinely browse the internet using MS Edge by choice.
His reason: sine I was little I loved Microsoft, I accept the fact that some websites don't show properly on Microsoft's browser, by using their browser I keep reminding myself that loyalty to what I love is more important than practicality.

My response to him: bbut... As long as you're happy!

As a web developer I feel that myself and other web devs have the responsibility to kick Microsoft in the butt to make their browser good enough for loyal people like that guy!

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

A continuation of the worst idiot that I worked for, in possibly the worst project of the world. ( The guy who said youtube watching doesn't cost data, downloading the videos offline does)

Guy sends me a template for a patent application.. I ask him why, and he's all secretive until he takes me into a meeting with the patent officers of the organization to reveal his grand plans.

Here goes his idea. He wanted to file a patent for a sonar made for large vehicles in India. His idea was that people in India are used to overtake busses while they turn and they are overrun by the large vehicles. True to some extent but a completely overkill solution for a minor issue that could be solved by educating the masses. I try to explain this to him, and he's pissed off. Starts throwing random, made up stats at me saying 2000 people die everyday on every street. I'm like WHAT??? I look at the patent officer, and he gives me that "don't look at me dude, I'm just here for any questions about the patent process" look. He's busy doodling in his notebook while I try everything possible to invalidate the stupid idea my client has barfed all over the meeting room and the attendants. I even bring out the technical challenges leaving aside the practicality of the nonsense. I asked him how to distinguish between a pedestrian, a parked vehicle, a dog, a cow.. To which he responds with an on the spot thoughtless answer. Heat signatures!! In 5 minutes we went from sonar to heat maps in a tropical country such as India.. He now wants a hybrid solution.

He was about to start yelling when I caved in on the condition that I want nothing to do with the idea after I finish the patent application.. Made up some document and sent it to the asshole, only to never hear about it again.. Thank god for that.. R&D my ass..

It needs to be outright illegal for laptops to have fewer than four USB ports.

If the purpose of law is to improve the quality of life, why not outlaw the time-consuming annoyance of laptops with few USB ports?

The purpose of laptops is portable computing. Depending on a USB hub makes it less portable.

If it was legally mandatory for laptops to have at least four USB ports, there would be no more competitive disadvantage for laptop vendors sacrificing unimportant slimness for important practicality.

And to the very few people who consider slim design more important than USB ports and who are going to whine online about the extra 3 millimetres of thickness: Sorry, life is unfair. Your preferences don't matter. Practicality is the purpose of computers. You are the reason laptops are ruined for the rest of us. Get lost.

Haven’t learned in a classroom setting, but am learning from multiple online sources and it would be way more helpful to teach thought process and practicality than syntax nuances.

As i was shitting on toilet I realized something very important. This could be THE answer.

The question: what is the formula for achieving success? I realized this must be THE ultimate answer:

Money + connections + luck >= success

Why?

MONEY:
You must have money to make more money.

CONNECTIONS:
Some average joe can tell his friend Cockty to phone call his friend Dickson who's a good friend with Cumston to message his millionaire friend Asslicker who is gonna help the average joe succeed.

LUCK:
No matter what you do or how hard you work, how many achievements you have or degrees, you can spend 10 million dollars on a project -- and still fail because you're not lucky.

Let's calculate this probability:

have = 1
missing = -1
money = 0
connections = 0
luck = 0
success = 1

money + connections + luck >= success

Case 1 (have everything):
have + have + have >= success
1 + 1 + 1 >= 1
3 >= 1 ✅

Case 2 (no money):
missing + have + have >= success
-1 + 1 + 1 >= 1
1 >= 1 ✅

Case 3 (no connections):
have + missing + have >= success
1 - 1 + 1 >= 1
1 >= 1 ✅

Case 4 (no luck):
have + have + missing >= success
1 + 1 - 1 >= 1
1 >= 1 ✅

Case 5 (no money, no connections):
missing + missing + have >= success
-1 - 1 + 1 >= 1
-1 >= 1 ❌

Case 6 (no money, no luck):
missing + have + missing >= success
-1 + 1 - 1 >= 1
-1 >= 1 ❌

Case 7 (no connections, no luck):
have + missing + missing >= success
1 - 1 - 1 >= 1
-1 >= 1 ❌

Case 8 (no money, no connections, no luck):
missing + missing + missing >= success
-1 - 1 - 1 >= 1
-3 >= 1 ❌

We have: 4 possible outcomes that we want, k=4

Out of total: 8 possible combinations, n=8

Probability of achieving success using this formula is: P(A) = k/n = 4/8= 0.5 * 100% = 50% chance of being successful in this shit life

This is correct in theory. HOWEVER:
Case 1: someone having
- a lot of money
- a lot of connections
- a lot of luck
In practicality is damn near IMPOSSIBLE

Maybe 1 in 100 million people are born like this. That's 100,000,000 people / 8,000,000,000 people = 0.0125 * 100% = 1.25% of people are this blessed and gifted in life. This might be even less so we can ignore this probability as a possible outcome and average it out to realistic average joe daily life.

Therefore giving us a total of 7 combinations, 3 possibilities to succeed in this shit life

So: k/n = 3/7 = 0.4285 * 100% = 42.85% chance to be successful in this shit life

Mathematically proven how life is pure trash

Funny enough we can round it to 42%. And 42 is the answer to life, universe and everything in existence

I think promoting 'a quick lookup on Google' every single time you need to add something useful into your codebase is a bad mentality. It's the same problem with populating your code with Stackoverflow snippets.

I think this is not a good approach because your code will eventually rot and you won't have full control over your codebase in that you didn't write those parts and you don't fully know what's going on underneath. Then, you will forget about that code. A new feature request will come up and oh no, you will be wrestling with your old code because you just quickly inserted it in there, not fully knowing it under the hood. Hours will be lost on debugging.

I advocate much more the approach of really knowing the language and the solutions you're using, instead of just constantly hacking it with the excuse of "Oh, there's no time to learn everything", "You don't need to know the details" and "This is the real world".

No, this is not a good attitude. With the former approach, you will be much more able to safeguard your code and improve on it, rather than wrestling for hours with it. I think it's important to have as much ownership of your code as possible and depend as little on outside libraries as possible.

Fundamentals first, practicality second.

For those of us OCD Sheldon Cooper types out there, programming can get very annoying.

For example, I want to do everything as efficient as possible but sometimes situations require "live with it" or "quick and dirty" solutions, which grinds my teeth because I'm not applying perfection in everything and a laid back attitude is against my personality, much like Sheldon. It's the same annoyance as when Penny knocks twice but not thrice at the door.

This sure is easier for brogrammers.

Is it just me that would prefer to work with Senior Engineers rather than mid level engineers?

Some mid level engineers are just pain in the ass. This one guy insist on getting perfection in all of the requirements. The problem is that if you work with software/lib for so long, you realize that most if not all software are buggy or have limitations.You can't expect everything to be perfect. Sometimes something just works/don't work and nobody knows why. Need lots of shortcuts/hacks just to make it work. I would say that 80% completion is good enough, especially since we're running out of time and manpower.

I noticed that Senior Engineers tend to be less strict. If it works then it's good enough, if we found some bugs later then we'll fix it. I like this practicality so we can tackle more important issues at hand.

I hope that I don't have to work in the same project with this guy again.

I've gotten started with web dev in the past and learned HTML and CSS and started learning JS but I never could understand what I could use for a code editor to practice and pretty much forgot all of that stuff. Now I'm trying to learn Python, but what's pissing me off is paying for a phone app that doesn't teach you to write code in these lessons, rather interactive multiple choice questions and "put this in the right order". sequences. This is not learning for me, this is informing. Which is info I don't retain. And If i'm paying for it why is there so little to these lessons? Barely covering anything. I've done every lesson Mimo had for python but it didn't really explain the practicality of what it was teaching me and they skipped a lot of shit. Changing the pace of the lesson from Print this and that and heavily explain the most basic stuff 3x over to only explaining the more advanced stuff one fucking time.

I would really like learning python while being walked through a project as a lesson. Teach the terminology, structure, application, process, rinse and repeat, and outcome all in one. With a project target to look forward to. I need a goal to keep my interest.

So far all I know about python is its a programming language used to create Youtube. And I'm trying to learn it because I keep reading that its the recommended starting line. But I need to be able to visualize what this code can be used for. Explanations in terminology I haven't been taught yet just frustrates me. And I read everyone's posts and see many people mention being frustrated, but I haven't even started coding yet. Feel free to comment and redirect me to page that can help. Links are appreciated. Nay, encouraged!

So, I just (few hours ago)made a new variable that's either brilliant or innately flawed... not sure yet. It's an oddly unique var...

__bs__

So far I only made it in python and windows env (i script like the methodology of css).

I bet you're wondering how I've defined __bs__ and the practicality of it.
__bs__ is derived from a calculated level of bullshit that annoys me to tolerate, maintain, etc. as well as things that tend to throw nonsensical errors, py crap like changing my strings to ints at seemingly random times/events/cosmic alignments/etc or other things that have a history of pulling some bs, for known or unknown reasons.

How/why did this come about now?

Well I was updating some symlinks and scripts(ps1 and bat) cuz my hdd is so close to death I'm wondering if hdd ghosts exist as it's somehow still working (even ostream could tell it should be dead, by the sound alone).

A nonsense bug with powershell allowing itself to start/run custom ps1scripts with the originating command coming from a specific batch script, which worked fine before and nothing directly connected to it has changed.

I got annoyed so took an ironic break from it to work on python crap. Python has an innately high level of bs so i did need to add some extra calculations when defining if a py script or function is actually __bs__ or just py.

The current flavour of py bs was the datetime* module... making all of my scripts using datetime have matching import statements to avoid more bs.

I've kept a log of general bs per project/use case. It's more like a warning list... like when ive spent hours debugging something by it's traceback, meticulous... to eventually find out it had absolutely nothing to do with the exception listed. Also logged aliases i created, things that break or go boom if used in certain ways, packages that ive edited, etc.

The issue with my previous logging is that it's a log... id need to read it before doing anything, no matter how quick/simple it should be, or im bound to get annoyed with... bs.

So far i have it set to alert if __bs__ is above a certain int when i open something to edit. I can also check __bs__ fot what's causing the bs. I plan to turn it into a warning and recording system for how much bs i deal with and have historical data of personal performance vs bs tolerance. There's a few other applications i think ill want to use it for, assume it's not bs itself.

*in case you prefer sanity and haven't dealt with py and datetime enough, here's the jist:
If you were to search any major forum like StackOverflow for datetime use in py, youd find things like datetime.datetime.now() and datetime.now() both used, to get the same returned value. You'll also find tons of posts for help and trying to report 'bugs', way more than average. This is because the datetime package has a name conflict... with itself. It may have been a bug several years ago, but it beeb explicitly defined as intentional since.