I have a junior who really drives me up a wall. He's been a junior for a couple of years now (since he started as an intern here).

He always looks for the quickest, cheapest, easiest solution he can possibly think of to all his tickets. Most of it pretty much just involves copy/pasting code that has similar functionality from elsewhere in the application, tweaking some variable names and calling it a day. And I mean, I'm not knocking copy/paste solutions at all, because that's a perfectly valid way of learning certain things, provided that one actually analyzes the code they are cloning, and actually modifies it in a way that solves the problem, and can potentially extend the ability to reuse the original code. This is rarely the case with this guy.

I've tried to gently encourage this person to take their time with things, and really put some thought into design with his solutions instead of rushing to finish; because ultimately all the time he spends on reworks could have been spent on doing it right the first time. Problem is, this guy is very stubborn, and gets very defensive when any sort of insinuation is made that he needs to improve on something. My advice to actually spend time analyzing how an interface was used, or how an extension method can be further extended before trying to brute-force your way through the problem seems to fall on deaf ears.

I always like to include my juniors on my pull requests; even though I pretty much have all final say in what gets merged, I like to encourage not only all devs be given thoughtful, constructive criticism, regardless of "rank" but also give them the opportunity to see how others write code and learn by asking questions, and analyzing why I approached the problem the way I did. It seems like this dev consistently uses this opportunity to get in as many public digs as he can on my work by going for the low-hanging fruit: "whitespace", "add comments, this code isn't self-documenting", and "an if/else here is more readable and consistent with this file than a ternary statement". Like dude, c'mon. Can you at least analyze the logic and see if it's sound? or perhaps offer a better way of doing something, or ask if the way I did something really makes sense?

Mid-Year reviews are due this week; I'm really struggling to find any way to document any sort of progress he's made. Once in a great while, he does surprise me and prove that he's capable of figuring out how something works and manage to use the mechanisms properly to solve a problem. At the very least he's productive (in terms of always working on assigned work). And because of this, he's likely safe from losing his job because the company considers him cheap labor. He is very underpaid, but also very under-qualified.

He's my most problematic junior; worst part is, he only has a job because of me: I wanted to give the benefit of the doubt when my boss asked me if we should extend an offer, as I thought it was only fair to give the opportunity to grow and prove himself like I was given. But I'm also starting to toe the line of being a good mentor by giving opportunities to learn, and falling behind on work because I could have just done it myself in a fraction of the time.

I hate managing people. I miss the days of code + spotify for 10 hours a day then going home.

The worst part of being a dev

My social dilemma

In a fast paced world where the average human spends at least 6 hours a day with technology, deriving basic entertainment, pleasures and engaging in various activities.

Here we are the developers that have to engage with technology for longer hours for a living , having to keep up with deadlines, immersing our minds in complicated algorithms and then the endless possibilities of entertainment from the machine in so few human hours a day , you wonder how you’d get off, and to top it up, I personally work from home.

And then the dilemma of overcoming different suggestions from various parties in taking a break off, a break off to what you later ask yourself, thus creating the shadow of doubt, splitting the fragile programmer’s mind , trying to solve this imaginary puzzle, “this bug of the mind”.

Then the challenge often arises in creating a balance, telling yourself, just catching up with people with this same technology takes a whole day, or then again quitting my Job, but from my little experience of life, nobody likes a poor visitor, this is actually worse than a “bug” and as I bask in this quagmire, “a little voice in my head keeps singing keep doing what you love doing”.

Like an infinite loop of crazy, spiralling back to these machines, trying the find and fix the balance of normalcy. Always remembered the cool years of college tho, with so much people around and then again that was college.

An then the thought arises, maybe something else might be worth doing, but after so much time spent in building your skills and the enormous joy of programming even typing without looking at the keyboard is a real pleasure, and yeah sure the days are short with the reality of a constant need to survive, remain sane, compete and make the best of life in such short time.

Then how do we know if we have fallen off the so-called “social track”, when we have only lived so little to really comprehend the most parts of life? with such constant stream of unanswered question, you’d realise you shouldn’t have burdened the mind creating such questions in the first place

But then again maybe it gets better, one of the above, the disturbed mind or the situation as whole and yes I try oh I try, I place calls, do some visiting, no relationship tho but with a good perspective in mind.

In this race of life, you sometimes ask yourself would you rather be in a different position, or maybe already put exactly where we belong. For this illusionary fight with self is a fight with reality as a whole and true bliss comes from actually letting go as time and people pass you by.

And my greatest achievement to date aside family and my work is getting into the 1000 club on devRant.

Honestly, mentoring is in my opinion the best part of the job. My firts mentee was a student in my last job, smart af but lazy and unable to trust in herself. I wasn't really too sure in myself at the time either but since I had to teach hery craft there was no place for me to doubt myself.

So I taught her everything I knew and in turn I learned to trust myself and once I had mastered the art of self confidence I could make her believe in herself. Since then I trained five more test automation engineers, some of them might be close to surpassing their 'master' (though won't make it easy for them 😏) and with every Single one I've developed a deeper understanding of my craft by explaining. I needed to research stuff I never questioned to answer their questions and therefor became better at what I do.

Three weeks ago I got an email from the girl I first mentored, she's in another company now and she thanked me for what I taught her. In my opinion I did a rwally Bad job at it (it was my first time teaching) but reading someone actually believing that one made an impact in their life is something special.

I always loved talking about my craft and I love sharing the knowledge I aquired. Test automation is not a thankfull craft but I'm always happy whenever I can interest someone in it and I fully enjoy seeing them grow and improve into fully fledged TAEs.

So we had this legacy Objective-C codebase for a mobile app that was actually pretty good: I'd inherited the codebase and spent the past several years gradually improving it and I was actually quite proud of the work I put into it. So of course management decides to scrap it (with NO consultation from the engineers) and outsource a complete rewrite of the app in C# for Windows Universal.

Let me tell you. That code was without a doubt and without exaggeration the *worst* code I've seen in my close to 30 years of experience as a developer. I mean they broke every rule in the book, I'm talking rookie mistakes. Copypasta everywhere, no consistent separation of concerns, and yet way too many layers. Unnecessary layers. Layers for the sake of layers. There was en entire abstraction layer complete with a replicated version of every single data class *just* to map properties in pascal case to the same property in camel case. Adding a new field to a payload in the API amounted to hours of work and about eight different files that needed to be modified. It was a complete nightmare. This was supposed to be a thin client, yet it had a complete client-side Sqlite database with its own custom schema (oh and of course a layer for that!) completely unrelated to the serverside schema, just for kicks. The project was broken up into about eight or nine different subprojects, each having their own specific dependencies on various of the other subprojects in such a tightly-knit way that it made gradual refactoring almost impossible. This architecture was so impressively bad, it was actually self-preserving!

Suffice it to say it was a complete nightmare, and was one of the main reasons I ended up leaving that company. So just sayin', legacy code isn't always bad. :)

!dev

I had semi-jokingly changed my username from dextel2 to nothappy, because of that one bad day.

But, it is now when I realized that I am actually NOT HAPPY, things are lately rough, I am constantly scared for no reason, I doubt my skills, I doubt myself for no reason, and top of that there's always a chance for another epileptic attack.

I tried and keep trying to distract myself from negative thoughts but the more I try the more I fail, I've become distant with my younger brother, for the record I'm very overprotective about him. I don't even know if he feels the same, as this year ends or every day passes by I feel changed from my past self (not in a good way).

Switched my first job to get another good job, turns out they don't even have any projects and I'm just a guy they are showcasing like they have ONE amateur developer and we are looking for an entire project and it did work for one client which I'm gonna deny personally because the client is not clear about the project itself, I do not care about the consequences, my heart lies in academics and I'll put my 100% in academics, shall I'm kicked.

A lot has happened in this year, but this one is/was unique and very hard to process. I've always been joyful, sarcastic, funny, you name it, but all of it has just vanished, don't know why. I'm also becoming distant from my ONLY 3 friends and parents.

I've been fighting with my xmlrant.com hosting provider for a good several days now regarding enabling web deploy for my account.

According to their screenshot it all works, according to my various attempts still getting either 404 or 401 with the same login / server details!

So frustrating... It almost looks as though same authentication works differently for them locally and for me externally... Maybe domain name needs to be in FQDN format... Or smth else... Either way this will probably end up with them saying fuck off, all is working on our end.

And as well it might - it just might be my incompetence... *self-doubt creeping in*

But it's still frustrating nevertheless.

So far I need to settle for unreliable FTP deploy, which introduces big overhead as always copies entire deployment folder, even is only a few files are actually changed.

*Le sigh*

I've started working at one of the biggest names in tech (think Microsoft) for a while now, and I gotta say, it feels surprising very corporate, robotic and I haven't been able to connect with my team much. I worked at a start-up a while ago and my experience there was better in every way (except for pay). At the start-up, my boss was amazed at the amount of work I put out. Now here my performance is listed as "needs improvement.

Ever since I took this job, I have lost my self-confidence and I'm starting to doubt if I'm even that good anymore. My dad made remarks that maybe I shouldn't be in dev, and go into other fields of engineering. It was always my dream to work one of the big 5 like Google and Facebook, but now I'm still not happy.

What do I do? Should I try to adapt to that company, so I can make a few bucks? Should I go back to the start-up and ask for a job again? Will I be happy there?

Like age 8?
As a kid I really liked flash games and animations and wanted to get into it. I couldn't do flash, it looked too complicated but I found a little software by the name od KoolMoves that was just a simpler flash animation tool.

I did a bunch of shitty stick figure animations in it (hello to everyone from stick figure death theatre) but eventually I realized that I can make it do things (interactive menus, choose your story kinda things, move the player around, shoot...!)

I fell in love with AS1 and later AS2.0 and made bunch of demos and proof of concepts for systems and games. Most are lost to time and datarot by now)

Age 12
Eventually I found out I can make the entire Windows machine do what I want using first Batch files and later Visual Basic script (made a skype bot!) At this point I was also really into graphics and logo/web design

Age 15 - 20 or so
Then it was pretty natural to move to actual Visual Basic, then C# and finally I to C++. And I had the C family in my heart forever. I managed to get a but into 3D graphics too and got a part-time in archviz

Even by this point I never believed I could be a programmer as a profession. I thought of it just as something I love, but have no chance getting into compared to some of the names out there. I half expected to be either doing graphics (cause I found it simple at the time) or some shitty random job in an office.

20+
Finally I decided to go to uni and study software development, see if I can touch the future I always dreamed of! And... Well... I found out more than 80% of the people there never touch a language up until now and most people are just as retarded as I thought..

For a while I also worked as a game designer (still not being comfortable calling myself a programmer, so I chose a non programming position) but I ended up going into the code and improving and fixing game designer tools (it was unity and C#)

After seeing actual programmers at work in a company, and talking to a bunch of them I realized I already have everything I need to do this seriously and with that experience out of the way I breezed through uni, learned to love Linux and landed a proper job :)

I kinda hope my experience with long lasting self doubt will be useful for someone

Is it common to freak out frustrated to the core when you fuck up a project or dependency you've been working on for with full dedication, leading to question your decision of selecting the field, your achievements yet, the whole point of existence. Then suddenly fix it after two hours of pulling hair out and looking back feeling stupid?
This episode has repeated over and over recently.