As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

During an Interview:
- What's your greatest strength?
- Perseverance.
- Ok, thank you, we'll contact you!
- I'll wait here...

When you come back to the first link you found googling and only now you understand it because of the bits and pieces you gathered meanwhile.

My personal android app project started at android 1.5 and actually went to google play when android 4.2 was launched... With the look and feel of android 1.5...

Prior to that I spent about 2 years trying to make an Adobe Air app out of it.

I feel proud of my perseverance.

My dad, who doesn't know shit about programming, but knows absolutely everything about perseverance and motivation.

1. There is nothing in this field that is impossible or out of reach for someone with the correct dedication and perseverance. Even if you suck at a particular topic, I highly believe that you can make sense of it through computer science, be it math, biology physics, finances etc. The field opens the doors to other subjects. This is true for everything else, but I seriously believe that Comp Sci makes it more reachable.

2. You cannot make development a quirky personality trait. There is more to life than just sitting around all day fucking with a computer, but at the same time that is how you hone your skills, find balance!

3. Being attractive and or charismatic in this field pays a lot, but also makes you a target.

4. I have never met more people in my life I wanted to punch to a pulp, and I worked in retail and was in the military....that says a lot.

5. Penises, there are way too many penises in this field. I hate being surrounded by dudes and since I grew up in a nail/hair salon I am more used/enjoy female company more.

6. Stuxnet se la come.

I mentor two profiles (started in their master first year), and for 3 years: taking them with me when I have a job change and applying ShuHaRi to teach them. They are my firsts mentorees in France, and they are finishing the course.

And I'm SO proud of them, they'll be leaving my side (changing job). And starting their own journey!!

They'll go to very good companies, for really good jobs/teams. I gave them tears and blood for 3 years and now they are riping the results of their perseverance, hard work and commitment.
It's one of the things that I love in my job. Being able to do that, and to see them grow it so cool!!

On the other hand, I'll lose have to replace them... And it'll be difficult for the company to find good profiles. And I'll start looking for a new mentoree to follow.

Software Devs are less supportive than the community tries to convey. They're also part of the most self-deluded and obnoxious crowd that exists on earth.

Someone saying they don't enjoy coding 24/7 outside of work? You actually enjoy totally different hobbies that have next to nothing to do with coding?
- Shitty developer, you should probably work elsewhere. Maybe flipping burgers.

"Coding in <Framework X> is SO friggin' easy. You're basically subhuman garbage if you can't learn it within a month!"

Watch some YouTube Videos with the "Freelancer Success Stories" of dudes that haven't - apparently coded, ever - and started to code late in life and tell you how perseverance and learning brings the success and yet you never see any repos of those guys. You see those guys mostly go on for up to half an hour to regurgitate some hot garbage you can read up within two minutes yourself from ANY coding blog.

You're not using a macbook to develop?
- "Oooof, man! How can you?"

You don't really like "Popular Framework X"?
- Especially when it comes to Frontend Frameworks prepare to either die on the hill of your beliefs or die a futile and slow death when people - more or less - snarkily try to dissect your opinion in order to try - again, more or less - to hide their own bias. Because don't forget, your opinion is OBJECTIVELY wrong and you simply happen to a garbage developer for (dis-)liking something.

You DO like "Popular Framework X"?
- Well, rinse and repeat basically.

You struggle to get a new job?
- All your fault. You clearly didn't spend enough time coding; you should have at least 12 Open-Source Projects with at least 100k downloads the week.

There is actually a whole lot more, but I feel I'm basically done with software dev. Software development is neither creative nor terribly fun. I'm just angry at myself that I switched careers for the money.

!rant
School and college introduced me to programming.
Personal perseverance and an excellent group of friends made me better at it.

1. Learn to read and understand the errors and exception messages. While writing code you're going to be facing exceptions most of the time and the real cause of them is under a lot of generic error messages. That and a lot of patience and perseverance.

2. You're going to face clients and bosses that ask you to do a temporary "workaround" even though you know there is a best way to solve a problem even if it takes more time and effort. Don't "crash" against their ideas, try to find a mid-term between the fast and easy work around and the best solution and leave it open to improve it in the future. I have met a lot of developers that let the frustration stops them to be creative just because the approved development is not what they wanted to do.

Yesterday I pulled 36 straight hours of coding compression algorithms. So help me god, I never want to look at another... Until I need to continue next week. ¯\_(ツ)_/¯

So here's a story..

Whenever we have a job announcement, whether tech or dev, there's this one guy who applies every single time and never gets selected. I have interviewed him once and learnt that he doesn't in fact have the skills or experience we're looking for. Also someone else with better experience applies everytime. He's been doing this for more than 3 years now.

Now WE feel embarrassed everytime he comes in for interview.

You can't blame him for wanting to work so much with one of the best teams in our tiny country. I gotta say I really admire his perseverance and I think and hope that he's gonna find what he's looking for with that kinda perseverance.

All is well in 2020 and claiming today will be my year.

1 updated my curriculum vitae and send my resignation love letter
2 hopefully be hired in a stable company and earn enough that can suffice my needs and wants as I moved out from my big sis home. Thank you ^_^
3 move into my long awaited own house for a couple of weeks. Thanks patience and perseverance ^_^
4 self study for freelance projects
5 settle down

I believe it is really useful because all of the elements of discipline and perseverance that are required to be effective in the workforce will be tested in one way or another by a higher learning institution. Getting my degree made me little more tolerant of other people and the idea of working with others, it also exposed me to a lot of topics that I was otherwise uninterested and ended up loving. For example, prior to going into uni I was a firm believer that I could and was going to learn all regarding web dev by maaaaaself without the need of a school. I wasn't wrong. And most of you wouldn't be wrong. Buuuuuut what I didn't know is how interesting compiler design was, how systems level development was etc etc. School exposed me to many topics that would have taken me time to get to them otherwise and not just on CS, but on many other fields.

I honestly believe that deciding to NOT go to school and perpetuating the idea that school is not needed in the field of software development ultimately harms our field by making it look like a trade.

Pffft you don't need to pay Johnny his $50dllrs an hour rate! They don't need school to learn that shit! Anyone can do it give him 9.50 and call it a day!<------- that is shit i have heard before.

I also believe that it is funny that people tend to believe that the idea of self learning will put you above and beyond a graduate as if the notion of self learning was sort of a mutually exclusive deal. I mean, congrats on learning about if statements man! I had to spend time out of class self learning discrete math and relearning everything regarding calculus and literally every math topic under the sun(my CS degree was very math oriented) while simultaneously applying those concepts in mathematica, r, python ,Java and cpp as well as making sure our shit lil OS emulation(in C why thank you) worked! Oh and what's that? We have that for next week?

Mind you, I did this while I was already being employed as a web and mobile developer.

Which btw, make sure you don't go to a shit school. ;) it does help in regards to learning the goood shit.

I am a good person. I can even say I am a good programmer. I have worked hard to get where I am and that shows perseverance. Although, where I am right now is not what I expected, I am somewhere. I can do something. I have good intentions.

Someday, I will build software which will be used by millions of people around the interwebs. And they will love me, for I will have made their lives better....in some way. Some will even consider paying me for it. Not because the well placed and non intrusive donate button I put there, but out of pure adoration and bare necessity to preserve someone as brilliant and precious as me. I shall be the definition of success. But I long for neither adoration nor wealth, for I am humble or at least that is how I will be perceived.

Like flies to the honey my success will attract big evil corporations to acquire my business. And I shall spit on their wretched face....at first. I would like to be wooed. Such display of integrity shall inspire generations of programmers. Let ye be inspired. There will be those who envy my achievements and they will be mocked and shunned by my true believers. But being the kind soul that I am, I will bring back my minions, for it could a PR nightmare.

All these events will take place in a not too distant future. Sure, I am going through a dark time now, it will pass. 'tis nothing but me transitioning from a lame ass PHP coder moth to this totally badass software engineer who is also a cool bro. This eclipse of my brain shall pass. My neurons will fire in all directions like photons from the sun during late winter, for it may overheat and we definitely don't want that.

I pray to the gods of engineering to grant my wishes. Trust me guys, you will be thanking yourselves when donate my money to charities that will help me set up. But that's another scheme. Amen.

How do I make my manager understand that something isn’t doable no matter how much effort, time and perseverance are put into it?

———context———
I’ve been tasked in optimizing a process that goes through a list of sites using the api that manage said sites. The main bottle neck of the process are the requests made to the api. I went as far as making multiple accounts to have multiple tokens fetch the data, balance the loads on the different accounts, make requests in parallel, make dedicated sub processes for each chunks. All of this doesn’t even help that much considering we end up getting rate limited anyway. As for the maintainer of the API, it’s a straight no-can-do if we ask to decrease the rate limit for us.

Essentially I did everything you could possibly do to optimize the process and yet… That’s not enough, it doesn’t fit the 2 days max process time spec that was given to me. So I decided I would tell them that the specs wouldn’t match what’s possible but they insist on 2 days.

I’ve even proposed a valid alternative but they don’t like it either, admittedly it’s not the best as it’s marked as “depreciated” but it would allow us to process data in real time instead of iterating each site.

Our site ran into a cache stampede which took down the site for awhile. While people were helping out, I just stayed out of their way since I knew nothing about it -_-

I realise I need to git gud but I can't help feeling inadequate and useless at times like this.

Is perseverance, experience, and passion to keep learning and bettering oneself the only way to being a master?

Programming is like climbing a giant mountain covered with other smaller mountains. You conquer one small mountain (i.e. bugs, refactor, etc) just to realize there are many more mountains ahead before you get anywhere near the final summit.

There are days you feel like a God and there days you have no idea what you are doing in the dev space.

All in all perseverance with a whimsical tone

Sometimes, I feel like this profession is a piece of shit. There's more to life than all these stresses. There's gotta be a better way to make more money, I just need more perseverance.

Can't single out one so: perseverance, Bootstrap CSS, SQL Procedures