How A Good Hacker Mindset Can Make You A Better Programmer

How A Good Hacker Mindset Can Make You A Better Programmer

How A Good Hacker Mindset Can Make You A Better Programmer

This article was originally printed on .cult by Mynah Marie. .cult is a networking platform for untold programmer stories, where programmers can read content around the softer side of watch and development documentaries about the technician they love.

I recall when my parents bought our first house computer. I remember looking at this cryptic “box” and thinking to myself, “how exactly does it work? Are there little people living inside the box doing all of the work for us?”

Curiosity was killing me and I only wanted to tear it apart but I was a great kid and I didn’t wish to disturb my parents.

It is just well into my adult life that I started to learn to program. Growing up, I guess I revealed some natural tendencies for the Arts and imagination because my parents chose to encourage that side of me rather than the curious side I had for science.

I was well into my adult life when I discovered programming, so I remembered this feeling I had as a child: the fascination for how things work and this incredible urge to want to tear things apart to know them better.

To me, that’s the essence of hacking and the inspiration which prompted the birth of what we call the hacker civilization.

Fast forward 30 decades, I am working as a Java script mentor at a coding Bootcamp and I am sitting in the classroom listening to the students’ research demonstrations. We’re doing Week 6 — database week — along with the students are learning the essentials of SQL syntax as well as the fundamental issues around safety and database management.

In one of the demonstrations, some pupils were requested to talk about security issues associated with SQL. They spoke briefly about SQL injections and cross-site scripting however I believed this was all very theoretical for them. I always try to encourage students to understand the effect these vulnerabilities could have in the real world.

So I inquired, “Can you try it?”

“Try what?”, they asked.

“Did you try creating a small database you could split? Can you find a sensible code illustration vulnerable to an injection?”

And well, they hadn’t.

Hacking and hackers today have a very poor reputation. As a result, hacker culture has gotten hugely misunderstood.

It is a fact that security in cyberspace hasn’t before been this important concern. It’s a fact that the more society depends on technology, the faster the growth cycle becomes, and the more the proportion of potential security problems increases.

It’s a dangerous world out there on the internet.

But during all this accelerated development, it’s important to remember how it all began.

Therefore, what exactly did “hacking” mean back in those days? What would be the ideologies that drove the production of that which we know today as hacker culture’?

Hacking meant you had an insatiable curiosity to understand the machines worked beyond the explanations that were given to you personally.

Hacking meant living in a world full of chances at which the query “what should? ” drove individuals to important discoveries and inventions.

Hacking meant having the desire to get the most out of the hardware you had at your disposition, even if (and some would say especially if) that hardware had very limited capabilities.

Hacking was about experimentation and most of all, hacking was FUN. Breaking stuff was a method to better comprehend the technologies surrounding us.

From Wikipedia, we can read:

The hacker culture is a subculture of those who like the intellectual challenge of creatively overcoming limitations of software systems to attain novel and clever outcomes.

Developers at MIT spoke about discoveries concerning their hack value, a term that nearly completely disappeared from the current tech jargon.

So what exactly does this mean to us as programmers today?

Being a programmer is not merely about building, it’s also about understanding the limits of the applications we build. To do that, I think that it’s important to question how the technologies we use work and not just take languages and frameworks for granted.

For me, understanding safety in program development comes in the specific same mindset I described earlier. It is that same want to tear things apart to understand how they work; that same obsession, which what if, always driving us to answer questions nobody else thinks to ask.

Everything we produce is built on top of someone else’s work. These days, companies are so absorbed by getting results quickly that, as programmers, it’s easy to skip a number of these fundamental measures necessary to understand exactly what our code is doing under-the-hood.

Also Read: Here Is The Ways To Manage Your Remote Employee’s Device Security

Hey, we are all human!

However, a healthy hacker mindset can help us constantly give our absolute best by remaining inspired and driven by our fascination instead of feeling drained by frustration.

I like this quote from the TV show Mr. Robot:

“A bug is never just a mistake. It represents something bigger. An error of thinking. That makes you who you are. — Elliot Anderson

So how can we develop a healthy hacker mindset?

The solution is straightforward: begin breaking things! Anything. Build something little and then attempt to break it. Find bugs in your projects and instead of repairing them immediately, ask yourself: “What chances does this bug open? How do I harness this?”

Before you know it, you’ll be amazed at the number of new things you’ll learn and how much additional value you will have the ability to add to your team on the job. And while having a fantastic deal of fun! Because a hacker mindset does bring a small mischievous feeling… and, well, it’s interesting to feel like a rebel once in a while.

Post a Comment