I wrote a Blender plugin that uses vector math, matrices, calculus, trigonometry, and likely other types of math. There's recursion, filesystem access, image processing, interface logic, and on and on.

And worst of all - other people are expected to use it, so there's added pressure to do a good job.

Oh, the hours I spent trying to figure out why the imported geometry looked like an exploded mess. Fumbling around with mathematics I didn't fully understand was exhausting. Finding help was impossible at times because I didn't have the vocabulary to even describe the problems I was having. And getting it to complete an import before the heat death of the universe was not easy.

Every time I made progress and thought I was done, I would discover a bug that other importers didn't have, leaving me to sift through languages that definitely aren't Python to see if I could reverse engineer the logic they used.

I almost gave up a few times, but didn't.

Now I have something that, while not used by many people, works very well, is very efficient, and doubles as a palette cleanser when I need to do something for fun or for a challenge. Plus I learned a lot along the way.

Well, I never had faith to begin with

A more interesting related fact is that this Tuesday I got fired and it was the first occasion that an event that impacted my career didn't have tenfold the impact on my faith in my own abilities. In fact, I didn't even really feel responsible at all. They were clearly looking for a senior with low self-esteem.

Now I just have to figure out how I'll feed myself for four more months before I graduate and get a full-time job anywhere around London.

Wow, some guys here have the means to travel to the future!! Cool!! I too want some of that action!

I work as a freelancer and one time I had a client that needed some work done on a crypto website. I was so hyped up because the money was good so I jumped on it. Fast forward 2 weeks later I still couldn’t figure what the shit I was doing as the client kept asking for update.

Yes, I have experience with blockchain but my skill on Javascript just couldn’t help. I did google and also ask questions on S.O. but it wasn’t enough to get me on track.

At the end, I reached out to the client and apologized for not being able to meet up with their request and then recommended someone else.
So I’d say “I lost faith” on my skill as a Javascript dev at that moment for not being able to use some blockchain APIs effectively and also look forward to improving my catalog.

The first job I had, asked me to build a simple CRUD functionality in CodeIgniter (It was popular in 2017).

I wasn't able to understand the framework and its ins and outs.
(I only knew Core PHP at that point).

It took me 3 days to finish the task and I got yelled at by the team leader because of it and I almost broke down crying. At that point I was convinced that web development career isn't for me.

many many times in the past I had this impostor syndrome in various situations but I never lost faith in my dev skills!

you have to be humble to realise that this situations are fine and that you will learn something from it (not necessarily tech things, but also how life works). Also you have to realise that development as everything else in life is just never ending learning endeavour! When you accept all of that, impostor syndrome goes away forever.

It's been around 3 years since I felt like impostor for the last time because I accepted who I am as a person.

It crawled up on me last week in a different way - I was thinking of myself - what if I am just really good at googling things and understanding how those things work but I am also very capable problem solver so I can understand the principle and apply it to my code.

Then I realised - ok, that's what programmers do! So that's the story of how the impostor syndrome actually become confirmation syndrome!

Folks, believe in yourself, be forgiving to yourself as we all were there, give yourself some time as people don't become good developers overnight - and this is OK.

All the time

Loosing faith...

Interesting question.

I don't think skills have something to do with faith.

If you don't know something, ask someone who does.

Even If I cannot solve a problem or deem a problem unsolvable, I usually don't doubt myself.

There are rare moments where I throw a fit, but that's not loosing faith, thats just being angry because my stubborn thick skull cannot make sense of it, which annoys me.

Might sound cocky, but in my opinion dev skills are not "do or die". Problem could be solved at a later time, maybe never. Who cares?

Loosing faith would mean to me that I define myself in some way on the ability to solve sth that doesn't have to be solved at all.

XD

After all, if it doesn't work, I don't give a fuck.

*Cheers*.

Every day…

Daily-

Writing simple driver for AT24C256 eeprom on pico (RP2040)

It turned out it was FT24C256A, which should follow same protocol.

After literally over month of coming back to it, getting stuck again, rewriting things (including some functions of pico-sdk), i almost gave up a d started just yolo trying random shit.

Afterall the documentation on addressing the chip fucking missled me -_- (1st bit is r/w flag and 2-7 bits are address, counted from MSB->LSB)

I made it work yesterday.

In meantime Ive rewritten Wire library, Ive modified someone's else rewrite, extended sdk to allow getting i2c registers, tried to use tiny go just to learn it doesnt support i2c slave mode, resoldered entire thing few times, measured connections few too many times etc.

Frustrated I doubted I will ever manage to finish putting this project together because it looked like Im just too noob.

When i was fired in a few minutes in my first meeting with the boss since i was working there.
but now im glad im out of there. The kpis they use to see how someone performs are utterly useless.

When I had a burnout failing to complete a uni task.

I was trying to implement a parallel version of the Barnes-Hut algorithm for the N-body problem. Spent way too many hours on that.

At the very start when I learned my first language. Didn't know where to find the "{" and "}" keys on the keyboard. Thought I would never be a dev, since I couldn't write a program without those keys.
Or when I didn't understand the notation of accessing values inside an array. Thought things like array[0] would do some magic to the array and didn't know how to access other parts of an array. I was following a book back then.

Going for a technical interview and being thrown at a site with a bunch of tests I've never seen

When I saw what teleric controls made my project work like