After interviewing 3 candidates for software today, I have officially decided its time to seriously pursue creating a YouTube channel with a complete set of series to learn programming MY WAY... not the short cut way... this will go all the way to beginning and start the person up with a solid foundation to build on... I’m going to pour my knowledge into these series.
The education system has failed too many in the real world... to many people I have interviewed they think they know have a degree but are clueless.. this is unacceptable and a waste... AND way too often I see online “learn programming in 30 days or learn programming in a day”... fuck off it’s all lies .. all wrong.. wrong methods wrong philosophy and I’m done with it...
I’m set on doing it this time, I’ve put it off too long, and longer I put it off the more I see shitty interviews! Time to fix it

<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>

Programming is one way communication from your past self to your future self.

My dev role model is my senior who taught me JavaScript when I was a noob. He was so cool. One of the few real programmers who enjoy their work in a clusterfuck world of idiots who pretend for money.

His philosophy sticks with me even today. I was new to the industry and the long hours of low pay intern work were getting to me. But he kept reminding me that programming still has this cool, engineering side where you blitz stuff out on a keyboard and build awesome shit.

I owe him my career because without him I'd still be one of the other stooges who bitch about the job and avoid studying. But since working with him, I never speak bad about my profession. Programming is a beautiful profession, even if the people I work with are sometimes dumbfuck dicks. And he taught me that distinction.

How I met python
[long read but worth]

There's nothing wrong with falling in love with a programming language for her looks. I mean, let's face it - Python does have a rockin' body of modules, and a damn good set of utilities and interpreters on various platforms. Her whitespace-sensitive syntax is easy on the eyes, and it's a beautiful sight to wake up to in the morning after a long night of debugging. The way she sways those releases on a consistent cycle - she knows how to treat you right, you know?

But let's face it - a lot of other languages see the attention she's getting, and they get jealous. Really jealous. They try and make her feel bad by pointing out the GIL, and they try and convince her that she's not "good enough" for parallel programming or enterprise-level applications. They say that her lack of static typing gives her programmers headaches, and that as an interpreted language, she's not fast enough for performance-critical applications.

She hears what those other, older languages like Java and C++ say, and she thinks she's not stable or mature enough. She hears what those shallow, beauty-obsessed languages like Ruby say, and she thinks she's not pretty enough. But she's trying really hard, you know? She hits the gym every day, trying to come up with new and better ways of JIT'ing and optimizing. She's experimenting with new platforms and compilation techniques all the time. She wants you to love her more, because she cares.

But then you hear about how bad she feels, and how hard she's trying, and you just look into her eyes, sighing. You take Python out for a walk - holding her hand - and tell her that she's the most beautiful language in the world, but that's not the only reason you love her.

You tell her she was raised right - Guido gave her core functionality and a deep philosophy she's never forgotten. You tell her you appreciate her consistent releases and her detailed and descriptive documentation. You tell her that she has a great set of friends who are supportive and understanding - friends like Google, Quora, and Facebook. And finally, with tears in your eyes, you tell her that with her broad community support, ease of development, and well-supported frameworks, you know she's a language you want to be with for a long, long time.

After saying all this, you look around and notice that the two of you are alone. Letting go of Python's hand, you start to get down on one knee. Her eyes get wide as you try and say the words - but she just puts her finger on your lips and whispers, "Yes".

The moon is bright. You know things are going to be okay now.

From NAND to Tetris..

This book is IMO the best book for those who want to venture to the lower level programming.

This books retrains you’re thinking, teaches you from the bottom up! Not the typical top down approach.

You begin with the idea of Boolean algebra. And the move on to logic gates.. from there you build in VHDL everything you will use later.

Essentially building your own “virtual machine”.. you design the instruction set. Of which you will then write assembly using the instruction set to control the gate you built in VDHL.

THEN you will continue up the abstraction layer and will learn how a compiler works, and then begin written c code that is then compiled down to your assembly of your instructions set to be linked and ran on your virtual machine you built.

All the compiler and other tools are available on the books website. The book is not a book where you copy and paste, run and done.... you kinda have to take the concepts and apply them with this book.

Then once you master this book, take it the extra step and learn more about compilers and write your own compiler with the dragon book or something.

Fantastic book, great philosophy on teaching software.. ground up rather than top down. Love it! It’s Unique book.

I really like this book on the basis of the philosophy overall, no this doesn’t solve all problems but it’s a good baseline of “guidelines/rules” to program by. Good metrics or goals to architect and design software projects high and low level projects.

Fight Software Rot
Avoid duplicate code
Write Flexible, dynamic, adaptable code
Not cargo cult programming and programming by coincidence.
Make robust code, contracts/asserts/exceptions
Test, Test, and TEST again and Continue testing.. this is a big one.. not so much meaning TDD.. but just testing in general never stop trying to break your software.. FIND the bugs.. you should want to find your bugs. Even after releasing code the field continue testing.

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.

the more i learn about web dev, the more i realise the reason for its mess up . There are 2 major problems in it : the people who create various important concepts and tools for web dev were 1) working on it without any collaboration and agreements on the philosophy and 2) were too stubborn on their ideology i guess.

There is no limitation to anything's functionalities, and the limits that are "defined" are badshit crazy. for eg:

====================================
HTML creator : "I am gonna make a language that would provide a skeleton to web page. it will just have the text and basic markers to let the scripting and styling engines/languages know which text is supposed to be rendered and how.
It won't provide any click or loading functionality.

someone: "So i guess opening a page or loading an image would be handled by JS or other programming language? also, bold , italic or division would be added via CSS?"

HTMLguy : Nah, my html engine would ALSO do that.

someone : what , why? won't that just be stupid and against your philosophy?
HTMLguy : WHAT? am too awesome, can't hear you
w3c , 50 yrs later : sorry can't change this, gotta support the 50 yrs of web dev and billion sites

=================================

CSS guy: I am gonna make the world's best beautifying stylesheet language to provide colors, styling, fonts and backgrounds to a page. every loadings and clicks would be handled somewhere else

Some1: cool, then clicks, hover and running of animation would be handled by JS only

CSSguy :Umm, i guess i could handle those.

Some1 wha-?

CSSguy : Thankyou Thankyou Thankyou for the nobel price!

====================================

JS guy : I am gonna make a god web programming language! It can do everything: add/remove html tags, add styling, control animations, control browser, handle clicks , perform operations, everything!

some1: cool! you must be making very large programming language with lots of modules.

JS guy: No! i am gonna keep it small. no built in classes and file imports! just use the functions directly. if someone wants the additional lib functionality, install them on your server

some1 : innovative! what's typeof NaN ?

JSguy :shut up.

For all things, for all men, that a man compliments a thing does not imply that this man at least attempts to understand this thing. However, for all men, that a man criticises a thing implies that this man at least attempts to understand this thing.

For all computer programs, that a computer program is terrible implies that scrapping the current implementation of this computer program and beginning anew may be the best method of fixing this computer program.

With few exceptions, for all programming languages $l$, given sufficient effort, $l$ source code can be human-readable.

The UNIX philosophy never became outdated.

For all computer programs $p$, $p$ should be written sufficiently well that the author of $p$ can be prideful of $p$.

For all computer programs $p$, a specification for $p$ should be written before $p$ is created.

For all good computer programs, a good computer program can run on terrible hardware.

Every clock cycle is valuable.

the one that exists (c#) seems underused compared to where it could (or even should) be used. and the place that uses it the most (enterprise) butchers and mangles its use, just as enterprise tends to do with everything.

the one that i'm designing... the fact that it doesn't exist yet, and that even as i'm zeroing in on syntax and philosophy that i'm very much starting to be proud of, i still don't have a proper idea of how to implement even the most basic parser/interpreter for it, not because it's in any way difficult or unusual, but just because... i've never done that before, so i get into weird circular thought paths that produce weird nonsensical code...

... on top of that, i still only have a very, very fuzzy idea of how will it (sometime in extremely distant future) actually implement the most interesting and core feature - event-based continuous (partial) re-parsing of the source code and the fact that traversing the tokens at the leaf level of the syntax tree should result in valid machine code (or at least assembly) that is the "compiled" program.

i *know* it's possible, i just don't yet know enough to have a contrete idea how exactly to achieve it.

but imagine - a programming language where interactive programming is basically the default way of working, and basically the same as normal programming in it, except the act of parsing is also the (in-memory) compilation at the same time, so it's running directly on the hardware instead of via interpretrer/vm/any of that overhead crap.

also then kinda open-source by definition.

and then to "only" write an OS in that, and voilá! a smalltalk-like environment with non-exotic, c-family syntax and actual native performance!

ahhh... <3

* a man can dream *

!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.

I don't know if anyone else feels this way, but for me JavaScript kind of feels like trying to understand people. The more I learn, the more history I understand, the deeper the foundations of my knowledge become, only leaves me with more questions. Now, this is true of programming at large but the divergent nature of JavaScript just blows my mind. I'm sure that's not unique.

Like, I was learning about accessor objects today, sure they're similar to other languages, but the reason it fucks me up so bad I guess is the why? Just like the motivations of people. I understand it to be dynamix creation, but still. And, for a long time what's really drawn me to programming is how humbling it actually can be. But I just feel like some student of philosophy where meaning starts to circle back onto itself.

I got it admit, as much as I love programming, it's insanely frustrating. It feels like one step forward is always two steps backwards, and so there is no root place to understand meaning. Maybe I'm just rambling and this isn't a unique feeling at all it's just so frustrating trying to master something, feel like it's at your fingertips and it moves away. It's almost like Heisenberg or something, when I quantify and measure my skill, it invariably makes the measurement wrong.

Thread topic: religion, philosophy, matrix

Summary: skip if you don't like these topics, stay if you want to find out why the conclusion has relevance to programming

.
.
.

Ok.

Let me get this straight:

There are 4 founders of the BAYC NFTs.

1 has a fasist/nazi pseudo name
1 has a racist pseudo name
1 has a satanic pseudo name
1 has a pedophile pseudo name

Their logo is a copy of Nazi Waffen Totenkopf emblem, which was the German division force of the Nazi concentration camps

And they became billionaires.

Ok

.
.
.

Sam bankman the founder of FTX crypto shit robbed people for 32 BILLION dollars. And hes not in jail because he donated most of that money to democratic political party, leaving himself 1 billion dollars as allowance. Now that he bought political power, politicians protect him. So he's having fun in the bahamas and penthauses, having generational wealth and enriching his fraud parents.

Ok

.
.
.

Balenciaga. They posted photos of female children holding fluffy toys with BDSM sexual bondage. Books on the table, with excerpt of Michael Borremans, who draws "art" of naked children covered in blood and being sacrificed in rituals. Then a book of "The Cremaster Cycle", which is a demented image that symbolizes "the murder and resurrection of Abiff". Hiram Abiff was the central character during Masonic initiation rituals as the culmination of a three-part process. Etc

Balenciaga is a multi million dollar "brand".

Ok.

.
.
.

What i learned through all my years of existing on this planet is, being good and doing good, does not pay off. I still live in the matrix. I am still a slave. I am still playing the game of earn to survive. Even while doing software engineering. And I don't know 1 single wealthy person who has obtained all that wealth by doing something good.

This has further lead me to realization: God doesn't help you get rich or wealthy. God doesn't give a fuck if you're rich or poor. He aint gonna help you. But do you know who will? That's right - evil forces will help you get wealthy. Funny how that works?

Because I am christian and believe in God, pray to God and did good all my life - I haven't received anything good in return, my life has not improved, in fact it has devolved and became worse.

Therefore, I came to a conclusion: I will switch teams. I'll let the evil demonic forces take over and guide me to wealth. I'm ready to scam, defraud, develop ponzis and step on corpses and people to get out of the matrix. Perhaps this is how and why good people turn into villains?

Now you understand.

I dont ask to be on the top. I just want to Not play the Matrix game. Which is the game where you have to earn to survive. I want to get into any store and buy whatever i want, without worrying how much does it cost or asking for a discount. People dumber than me do it. But i cant? That means there has to be a loophole in the matrix. An escape plan is possible. I tried escaping since 2018 and failed. For 4, almost 5 years. Because i was trying to escape through good forces. I'll now try to escape using demonic forces and perhaps I'll end up like BAYC founders, FTX founder, Balenciaga brand and many others similar to them. Ending up even half of their success or a fraction - I'll be more than happy. I am not happy living in poverty. Im getting sick of it. I'm getting sick to be underpaid $600/month for doing a job as hard as software engineering, even with a CS degree. Life is not meant to be slaved away till 65+ years old. I can't even afford to buy a car with this slave salary.

So forgive me God. Im just tired of life. Im tired of being a slave. Im tired of watching my parents become older, weaker and still working. I'll shut down all of my morals and I am ready to rob people in Web3 using all of my programming knowledge that has been undervalued.

"A little boy asked God for a new bike for his birthday, but he knows God doesn't work that way. So he stole a bike and prayed to God for forgiveness"

Sometimes I just code some ugly crap that does the job and create a To Do to revisit it later and try to make it elegant.
When I revisit the code I always can't believe that I thought it was bad.

Seems like my past Me is a better programmer than present Me. Ouch.

Getters and setters vs property accessors?

The instructor of my Android development class is manually and purposefully using setters and getters when the Kotlin language and Android Studio is strongly pushing for this property accessor way of handling private data fields. He says that it goes against the philosophy of hiding the data and keeping data fields private.

I’m all for property accessors, but I’m struggling to come up with a response for what he says. Modern programming languages like Kotlin and Swift have been strongly encouraging the use of property accessors.

Yo, DevRat! Python is basically the rockstar of programming languages. Here's why it's so dope:

1. **Readability Rules**: Python's code is like super neat handwriting; you don't need a decoder ring. Forget those curly braces and semicolons – Python uses indents to keep things tidy.

2. **Zen Vibes**: Python has its own philosophy called "The Zen of Python." It's like Python's personal horoscope, telling you to keep it simple and readable. Can't argue with cosmic coding wisdom, right?

3. **Tools Galore**: Python's got this massive toolbox with tools for everything – web scraping, AI, web development, you name it. It's like a programming Swiss Army knife.

4. **Party with the Community**: Python peeps are like the coolest party crew. Stuck on a problem? Hit up Stack Overflow. Wanna hang out? GitHub's where it's at. PyCon? It's like the Woodstock of coding, man!

5. **All-in-One Language**: Python isn't a one-trick pony. You can code websites, automate stuff, do data science, make games, and even boss around robots. Talk about versatility!

6. **Learn It in Your Sleep**: Python's like that subject in school that's just a breeze. It's beginner-friendly, but it also scales up for the big stuff.

So, DevRat, Python's the way to go – it's like the coolest buddy in the coding world. Time to rock and code! 🚀🐍💻

A philosophical question about maintenance/updating.

There is no need to repeat the reasons we need to update our dependencies and our code. We know them/ especially regarding the security issues.
The real question is , "is that indicates a failure of automation"?

When i started thinking about code, and when also was a kid and saw all these sci fi universes with robots etc, the obvious thing was that you build an automation to do the job without having to work with it anymore. There is no meaning on automate something that need constant work above it.

When you have a car, you usually do not upgrade it all the time, you do some things of maintance (oil, tires) but it keeps your work on it in a logical amount.
A better example is the abacus, a calculating device which you know it works as it works.

A promise of functional programming is that because you are based on algebraic principles you do not have to worry so much about your code, you know it will doing the logical thing it supposed to do.
Unix philosophy made software that has been "updated" so little compared to all these modern apps.
Coding, because of its changeable nature is the first victim of the humans nature unsatisfying.

Modern software industry has so much of techniques and principles (solid, liquid, patterns, testing that that the air is air) and still needs so many developers to work on a project.
I know that you will blame the market needs (you cannot understand the need from the start, you have to do it agile) but i think that this is also a part of a problem .
Old devices evolved at much more slow pace. Radio was radio, and still a radio do its basic functionality the same war (the upgrades were only some memory functionalities like save your beloved frequencies and screen messages).

Although all answers are valid, i still feel, that we have failed. We have failed so much. The dream of being a programmer is to build something, bring you money or satisfaction, and you are bored so you build something completely new.

What is it about programming that makes coding so satisfying when it actually works?

Challenge: what do you think is the most useful bit of software ever made?