I'm at my seat during the regular morning routine of checking emails, planning the things I need to complete/study when my phone rings.

HR: Good Morning, can you come over to the conference room please ?

Me: Sure

I enter the conference room and on the other side of the table, I see a group of 3 HR Managers (not a very nice feeling), especially when it was 10 months into my first job as a Trainee Software Developer.

HR: The company hasn't been performing as expected. For this reason, we've been told to cut down our staff. We're sorry but we have to let you go. You've been doing a great job all along. Thank you.

Me: ---- (seriously ?!)

The security-in-chief 'escorts' me out of the premises and I hand over the badge. I'm not allowed to return to my desk.

This happened about 16 years ago. But it stuck with me throughout my programming career.

A couple of Lessons Learnt which may help some of the developers today :

- You're not as important as you think, no matter what you do and how well you do it.
- Working hard is one thing, working smart is another. You'll understand the difference when your appraisals comes around each year.
- Focus on your work but always keep an eye on your company's health.
- Be patient with your Manager; if you're having a rough time, its likely he/she is suffering more.
- Programming solo is great fun. However it takes other skills that are not so interesting, to earn a living.
- You may think the Clients sounds stupid, talks silly and demands the stars; ever wonder what they think about you.
- When faced with a tough problem, try to 'fix' the Client first, then look for a solution.
- If you hate making code changes, don't curse the Client or your Manager - we coders collectively created a world of infinite possibilities. No point blaming them.
- Sharing your ideas matter.
- Software Development is a really long chain of ever-growing links that you may grok rather late in your career. But its still worth all the effort if you enjoy it.

I like to think of programming as a pursuit that combines mathematical precision and artistic randomness to create some pretty amazing stuff.

Thanks for reading.

Soms week ago a client came to me with the request to restructure the nameservers for his hosting company. Due to the requirements, I soon realised none of the existing DNS servers would be a perfect fit. Me, being a PHP programmer with some decent general linux/server skills decided to do what I do best: write a small nameservers which could execute the zone transfers... in PHP. I proposed the plan to the client and explained to him how this was going to solve all of his problems. He agreed and started worked.

After a few week of reading a dozen RFC documents on the DNS protocol I wrote a DNS library capable of reading/writing the master file format and reading/writing the binary wire format (we needed this anyway, we had some more projects where PHP did not provide is with enough control over the DNS queries). In short, I wrote a decent DNS resolver.

Another two weeks I was working on the actual DNS server which would handle the NOTIFY queries and execute the zone transfers (AXFR queries). I used the pthreads extension to make the server behave like an actual server which can handle multiple request at once. It took some time (in my opinion the pthreads extension is not extremely well documented and a lot of its behavior has to be detected through trail and error, or, reading the C source code. However, it still is a pretty decent extension.)

Yesterday, while debugging some last issues, the DNS server written in PHP received its first NOTIFY about a changed DNS zone. It executed the zone transfer and updated the real database of the actual primary DNS server. I was extremely euphoric and I began to realise what I wrote in the weeks before. I shared the good news the client and with some other people (a network engineer, a server administrator, a junior programmer, etc.). None of which really seemed to understand what I did. The most positive response was: "So, you can execute a zone transfer?", in a kind of condescending way.

This was one of those moments I realised again, most of the people, even those who are fairly technical, will never understand what we programmers do. My euphoric moment soon became a moment of loneliness...

*signs up for Skillshare*
> Sorry, your password is longer than our database's glory hole can handle.
> Please shorten your password cumload to only 64 characters at most, otherwise our database will be unhappy.

Motherf-...

Well, I've got a separate email address from my domain and a unique password for them. So shortening it and risking getting that account stolen by plaintext shit won't really matter, especially since I'm not adding payment details or anything.

*continues through the sign-up process for premium courses, with "no attachments, cancel anytime"*
> You need to provide a credit card to continue with our "free" premium trial.

Yeah fuck you too. I don't even have a credit card. It's quite uncommon in Europe, you know? We don't have magstripe shit that can go below 0 on ya.. well the former we still do but only for compatibility reasons. We mainly use chip technology (which leverages asymmetric cryptography, awesome!) that usually can't go much below 0 here nowadays. Debit cards, not credit cards.

Well, guess it's time to delete that account as well. So much for acquiring fucking knowledge from "experts". Guess I'll have to stick to reading wikis and doing my ducking-fu to select reliable sources, test them and acquire skills of my own. That's how I've done it for years, and that's how it's been working pretty fucking well for me. Unlike this deceptive security clusterfuck!

Manager: You can’t define an async function without using await.

Dev: Yes you can.

Manager: Well you shouldn’t, there’s no point!

Dev: Yes there is. It can turn blocking synchronous logic into work performed concurrently. In this case the perform—

Manager: It’s called async *await*. Async *AWAIT*! Did you hear the two parts to that? You shouldn’t ever have one without the other. THEY GO TOGETHER. Worrying about concurrency is for people who use callbacks which just goes to show how out of date your skills are. I’m reading a book on javascript and there are so many advanced techniques out there that I haven’t even seen you use ONCE!

Dev: …

*I looked at the book he’s reading, it’s from the < ES6 era… no wonder he doesn’t see me using any of those archaic patterns/hacks/workarounds…*

Ok story of my most most recent job search (not sure devRant could handle the load if I was to go through them all)

First a little backstory on why I needed to search for a new job:

Joined a small startup in the blockchain space. They were funded through grants from a non-profit setup by the folks who invented the blockchain and raised funds (they gave those funds out to companies willing to build the various pieces of the network and tools).

We were one of a handful of companies working on the early stages of the network. We built numerous "first"s on the network and spent the majority of our time finding bugs and issues and asking others to fix them so it would become possible, for us to do what we signed up for. We ended up having to build multiple server side applications as middleware to plug massive gaps. All going great, had a lot of success, were told face to face by the foundation not to worry about securing more funds at least for the near term as we were "critical to the success of the network".

1 month later a bug was discovered in our major product, was nasty and we had to take it offline. Nobody lost any funds.

1-2 months later again, the inventor of the blockchain (His majesty, Lord dickhead of cuntinstein) decided to join the foundation as he wasn't happy with the orgs progress and where the network now stood. Immediately says "see that small startup over there ... yeah I hate them. Blackball them from getting anymore money. Use them as an example to others that we are not afraid to cut funds if you fuck up"

Our CEO was informed. He asked for meetings with numerous people, including His royal highness, lord cockbag of never-wrong. The others told our CEO that they didn't agree with the decision, but their hands were tied and they were deeply sorry. Our CEO's pleas with The ghost of Christmas cuntyness, just fell on deaf ears.

CEO broke the news to us, he had 3 weeks of funds left to pay salaries. He'd pay us to keep things going and do whatever we could to reduce server costs, so we could leave everything up long enough for our users to migrate elsewhere. We reduced costs a lot by turning off non essential features, he gave us our last pay check and some great referrals. That was that and we very emotionally closed up shop.

When news got out, we then had to defend ourselves publicly, because the loch ness moron, decided to twist things in his favour. So yeah, AMAZING experience!

So an unemployed and broken man, I did the unthinkable ... I set my linkedin to "open to work". Fuck me every moronic recruiter in a 10,000 mile radius came after me. Didn't matter if I was qualified, didn't matter if I had no experience in that language or type of system, didn't matter if my bio explicitly said "I don't work with X, Y or Z" ... that only made them want me more.

I think I got somewhere around 20 - 30 messages per week, 1 - 2 being actually relevant to what I do. Applied to dozens of jobs myself, only contacted back by 1, who badly fucked up the job description and I wasn't a fit at all.

Got an email from company ABC, who worked on the same blockchain we got kicked off of. They were looking for people with my skills and the skills of one other dev in the preious company. They heard what happened and our CEO gave us a glowing recommendation. They largely offered us the job, but both of us said that we weren't interested in working anywhere near, that kick needing prick, again. We wanted to go elsewhere.

Went back to searching, finding nothing. The other dev got a contract job elsewhere. The guy from ABC message me again to say look, we understand your issues, you got fucked around. We can do out best to promise you'll never have to speak to, the abominable jizz stain, again. We'll also offer you a much bigger role, and a decent salary bump on top of that.

Told them i'd think about it. We ended up having a few more calls where they showed me designs of all the things they wanted to do, and plans on how they would raise money if the same thing was to ever happen to them. Eventually I gave in and signed up.

So far it was absolutely the right call. Haven't had to speak to the scrotum at all. The company is run entirely by engineers. Theres no 14 meetings per week to discuss "where we are" which just involves reading our planning tool tickets, out loud. I'm currently being left alone 99% of the week to get work done. and i'm largely in-charge of everything mobile. It was a fucking hellhole of a trip, but I came out the other side better off

I'm sure there is a thought provoking, meaningful quote I could be writing now about how "things always work out" or that crap. But remembering it all just leaves me with the desire to find him and shove a cactus where the sun don't shine

.... happy job hunting everyone!

HR: why you want to work with us.

Me inside: you stupid, because you need my skills and I need your stupid money, stop reading articles about stupid interview questions.

Me: because I love to work on such amazing environment, and I really love the technology you're using.

Just before you, my fellow system programmer, scroll past this, let me say this:

🍬 The web is actiually simple. 🍬

Both HTML and CSS is declarative. It's all easy when you understand the concepts, learn how to be idiomatic and quit trying to do that imperative bullshit in languages that aren't imperative.

HTML is simple. You know the boilerplate: doctype, head, body, that's all. Just mark it up and do NOT look at it before you end, mark it up as it were article or something. The appearance is up to css.

CSS is simple. You may even forget bem or rscss, you're already a skilled software developer. Use common sense and your code-splitting and naming skills you gained reading The Code Complete or doing software development for years.

Forget mockups. Forget absolute positioning, forget setting width and height in pixels. Go to awwwards, find some inspiration. Draw some buttons and fields on paper with your good old pencil. Then go and write some css. Feel free to steal some shadows and transitions from codepen.

Read about 8-pixel grid system. Let every element push away from others by setting something like margin: 16px; and whoops! You've just got fully responsive and got great vertical rhythm without even using media queries!

Oh my god, do NEVER set width and height explicitly! Type something like button { width: 120px; } and bang! The entire web page is broken. Quit that shit. Let it resize as it should. It will resize itself to fit its contents.

HTML is by default ready for your template engine. That's how you receive data from server — as server-side rendered, plain old HTML page. On the other hand, the form element is the most axiomatic and simple way to send the data to server. That's how you send it — as plain old GET or POST that every webserver can handle.

All of there are true:
1. It's easy to get great 100% responsiveness without media queries.
2. It's easy to align items in row, it's just one line of css. Maybe two, if you still want elements to wrap, but want to use flexbox:
.parent {
display: flex;
flex-wrap: wrap;
}
3. HTML and CSS are fast by default.
4. You don't need mockups to achieve great visual experience. Mockups is imperative, web is declarative.
5. You may not even need JavaScript to make great website.

Go on, ask me a question about web! I'll ready to answer everything.

The reason why hiring a Recruiter in Software/Web Development industry is a waste of time and money.
- A real story from 2 years ago.

**few minutes of recruiter reading my resume, skills and whatnot**

Recruiter: Okay sir, we are looking for people skilled in C# for our app development and Java for our business software envirnoment. Which one are you interested in.

Me: C#.

Recruiter: I see, well.. I'm afraid we already have someone for the seat.. *checks resume again*.. maybe you would be interested in Java?

Me: Not really, why is that if I may ask?

Recruiter: Well, says here you have experience in Javascript

Me: *trying not to cringe* Yes, but I didn't see any Javascript related job available.

Recruiter: Correct me if I'm wrong, but isn't "Java" just short for Javascript?

Me: No, just like C# isn't short for C and C++

Recruiter: *oops* then I think we do have a free spot for you.

TL;DR - the guy had guidelines but no field-specific knowledge.. I only feel sorry for the other guy who thought he got the job lol.

Reading open source projects made me doubt my skills but also was the cause of improving them :')

I'm a shit programmer

I'm 29 and I assumed that by this point I'd be successful some way or another, either by being financially abundant or technically complex.

I am not, just mildly accomplished instead.

Here'a list of thing I consider challenges that I have:
* I tend to tunnel vision ideas that are terrible or execute them poorly because of said tunnel vision.
* I don't hone my skills, I usually consider my potentials the same as my actuals, as if I achieved everything already, probably product of ny huge ego.
* I communicate poorly with my boss, I sidetrack into thing he didn't ask
* I'm a mess when it comes to reading documentation online, I have the attention span of a fucking fish.
* I work alone, I have 0 networking status or skills.
* I take huge amounts of time to finish my side projects
* Of all the side projects I started I only finished one, the ones that I couldn't finish usually bevame insabely stressful things, so much and so many that I questioned myself many times if I should be a programmer or not.
* I have little discipline or organization, if I work in more than one thing at a time, i get really anxious and stressed.

I am not saying I'm not competent, I think I am (I'm looking at you imaginary scary recruiter googling this online), I'm just not really proud of myself

Satoru Iwata.

You might remember it as the former president of Nintendo, but he was also a very impressive programmer. As he was president of HAL Laboratories, he helped with the development of Pokémon Stadium for the Nintendo 64 by porting the Pokémon Red/Blue battle system not by having any sort of documentation, but by reading the assembly source code.

He did so to allow Game Freak's developers (who were only a team of 4 at the time) to focus on their work on Pokémon Gold/Silver. But he did more: when they had to localize Red/Blue for America, they couldn't fit everything in a cartridge. They had the same problem while developing Gold/Silver, since cartridges had at most 8 Mb of storage capacity back then, and they had to fit not only the Johto region but the Kanto one as well! So Iwata stepped in, and created a graphics compression tool which managed to make everything fit in the cartridges.

He did this while not even being part of Nintendo, and the work was so impressive that the Pokémon devs thought it was "a waste to just have [him] as president!" (ie. why not make use of such programming skills).

Truly someone I look up to.

#LongRant

I AM SO FUCKING PISSED RIGHT NOW OF ALL YOU DICKHEADS WHO DON'T KNOW SHIT 'BOUT PROGRAMING AND STILL QUALIFY FOR THE NEXT ROUND!

Background: I am a final year student of Computer Science. This time of the year, companies come to the campus to recruit potential employees for their vacant positions. But during the COVID-19 times, the number of such companies and jobs have gone a little down. Two companies came to our university for recruitment — DXC Technology and Hanu Software. I cleared the aptitude/code test for DXC and appeared for the interview, which went fairly well. Waiting on the results. The rant is about the other company.

The Story: I am learning and working on Cloud (AWS specifically) for the past 1 year. I have a cloud Certification in Oracle and working my way to get Azure Certified. Hanu Software, which is a core cloud company (works on Azure) came to our campus for the recruitment (Cloud Engineer). Their test had these sections —
1. Personality (54 Questions; 15 minutes)

2. Verbal (20 Questions; 20 minutes)

3. Reasoning (15 Questions; 15 minutes)

4. Technical (25 Questions; 25 minutes)

5. Quantitative (15 Questions; 15 minutes)

As soon as I finished my Interview with DXC, I had my Hanu test within 30 minutes. I have a Mac so the test by default started on Safari. After completing 4 sections, I receive a mail in Junk from Hanu which stated that only Chrome or Firefox can be used to give the test. AHH! And on Safari.. the platform on which the test was being conducted didn't ask me for any camera permission (the test is monitored, can't even change windows/switch tabs). I then changed the browser to Mozilla Firefox and somehow finish the test. After finishing, I call up my classmates to find out how their test go. Know what? FUCKING TWATS USED GOOGLE LENS TO FIND OUT THE ANSWERS!

Last night, the list of qualifying students arrived and obviously I didn't make it to the list, but those dumbfucks did who don't even know what Cloud technology is or how it works. Neither they could do any average level program, nor have the communication skills. HOW?! HOW THEM AND NOT ME? Life is very unfair sometimes. I couldn't sleep at night.

PS: If you made this far, thank you for reading this rant (and sorry for it being so long). Makes it better to be able to share with someone. If you could, then please guide me (online resources/recommendations) to be better at competitive programming, or help me enhance my resume/linkedin or if you could refer me for an entry level position at your organisation, I would eternally be grateful. Thank you once again. And sorry for the long rant.

Hey there! I am pretty new but old to the community xD. Let me explain and introduce myself.

The post might be a little longer, depending on my inspiration, read it at your own risk ;)

I am here on devRant for almost a year now but, this is my first post. I wasn't active until a week ago or so. Why? Well, at the time, I didn't find posts interesting enough to keep me from work or school. I must addmit I was either stupid or confused (not uncommon for me).

Well, I am high school student who, when not prepearing for an entrance exam for faculty, is learning and doing indie game developent with my cousin's support.

Even though I was intermediate gamer whan I was younger, passionate but not addicted, I didn't even think about getting into game development until my cousin showed me one secific game and told me a story about it. Let's stop here and let me tell you why I tagged this rant with wk88.

I've already mentioned my cousin, he's my wk88 trouble. Why? I'll tell you only one thing. He studies CS at University of Cambridge, UK. He earned the scholarship by competing and earning multiple medals in programming in International Olympiad in Informatics. And here I am struggling with ******* trigonometric identities. But nvm, let's move on.

I told you about the game but didn't actually tell you the title and who developed it. So, my inspiration for getting into game development was Alexander Bruce , guy who designed Antichamber. If you haven't heard of it before/tried it yet, give it a shot, you probably won't be disappointed of you like fucking with your brain.

Here're some facts:
- Started learning programming at the age of 12, thought by my brother using Free Pascal in Lazarus.
- Have been learning C++ for 4 years and C# for 3, both at the same time.
- While learning these two, started building .NET based back-end and doing SQL stuff; failed to finish it, gave up after I realised I needed some advanced front-end skills, which I didn't want to learn, to implement a lot of things I wanted.
- Played a piano since I was 11 and been playing around with music production recently.

Here I am now, learning Blender and hoping that one day I will publish the game I've been developing for past year and a half.

Hope you didn't waste your time reading this. I will try to keep you up with things I experience durning future development.

Cheers! 🍻

Xpost from /r/sysadmin:
I occasionally see posts from people who seem like they want to spend every waking hour of every waking minute working on home lab stuff and studying for certs.

If you do this, you're missing out on life which you will regret later, but even if you don't care about missing out on life, it actually is hurting your career.

Being well rounded helps you interact with others at work in a number of ways. It makes you less one dimensional as "the computers guy" and it also gives you topics to discuss with people. If you know how to cook, or brew beer, or bake bread you end up using a lot of your technical and troubleshooting skills. Biking long distancing and learning how to fix your bike helps with your troubleshooting skills too. You learn to look at things from other angles.

Reading novels or writing poetry or making art work also helps because it exercises your brain. Woodworking or metal working involve a lot of skills that'd help your IT career including project planning and measuring and budgeting for each project. Working on cars or motorcycles would be similar. You just have to do SOMETHING.

I have a member of my team who literally has nothing going on in his life other than studying for certs. No friends, no hobbies, and he basically eats nothing but McDonalds and frozen dinners because even making a meal takes time away from his studying. He thinks means he's dedicated and will experience great career success.

But instead he has nothing to talk to anyone about, and when I say nothing, I mean literally nothing. It's borderline terrifying. Even if he was into comic books and video games it might help, which might help him relate to SOME of the IT staff even if the rest of the people at the company know nothing about it. But he doesn't even have that.

This isn't a solitary field anymore. Even if you truly are "the best" you still have to interact with other people and stay mentally stable enough to not burn out. Even if you know more than everyone else (or think you do) you have to try to broaden your horizons.

Not really a rant but my biggest fuckup that entirely ruined my IT career and future life

> be me 21yo CS student looking for an internship
> looking for help with my friend and sent him my CV to apply to a big corp
> then I lied that I have sent CV to official email {here the fuck up begins}
> after that I got an instant phone call from a friend of him claiming that the CV was sent properly and I am going to visit a company
> I had a review but it was recorded my CV hasn't got precisely specified technologies so interviewer thought I can manage to work as a dev not an intern
> with my shitty communication skills I managed to "work" there 8days, fucked up someone's computer by deleting his Windows and all data he had and installing Ubuntu instead
> then shit got out of control for an intern I talked a lot of bullshit in this Corp they realized I was there an "alien" and I didn't even know what to do so I wanted to sudo rm - rf myself
> unfortunately my parents woke up that morning I decided to sudo rm - rf and and I am now in mental asylum with fucked up people and the Corp knows where am I and I am going to pay for my stupidity and being naive (I didn't even seen the CEO, I didn't have enough information that I really worked there)
> To sum up, being bipolar, naive and irresponsible has brought me to this point in life. Thank you for reading. I don't see a solution, my parents don't believe me and I feel isolated with this fuckup so I decided to share it as a remark for young people starting in IT. For me it already ended too fast.

So this post is going to target an irritating aspect of a specific culture based on observational evidence over the last 20 years, and has reared its hideous face yet again. If you're triggered by that, stop reading here.

I'm flatly fed up with two-faced onshore Desi coworkers. They make up 95% of my colleagues and the following sequence of events has played out repeatedly over the course of my career, consistently, though it's slightly more pronounced in other women for whatever reason :

1. Work with them for years, good relationship, teach them all sorts of skills (which I will do freely for anyone, for any reasons as I view it to be a moral imperative), general lifting up and solid teamwork.
2. They move up in the hierarchy, generally to management, usually project
3. The second they view themselves as higher in the pecking order they start treating me like shit as if we have no history. Rude, commanding, unwilling to share details, obligatory exasperated thank yous if any at all, not interested in anything I have to say even if I'm the noted expert on the subject.

I understand a lot of their etiquette culture, specifically the level of "directness" or politeness they employ is based on the estimated risk of loss in the interaction. I find that disgusting, but I understand that academically. I just can't get my mind around how universal this shiftiness is, as it happens over and over again. It's like human decency and respect go out the window the second they don't feel like they have anything to gain from you. In *my* culture that is the lowest form of behavior a human can exhibit, and it causes me to rage because I can't imagine being so utterly devoid of altruism.

Fuck. It's just so sickening. It's fucking debased, and selfish and greedy and fuck. I can't even, this is one of those things that so irrational my mind can't accept it and I just go around and around on it.

Tl;dr you want to get throat punched? Because that's how you get throat punched. It's definitely getting this person doxxed to USCIS

Spent 2-3 weeks on implementing a new feature, a guy with 10 years of experience jumps in and solves it within 5 days.

*Oh! I forgot to mention, it was his first time working with the framework.

I must say his OOP skills are really good, not sure if this is something you learn by reading books or simply by practice.

I strongly believe that if you have a good understanding of how to build apps with OOP pattern, you'll do a great job in the SW industry.

Tl;Dr - It started as an escape, carried on as fun, then as a way to be lazy, and finally as a way of life. Coding has defined and shaped my entire life from the age of nine.

When I was nine I was playing a game on my ZX spectrum and accidentally knocked the keyboard as I reached over to adjust my TV. Incredibly parts of it actually made a little sense to me and got my curiosity. I spent hours reading through that code, afraid to turn the Spectrum off in case I couldn't get back to it. Weeks later I got hold of a book of example code to copy out to do various things like making patterns on the screen. I was amazed by it. You told it what to do, and it did it! (don't you miss the days when coding worked like that?) I was bitten by the coding bug (excuse the pun) and I'd got it bad! I spent many late nights on that thing, escaping from a difficult home life. People (especially adults) were confusing, and in my experience unpredictable. When you did things wrong they shouted at you and threatened to take you away, or ignored you completely. Code never did that. If you did something wrong, it quietly let you know and often told you exactly what was wrong. It wasn't because of shifting expectations or a change of mood or anything like that. It was just clean logic, simple cause and effect.

I get my first computer a year later: an IBM XT that had been discarded by a company and was fitted with a key on the side to turn it on. With the impressive noise it made it really was like starting an engine. Whole most kids would have played with the games, I spent my time playing with batch scripts and writing very simple text adventures. And discovering what "format c:" does. With some abuse and threatened violence I managed to get windows running on it. Windows 2.1 I think it was.

At 12 I got a Gateway 75 running Windows 95. Over the next few years I do covered many amazing games: ROTT, Doom, Hexen, and so on. Aside from the games themselves, I was fascinated by the way computers could be linked together to play together (this was still early days for the Web and computers networked in a home was very unusual). I also got into making levels for Doom, Heretic, and years later Duke Nukem 3D (pretty sure it was heretic; all I remember is the nightmare of trying to write levels entirely by code!). I enjoyed re-scripting some of the weapons and monsters to behave differently. About this time I also got into HTML (I still call this coding, but not programming), C, and java. I had trouble with C as none of the examples and tutorial code seemed to run properly under a Windows environment. Similar for my very short stint with assembly. At some point I got a TI-83 programmable calculator and started rewriting my old batch script games on it, including one "Gangster Lord" game that had the same mechanics as a lot of the Facebook games that appeared later (do things, earn money, spend money to buy stuff to do more things). Worried about upcoming exams, I also made a number of maths helper apps, including a quadratic equation solver that gave the steps, and a fake calculator reset to smuggle them into my exams. When the day came I panicked and did a proper reset for fear of being caught.

At 18 I was convinced I was going to be a professional coder as I started a degree in Computer Science. Three months later I dropped out after a bunch of lectures teaching what input and output devices were and realising we were only going to be taught Java and no C++. I started a job on the call centre of a big company, but was frustrated with many of the boring and repetitive tasks we had to do. So I put my previous knowledge to use, and quickly learned VBA to automate tasks. It wasn't long before I ended up promoted to Business Analyst where I worked on a great team building small systems in Office, SAS, and a few other tools.

I decided to retrain in psychology, so left the job I was in and started another degree. During my work and placements my skills came in use a number of times to simplify and automate tasks. I finished my degree, then took a job as a teaching assistant while I worked out what I wanted to do next and how to pay for it. Three years later I've ended up IT technican at the school, responsible for the website, teaching a number of Computing lessons each week, and unofficial co-coordinator for Computing as a subject. I also run a team of ten year old Digital Leaders who I am training in online safety and as technical experts; I am hoping to inspire them to a future in coding. In September I'll be starting teacher training with a view to becoming a Computing specialist teacher. Oh, and I'm currently doing a course in Android Development in my free time.

And this all started with an accidental knock on the keyboard of a ZX Spectrum.

You start wondering if the CV you're reading is real when you see: "I have skills with emails and the Internet".

I'm coming off a lengthy staff augmentation assignment awful enough that I feel like I need to be rehabilitated to convince myself that I even want to be a software developer.

They needed someone who does .NET. It turns out what they meant was someone to copy and paste massive amounts of code that their EA calls a "framework." Just copy and paste this entire repo, make a whole ton of tweaks that for whatever reason never make their way back into the "template," and then make a few edits for some specific functionality. And then repeat. And repeat. Over a dozen times.

The code is unbelievable. Everything is stacked into giant classes that inherit from each other. There's no dependency inversion. The classes have default constructors with a comment "for unit testing" and then the "real" code uses a different one.

It's full of projects, classes, and methods with weird names that don't do anything. The class and method names sound like they mean something but don't. So after a dozen times I tried to refactor, and the EA threw a hissy fit. Deleting dead code, reducing three levels of inheritance to a simple class, and renaming stuff to indicate what it does are all violations of "standards." I had to go back to the template and start over.

This guy actually recorded a video of himself giving developers instructions on how to copy and paste his awful code.

Then he randomly invents new "standards." A class that reads messages from a queue and processes them shouldn't process them anymore. It should read them and put them in another queue, and then we add more complication by reading from that queue. The reason? We might want to use the original queue for something else one day. I'm pretty sure rewriting working code to meet requirements no one has is as close as you can get to the opposite of Agile.

I fixed some major bugs during my refactor, and missed one the second time after I started over. So stuff actually broke in production because I took points off the board and "fixed" what worked to add back in dead code, variables that aren't used, etc.

In the process, I asked the EA how he wanted me to do this stuff, because I know that he makes up "standards" on the fly and whatever I do may or may not be what he was imagining. We had a tight deadline and I didn't really have time to guess, read his mind, get it wrong, and start over. So we scheduled an hour for him to show me what he wanted.

He said it would take fifteen minutes. He used the first fifteen insisting that he would not explain what he wanted, and besides he didn't remember how all of the code he wrote worked anyway so I would just have to spend more time studying his masterpiece and stepping through it in the debugger.

Being accountable to my team, I insisted that we needed to spend the scheduled hour on him actually explaining what he wanted. He started yelling and hung up. I had to explain to management that I could figure out how to make his "framework" work, but it would take longer and there was no guarantee that when it was done it would magically converge on whatever he was imagining. We totally blew that deadline.

When the .NET work was done, I got sucked into another part of the same project where they were writing massive 500 line SQL stored procedures that no one could understand. They would write a dozen before sending any to QA, then find out that there was a scenario or two not accounted for, and rewrite them all. And repeat. And repeat. Eventually it consisted of, one again, copying and pasting existing procedures into new ones.

At one point one dev asked me to help him test his procedure. I said sure, tell me the scenarios for which I needed to test. He didn't know. My question was the equivalent of asking, "Tell me what you think your code does," and he couldn't answer it. If the guy who wrote it doesn't know what it does right after he wrote it and you certainly can't tell by reading it, and there's dozens of these procedures, all the same but slightly different, how is anyone ever going to read them in a month or a year? What happens when someone needs to change them? What happens when someone finds another defect, and there are going to be a ton of them?

It's a nightmare. Why interview me with all sorts of questions about my dev skills if the plan is to have me copy and paste stuff and carefully avoid applying anything that I know?

The people are all nice except for their evil XEB (Xenophobe Expert Beginner) EA who has no business writing a line of code, ever, and certainly shouldn't be reviewing it.

I've tried to keep my sanity by answering stackoverflow questions once in a while and sometimes turning evil things I was forced to do into constructive blog posts to which I cannot link to preserve my anonymity. I feel like I've taken a six-month detour from software development to shovel crap. Never again. Lesson learned. Next time they're not interviewing me. I'm interviewing them. I'm a professional.

Reading books, not sure if you can even call it a non-dev activity since it is essential in my opinion but reading improves my programming skills everyday!

As a person who spends 99.99% of his time at home if not at school programming, reading, and watching netflix, what can I do to develop my social skills?

!rant

New years resolutions:

1. Reading all 16 books on my goodreads list
2. Learn Clojure
3. Switch job to a company which appreciates my skills more
4. Be the best dad my son could wish for

**My Resume** : Worked with JavaScript and .NET for the last 3 years ... have an Associates degree...more things

**Recruiter**
You look like you'd be a great fit for this position. We require a Bachelors degree, but we're willing to take 4 years progressive experience in lieu of each year of schooling.

**First**
4 YEARS of experience for EACH YEAR of school?

**Me**
I guess basic reading and math aren't required to be a job recruiter? Man...Only 5 more years and I'll be able to see how my skills as a developer with 8 years of professional experience will go over as an Entry level developer!

Not an actual teacher but definitely the guy who thought me the most: @java9

@java9 is a friend of mine who started the apprenticeship with me, but had serval years more of experience than I did.

At first he helped me get through the first complex tasks.

Luckily we are in the same class at professional school, and he helped me studying a lot.

Because of him I was able to develop my skills rather quickly.

Over the years our relationship developed into a close friendship.

Now we are working together as a team on more than side project and I've learned to love his perfectionism when it comes to code.

It's a pleasure to work with you @java9

Thanks for reading fellow ranter, here is a picture of us sharing a beer as a bonus

Enough!!

There is to much hate in the world already without hating on Windows because you are a Linux user, or vice Versa.

All I'm reading is windows is shit! Linux is for supreme devs.

More to life than hate! Respect each other's skills. Skills are like race all are unique and no one race is superior and don't discriminate because of skills.

I just wanted to get this off my chest.
There we go, that time is finally coming: all of my friends are starting to look for jobs; we are all about to graduate, but i feel no desire to move forward... I wish i had their optimism, but all i feel is terror and panic every time they bring up the topic...

I have no plan, no idea of what might happen, and i don't feel like i am particularly competent in anything: I do not have much to offer to society, surely not in terms of technical skills: i'm a real shitty programmer with the attention span of a goldfish.
I am passionate about a bunch of topics, but i am not competent at them in any meaningful way: I like reading about x86 Assembly or Operating System design, but if you'd ask me to write them i wouldn't be able to really. Its all superficial, i read these things for fun but i never really accomplished anything.

And i know this is all in my head, that as soon as i find anything its probably gonna be fine, i just wish i had the enthusiasm and drive that people around me seem to have, instead of acting like a little bitch :)

The company I work at sends their developers out to other companies to help them work on projects and help them in other ways (advice when communicating to customers of on demand software for example).

While not on a project you are working in house training trainees and interns. Part of that is teaching them to show initiative and treating them as full developers. The 30 interns all discussed a git flow and code format.
During the third sprint (two weeks sprints) a team messaged me if I wanted to check their merge request for the sprint.

It took me a glance at the first file to know they didnt do any review themselves. I used my flywheel to check all their changes and without being able to read the code I saw indentation was all over the place, inconsistent bracket placements etc. I let them know I wouldnt check their code until it was according to their own standards.
Two days later I got the message to check it again. At first glance the indentation was fine so I started reading the code. Every single thing was hardcoded, not made to support mobile (or any resolution other than 1920×1080).
A week later they improved it and still not good. Gave them a few pointers like I would for any colleague and off they went to fix things. The code became worse and indentation was all over the place.

I told them the next time it shouldnt be a quick glance to be able to reject it again. By this time other teams came to me asking why it wasnt merged yet and I explained it to them. One of the teams couldnt do anything u til this was merged so I told them to implement it themselves. I was surprised that 4 teams came to me asking about a merge request, that was every team except the team whose pull request it was.

4 weeks after the intitial sprint the other team made a merge request and I had three small comments and then an hour later it was merged.

The other team messaged me why their merge request did went through (still havent seen any of their team in person, Im sitting 10 meters away from them behind a wall)
They also said that it was easier for them because they started from scratch. Thats when I called them in to discuss it all and if they were not interns but full time developers they would have been fired. I told them communication is key and that if you dont understand something you come in person to ask about it. They all knew I like teaching and have the patience to explain a single thing ten times, but the initiative should be theirs.

One of the team members is my current coworker and he learned his lesson by that. The others stopped with their study and started doing something completely else.

TL;DR
Merge request is open for 4 weeks, in the end another team started from scratch and finished it within a week. The original team didnt ask me questions or come to me in person, where other teams did.

DISCLAIMER: some of you might find it harsh, but in our experience it works the best for teaching and we know when people don't dare to ask questions and we help them in that too. It's all about the soft skills at our company.

Rant r = new Rant(Rant.TEAM_PROBLEM);

Three months ago, a senior, one year older than me, decided to join me in doing startups. He said he's good at finance stuff (his parents are fund managers), and he is interested in startups just like I am. He treated me very nicely, so I gladly accepted him.

I'm currently working on many projects, and some of them won me quite a few awards, most notably on the national competition. I also got invited into startup incubator programs, met some awesome people and offered free scholarships at universities in my country.

He frankly said he joined because he wanted to learn about startups and have those "privileges" too, and I'm cool with that.

Anyway, the problem is that I'm the one doing all the work. He's really nice, doesn't claim anything whatsoever, but the thing is he doesn't have any skills whatsoever except soft skills like communicating. So, I'm horribly tired from working alone.

My tasks mostly involves full-stack development, such as planning the specs, designing and developing frontend for mobile apps and progressive webapps, developing microservices for the backend, up to deploying and maintaining the servers. It's a lot of work for a single person to handle in such a short timeframe.

Not only that, but I'm also the one handling the business/marketing part, albeit I'm still learning. From doing paperworks, pitches, business models, up to creating advertising materials for the product.

I'm obviously not the smart ones like the people out there, but I keep focusing on improving my skills.

So, he said he could help me, and I let him try. What did you think he did?

He made pitch decks using default fucking PowerPoint themes, shooted a demo video with his phone cam in 320p potato resolution and expect me to "add some effects", gives me loads of requirements when all we needed was a simple feature, copying and pasting prior documents in my paperworks which doesn't make any fucking sense at all, and quite a lot more.

Also, he said I should stay in the developer zone only while he maintains the business, whilist he obviously can't do much in the business part either. Seriously...?

I'm okay with his lack of experience, considering he's nice and all, unlike the other business guys I've met in the previous rants. However, I keep questioning myself why he is here in the first place when I'm the one doing everything anyway.

What should I do? Maybe just keep him and recruit more experienced people to join us, as he's not that much of a burden? What do you devRanters think?

Thanks for reading, fellow devRanters! 😀

If hiring managers really want to hire based on skill, what they should be doing is testing for one thing:

The ability to take a specification, written in general language, notice deficiency, communicate with the 'client' (manager) to hash out what needs done, and the (explicit) ability to read documentation on libraries or tooling outside the dev's core skillset.

If a dev can read a spec, talk to a client to work out whats lacking, and then identify what they need to know and where to find it, thats 90% of the skills they need from what I can see.

tl;dr version of it, is they should be explicit about the requirements for reading/implementing specs and finding the correct documentation.
Something along the lines of
"can you form your letters? Are you able to follow instructions on the back of a cake box? Then there may be a position waiting for you!"

If someone asks you something that's easily google-able, they are probably just trying to break the ice with you.

Been reading a few books this year on people skills. We write code to make the lives of people better. To do that we need to understand and emphasise with each other

This isn't a funny rant or story. It's one of becoming increasingly unsure of the career choices I've made the path they've led me down. And it's written with terrible punctuation and grammar, because it's a cathartic post. I swear I'm a better writer than this.

The highlights:
- I left a low-paying incredibly stable job with room to grow (think specialized office worker at a uni) to become a QA tester at a AAA game studio, after growing bored with the job and letting my productivity and sometimes even attendance slip
- I left AAA studio after having been promoted through the ranks to leading an embedded test tools development team where we automated testing the game (we got to create bots, basically!) and the database, and building some of the most requested tools internally to the company; but we were paid as if we were QA testers, not engineers, and were told that wouldn't change; rather than move over or up, I moved out to a better paying, less fabulous web and tools development job for a no-name company
- No-name company offered one or two days remote, was salaried, and close to home. CTO was a fan of long lunches and Quake 3 Arena 1-2 hours at the end of every day. CTO position was removed, I got a lot of his responsibilities, none of his pay, and started freelancing to learn new skills rather than deal with the CFO being my boss.
- Went to work as a freelancer for an email marketing SaaS provider my previous job had used. Made loads of money, dealt with an old, crappy code base, an old, cranky senior dev, and an owner who ran around like the world was on fire 24/7; but I worked without pants, bought a car, a house, had a kid, etc;

Now during ALL of this, I was teaching game dev as an adjunct at my former uni. This past fall, I went full time as a professor in game dev. I took a huge pay cut, but got a steady schedule (semester to semester anyway) and great benefits. I for once chose what I thought was the job I wanted over more money and something that was just "different". And honestly, I've regretted it so much. My peer / diagonally above me coworker feels untrustworthy half the time and teaches the majority of the programming courses when he's a designer and I've been the game programming professor for 8 years (I also teach non-game programming courses, but those just got folded into the games program...); I hate full-time uni politics; I'm struggling with money for my family; and I am in the car all the time it feels like. I could probably go back to my last job, which had some benefits, but nowhere near as good; my wife doesn't want me back to working in the house all the time because that was a struggle unto itself once we had a kid (for all of us, in different ways); and I have now less than 24 hours to tell my university I want to not pursue longer term contracts for full-time and go back to adjunct next Fall (or walk away entirely), or risk burning a bridge (we are reviewing applicants for next year tomorrow, including my own) by bailing out mid-application process.

I'm not sure I'm asking for advice. I'm really just ranting, I guess. Some people I know would kill to have the opportunities I have. I just feel like each job choice led me further away from a job I liked, towards more money, which was a tradeoff that worked out mostly, but now I feel like I don't have either, and I'm trapped due to healthcare and 401k and such. Sure, I like working more with my students and have been able to really support them in their endeavors this semester, but... that's their lives. Not mine. The wife thinks I should stay at the university and we'll figure out money eventually (we are literally sinking into debt, it's not going well at all), while most people think I should leave, make money, and figure out the happiness factor once my finances are back on track and the kid is old enough to be in school.

And I have less than 24 hours it feels like to make a momentous decision.

Yay. Thanks for reading :)

!rant
Warning : This rant is long and is a rant asking for help and suggestions. If you will read and dont leave any comments, please go search other rants. Thanks.
-----------------------------------
Hi, fellow ranters. In our community, we have a tech class where teens (teens here mean 14yo -15yo) come to learn computer stuffs. Teens here are selected by a test and an interview. There are some teens who are f***ing awesome. One of them are proficient in scratch. (yeah, the orange cat) Another is awesome at PhotoShop, and the other loves windows xp. The teacher uses Microsoft Visual C++ IDE made in the 1990s. The kid sitting to my left made flappy bird with gamemaker. About 10 to 11 teens doesnt know what ctrl+alt+del does in windows and never did programming before... 3 among them always brings coke and oreos and eats super loudly. CRACK! And I bet no one knows about git.
Ok. Enough for the awesome teens. Now what we learn.
We learn C! Yes, C. We learned for, if else, switch and all those stuffs, then learned variables, which made other students who never did programming before be (―,.―).
Next class we will learn about functions in 3 hours. Then array and pointer in 3 hours. Thats it for c programming. Then we do some unnecessary stuffs and time for the finals.
We need to make a project with up to 4 teens as one team. Now I am asking you awesome ranters to suggest some projects for about 4 pros and 16 noobs can do. 10 hours are given in class and we can do in other times by ourselves in home. What should we do? I bet many of them will say to make ascii art in c which is dull and I have no thoughts of doing that.
Any thoughts will be appreciated.
Thank you for reading.
To see my skills, go to my profile page.
| Comments below
v

I need to rant about life decisions, and choosing a dev career probably too early. Not extremely development related, but it's the life of a developer.

TL;DR: I tried a new thing and that thing is now my thing. The new thing is way more work than my old thing but way more rewarding & exciting. Try new things.

I taught myself to program when I was a kid (11 or 12 years old), and since then I have always been absolutely sure that I wanted to be a games programmer. I took classes in high school and college with that aim, and chose a games programming degree. Everything was so simple, nail the degree, get a job programming something, and take the first games job that I could and go from there.

I have always had random side hobbies that I liked to teach myself, just like programming. And in uni I decided that I wanted to learn another language (natural, not programming) because growing up in England meant that I only learned English and was rarely exposed to anything else. The idea of knowing another fascinated me.

So I dabbled in a few different languages, tried to find a culture that seemed to fit my style and attitude to life and others, and eventually found myself learning Korean. That quickly became something I was doing every single day, and I decided I needed to go to Korea and see what life there could be like.

I found out that my university offered a free summer school program for a couple of weeks, all I had to pay for was the flights. So a few months later I was there and it was literally the best thing I'd done in my life to that point. I'd found two things that made me feel even better than the idea of becoming the games programmer I'd always wanted to be. Travelling and using my other language to communicate with people that I couldn't in English. At that point I was still just a beginner, but even the simple conversations with people who couldn't speak English felt awesome.

So when I returned home, I found that that trip had completely thrown a spanner into my life plan. All I could think about after that was improving my language skills and going back there for as long as possible. Who knows what to do.

I did exactly that. I studied harder than I'd ever studied for anything and left the next year to go and study in Korea, now with intermediate language skills, everyday conversations no longer being a problem at all.

Now I live here, I will be here for the next year and I have to return to England for one year to finish my degree. Then instead of having my simple plan of becoming a developer, I can think of nothing I want to do less than just stay in England doing the same job every day, nothing to do with language. I need to be at least travelling to Korea, and using my language skills in at least some way.

The current WIP plan is to take intensive language classes here (from next week, every single weekday), build awesome dev side projects and contribute to open source stuff. Then try to build a life of freelance translation/interpreting/language teaching and software development (maybe here, maybe Korea).

So the point of this rant is that before, I had a solid plan. Now I am sat in my bed in Korea writing this, thinking about how I have almost no idea how I'm going to build the life that I want. And yet somehow, the uncertainty makes this so much more exciting and fulfilling. There's a lot more worrying, planning and deciding to do. But I think the fact that I completely changed my life goals just through a small decision one day to satisfy a curiosity is a huge life lesson for me. And maybe reading this will help other people decide to just try doing something different for once, and see if your life plan holds up.

If it does, never stop trying new things. If it doesn't (like mine), then you now know that you've found something that you love as much as or even more that your plan before. Something that you might have lived your whole life never finding.

I don't expect many people to read this all, but writing it here has been very cathartic for me, and it's still a rant because now I have so much more work and planning to do. But it's the good kind of work.

Things aren't so simple now, but they're way more worth it.

What you're about to read is an horror story based on real facts.
Our story begins one week ago, when a dev who calls himself "Arfmann" (what a loser, the f* means arfmann?) decided to take his dev skills to another level.

He always has been scared of databases. He made really bad dream about them. Like, they were screaming at him "SELECT useUs FROM database" while he was crying in some shared preferences noises.

A week ago, he decided to overcome his fear. He learned the basics of SQL. Everything was going well. Until, he decided to implement it on Flutter. A Google's technology.

At first, he decided to appeal to documentation. Went on Flutter web site. Flutter documentation. Sqflite documentation. Started reading. Started doing tests with the code written by Google's engineer.

Everything was fucked up. Dozens of errors, the documentation started to blow up and his PC went on fire, due to Android Studio.

He used a sample project made by Google's engineer. "Maybe if use directly their code it will work. Maybe I was the problem". He wasn't.

The whole documentation was wrong, every single line of code was a spaghetti code (yes, every single line was an entire spaghetti code). Everything was put in the main. If you wanted to try to keep things organized, you would end up punched and beaten up from the code itself. It would become a sentient entity that will beat you the fuck up.

Really scary.

So we've had a new guy on our team for over 6 months now... Been training him up doing shadowing.... Training courses... Study time... The works...

He didn't have the specific skills for our team but had 2 degrees, lectured at uni... Seems VERY smart......

Yet he still has barely grasped the basics..... When experienced people talk about challenges they've had he tries to suggest what they do... Constantly raising 'problems' with ways of working but offers no solutions and never collaborates on how we can fix it......

He avoids doing practical learning and thinks he can learn the job from reading docs... .. Sigh....

Gone almost as far as doing daily check ups on what he's actually doing to make sure he's progressing..... Tough one to crack!

The guy who leads the Objective Programming classes/labs told us that we have to make a game or an app to pass this semester.

I was so hyped, I've instantly started reading up on creating a 2D engine in C++ (which I don't like as much as C# but that was his conditions).

..as soon as I've created base for the engine, he said that the first version has to be console based.. so I'm like - okay, how do I show my 2D _graphical_ engine in a console?
So I came up with showing basic vector maths like movement towards a bearing angle and whatnot.

..now I've been pointed out that we are supposed to make a documentation, except it's supposed to contain info on ALL libraries and ALL classes our project will have.. which is insane, how can one predict what he'll need to accomplish the task? You can only know the half of the things you'll need, unless the project is way too simple.

I'm just plain annoyed, because this whole 'wow, I can showoff my mad skills' turned into 'wow, I have to do shit the tedious way and I'm already crying that I've picked a 2D engine and not a simpleton game like crosses and circles.

Below is a transcript from work Slack today. Only the names and some code are changed. It ended up causing a bit of drama. DevRanters, what do you take from this?

---

Delivery Lead:
Hey Gang. What's the blocker for FEATURE-123?

Dev1:
FEATURE-122 crashed on iOS app when viewing Feature Introduction page.

Teach Lead:
I've talked about this with Dev1 on a side channel.
And diagnosed the stack trace.
It looks like there is/was some bad handling of a List in the Feature Introduction view logic.
But this is confined to changes that Dev2 is still working on.
(It's not present in master)
Dev2, what's your current position on this?

Dev2:
I have tested at my end with Dev1 but it seems to be working fine

Tech Lead:
There is a race condition related to the use of someList.first()
My guess is that theres a Flow of those lists defined, with an initial value of emptyList
And that on your machine, that Flow is updating with a new value quickly enough that it doesn't matter.
But on Dev1's, for whatever reason, it doesn't get there in time, hits the empty list and falls over.
The logic that's performing the first() needs to gracefully handle empty lists as well.

Dev2:
Where is that logic called?

Tech Lead:
Here's the stack trace Dev1 provided in our conversation earlier:
Caused by: kotlin.NoSuchElementException: List is empty.
...
at 3 iosApp 0x00000000 kfun:kotlin.NoSuchElementException#<init>(kotlin.String?){} + 00
at 4 iosApp 0x0000000 kfun:kotlin.collections#first@kotlin.collections.List<0:0>(){0§<kotlin.Any?>}0:0 + 000
...
at 9 iosApp 0x0000000 kfun:kotlin.coroutines.native.internal.BaseContinuationImpl#resumeWith(kotlin.Result<kotlin.Any?>){} + 0000

This line:
kfun:kotlin.collections#first@kotlin.collections.List<0:0>()
...says that it's first() being called on an empty list.

Dev1:
FYI: Dev3/Dev4/myself are seeing the same issue with the same stack-trace above.

Tech Lead:
So Dev2, have you introduced such a call?
Because I checked master branch and there isn't one, in that version of the file.
Ok, I'll check your working branch Dev2
...
Yes you have here:
var processed1 = someList.first()
var processed2 = someList.first()
...
Lines 123, 124.
Solution looks really straightforward guys.

Dev2:
Okay, I will fix that and push the change

Tech Lead:
Check if someList is empty and allow for generating / handling null processedValues in the view.

Now; I'm going to be straight with you here.
This issue has been discussed over several hours today.
I expect that either one of you could have gone through the process I did in the last 10 minutes above, and resolved it in the same way :point_up:

Dev2:
I went on a break and it's not reproducible on my machine

Tech Lead:
I didn't reproduce it on mine either.

Dev1:
Dev2 and myself are now on sharing screen to sort this issue out. Hope to update back later.

Tech Lead:
<Screen shot of diff with changed code>
:point_up: That change should do it.

Dev2:
Already have pushed the change.

Tech Lead:
...just seen it, is good - same approach :ok_hand:
Dev1 please let us know when tested on your machine.

Dev1:
That does it. It fixes the issues. Thank you, Dev2. I will pick it off from here.

Tech Lead:
Glad to hear it guys.

Dev1:
I have to say this that it is not because we are not working on the issue - Dev2 and myself (together with Dev3/Dev4) have been on this issue all this morning. It just difficult to connect the dot when it wasn't reproducable on Dev2's machine. I brought the issue up because I wanted to switch to working on other tickets while waiting for this to resolve. Still thank you largely for Dev2's work and your keen eyes that spot and resolve the issue quickly.

Tech Lead:
Noted Dev1.
I think the take-away has to be to read the stack-trace carefully... don't worry - we've all been guilty of not reading the error in full, at some point.
The stack trace said that the 'first' element is being referenced from an empty list - that's just logically impossible, right?
Looking for that call to first, we saw it wasn't in the code before, and is after (two of them, in fact).
So then we ask ourselves, how can we deal with an empty list - and then solution almost presents itself.
It didn't really take reproduction of the error to resolve.
Maybe working with a new tech stack creates an anxiety that every issue faced will have a complex solution related to that stack; but I think you'll agree, this particular issue really just required a deep breath and your trusty 'debugging skills 101'... don't lose them! :smiling_face:

I hate React. I keep reading that people have problem of grasping it, but that's not the case for me. I get it, I understand it, but I hate with passion HOW it's done knowing how nice it's done elsewhere. What really triggers me is how ugly it looks, both from architecture and code level. To me it really say a lot when even code shown in documentation looks ugly, and while reading it you ask ourself constantly "why it's done this way?". When I read React being called an "elegant" solution something explodes in me. Did you saw Svelte? Vue? Damn, even Alpine.js?
I just cannot how overengineered this API is. Even doing simplest things there produces so much junk code written only because this is what library requires. Why? I feel like working with it is a punishment.
And scalability and maintainability? I've never seen large-scale projects more messed up than those wrote with React. And yes, you can blame teams working on them for lack of skills, but it is the library which encourages or not good practices also, and I've never seen such bad situation with other libraries/frameworks.

I absolutely hate software to the point where I started converting from sysadmin to becoming more like a dev. That way I could just write my own implementations at will. Easier said than done, that's for sure. And it goes both ways.

I think that in order to be a good dev, you need these skills the most:
- Problem solving skills
- Creativity, you're making stuff
- Logical reasoning
- Connecting the dots
- Reading complex documentation
- Breaking down said documentation
- A strong desire to create order and patterns
- ...

If you don't have the above, you may still be able to become a dev.. but it would be harder for sure, and in some cases acceptance will be lower (seriously, learn to Google!)

One thing I don't think you need in development is mathematics. Sure there's a correlation between it and logic reasoning, but you're not solving big mathematical monsters here. At most you'd probably be dealing with arrays and loops (well.. program logic).

Also, written and spoken English! The language of the internet must be known. If it's not your first language, learn it. All the good (and crucial) documentation out there is in English after all.

One final thing would be security in my opinion, since you're releasing your application to the internet and may even run certain services, and deal with a lot of user data. Making those things secure takes some effort and knowledge on security, but it's so worth it. At the most basic level, it requires a certain mindset: "how would I break this thing I just made?"

So our company wants us to start learning/sharpening our Python skills for work. We signed up for CodeWars and ran through our first Kata today. I'm excited to learn, but I don't have any actual experience with anything but HTML/CSS and super basic JS for just things like animation... I feel like such a fucking moron trying to work through this Kata. Because our manager wanted us to only spend like 15-20 minutes on it. I spent over 4 hours trying to figure out the right place to even start, even with reading documentation and trying to find similar examples online and after 4 headsmashingly long hours I couldn't even get an idea of how to tackle the problem.

Watching python videos to try and figure this out...

Reading through one of my posts I’ve realized how much ego programmers can actually have. Guys, some of you have already mastered or grasped more than just the foundations of the industry standard languages, as well as developed a very solid intuition behind some design patterns and a solid understanding of some frameworks and libraries, say NumPy, say React... we get it.

You don’t have to be such condescending assholes and be offended by some of the jokes we, programming beginners, make to release stress or just to have fun.

You already have some amazing developer and engineering skills. Do not ruin it with such a detrimental attitude; I make this post because I myself have made this mistake, and I still do to this day. But if what I’ve felt reading your comments is what non-programming people feel when around me, I wouldn’t be surprised if I found that some people hated me or just wanted to kill me.

I don’t know if this will get downvot’d or if more people think like this. But I needed to share this, even just as a reflection of my very own attitude.

Thank you for your time,

D.

whining

So I'm sitting here, working my ass off developing something far above my current skills.

On the opposite side of the table sits relatively new guy, working as a part of support "department". Relatively new means that he's with the company for around 1 month.

The guy started speaking to me. I took off my headphones and listened, while still reading code. He told me about how he'll have to carry out the recruitment process for the support department today. And that he was told to present himself as a leader of the department, blah blah blah.

To be honest, I stopped listening at that moment. I got really pissed. And it's not because of the absolute lack of the professionalism of the company (srsly, make a new guy do recruitment work?). It's because I asked boss to get someone to help me half a year ago. He did employ around 3 new support people (4th today). But no one for me.

And he has the balls to tell me that I NEED to work harder to make it for deadline that he imposed. That he won't employ anyone new for me because new people could stole his "idea". Because MAYBE in a month one guy, a junior like me, will come back (he's on a break to finish his master thesis).

Product I'm working on is probably the main reason other companies are even buying the system he's reselling. As a student I'm working only half-time, so those deadlines are almost impossible.

I wonder how he'll manage if I'll get accepted for the work I'm currently applying.

Perhaps one of the most important things I will ever learn in life is how powerful regularity is. Read up on a topic once? Understand nothing? Read more random shit on it. Keep reading. And then stare in awe as things fall into place.

I'm writing this out not because people don't know this. Almost everyone knows this. But it's nice to be reminded of it. It's nice to be reminded that learning new things and honing bew skills is never easy. It's nice to be reminded that there's great knowledge and skills waiting to be learned.

This is not meant as motivation so much as it is meant as a reminder. Our colleagues may be garbage. Our clients may be garbage. Our bosses, the interns, the new dev, and almost certainly ourselves, are almost always garbage.

But if you've learned 1-2 new things today, the day wasn't garbage.

I'm just learning move semantics...

I brought this up before, but what’s with these claims of getting a job after learning to code for a few months? Can this profession be learned that quickly? Am I just dumb for taking years to get my degrees and land a great paying development job and gaining skills and experience to become proficient? My self esteem takes a huge hit after reading these things but what they leave out is whether these jobs are internships, how much they were paid, where they worked etc.

Sorry, just a little incoherent and cranky bc i slept for just a few hours due to a toothache. I’m not blaming these people at all, I’m just kinda questioning my abilities atm

Ok, so I need some clarity from you good folk, please.

My lead developer is also my main mentor, as I am still very much a junior. He carved out most of his career in PHP, but due to his curious/hands-on personality, he has become proficient with Golang, Docker, Javascript, HTML/CSS.

We have had a number of chats about what I am best focusing on, both personally and related to work, and he makes quite a compelling case for the "learn as many things as possible; this is what makes you truly valuable" school of thought. Trouble is, this is in direct contrast to what I was taught by my previously esteemed mentor, Gordon Zhu from watchandcode.com. "Watch and Code is about the core skills that all great developers possess. These skills are incredibly important but sound boring and forgettable. They’re things like reading code, consistency and style, debugging, refactoring, and test-driven development. If I could distill Watch and Code to one skill, it would be the ability to take any codebase and rip it apart. And the most important component of that ability is being able to read code."

As you can see, Gordon always emphasised language neutrality, mastering the fundamentals, and going deep rather than wide. He has a ruthlessly high barrier of entry for learning new skills, which is basically "learn something when you have no other option but to learn it".

His approach served me well for my deep dive into Javascript, my first language. It is still the one I know the best and enjoy using the most, despite having written programs in PHP, Ruby, Golang and C# since then. I have picked up quite a lot about different build pipelines, development environments and general web development as a result of exposure to these other things, so it isn't a waste of time.

But I am starting to go a bit mad. I focus almost exclusively on quite data intensive UI development with Vue.js in my day job, although there is an expectation I will help with porting an app to .NET Core 3 in a few months. .NET is rather huge from what I have seen so far, and I am seriously craving a sense of focus. My intuition says I am happiest on the front end, and that focusing on becoming a skilled Javascript engineer is where I will get the biggest returns in mastery, pay and also LIFE BALANCE/WELLBEING...

Any thoughts, people? I would be interested to hear peoples experiences regarding depth vs breadth when it comes to the real world.

You know something's truly off when you're being challenged for all the wrong reasons. When all it seems you ever do is apply a band-aid every time instead of making the time to fix it properly and for good. Or when the people who should be making your work easier to do instead suggest new tools and features to integrate into your workflow or project because they plug the holes in their management process and can ignore the leaks for the time being.

I need to push myself out of this place and ramp up my skills and update my personal projects so I can prove myself capable and move on to a better employer. Because I'm starting to hate the stopgap short-term approach that keeps getting shoehorned into our work, and only proceeds to make us look bad even if it's the whims of our bosses causing it in the first place.

Thanks for reading.

Right now, I'm doubting my reading skills.

I'm doing a feature acceptance presentation and half way through they're like "did you handle cases A, B and C?"

No.

Fuck.

Now it's got to be rushed in ...
And all because I can't read the spiderweb of requirement docs

Reading code takes time!

Everytime I read:
"var" or "auto" Add: 10s
- Just use the type

Everytime I read:
if(Expression1 && Expression() ? GetNumber() : 0 > 0) Add: 30s
- Just write two if statements or create two bools the line above.

Everytime I read:
delegate = () => {} Add another 5 minutes of reading time.
- Just write a separate function for it. It helps with searching and understand what it does

Please code like the person that needs to check your code or change it just knows basic coding skills and logics.

I do know all these concepts I just never use them because it makes the code unreadable. hard to follow, mistakes that can happen everywhere. difficult to search.

And it frustrates that I need to read 10 extra lines to understand code flow or hover my mouse in an IDE to figure out what type object it is.

It's properly just me... I just like clean readable code. that is logical and failsafe and strict and deterministic with its behavior

I'm a tiny bit happy today.
Recently I've been noticing that I'm developing a tolerance for deeply crowded spaces. I don't know if the AC/DC concert was an effective shock therapy or something.

I'm not at the point where I can comfortably head outside into town by myself yet, but I have a feeling that it's not going to be too long until I can.
Maybe I can even find some joy in "being under people".

Maybe make some contacts, friends, whatever.
The biggest challenge will probably be getting over my, I guess "crippling" isn't the right word, but close-ish to it, self-conscious.
The worst thing is that as of yet, I have no idea why I'm still like that.
I think I know the root cause, but that's not something relevant right now.

Hell, I go out with friends, guys and girls, and eventually it goes like:
>"How come you are not dating someone?"
>"Can't really. Can't go out and fine someone, also I think I'm not good-looking enough."
>"Bullshit, you look awesome."

That's coming from close friends, hence why I don't believe it's just some "oh, he'll feel better if I compliment him" shite.
I somehow am unable to gain self worth from compliments.

[...]

In other news, I got a certificate at the FernUni Hagen for a course in IT project management.
Also, my programming and solution finding/problem solving skills are improving noticeable. I think.
I'm not in Uni or anything, but I feel like I'm getting more competent/professional in my development activities at work.

Contrary to what I stated above, I can gain self worth from good work done.
...which worries me, because I am afraid that eventually I'll only be able to feel good after having worked myself to the metaphorical bone.

In job college, I talk to my classmates.
Turns out, everybody is mostly sitting on their ass doing fuck all at work. They are telling me that I'm a workaholic.
I think that I'm either going mad, or that they are lazy fuckers.

From Wednesday to Thursday evening, three colleagues and I went to the CAS Partner Preview Day & CAS Customer Centricity Forum in Karlsruhe. Lots of talks (mostly boasting about themselves), some workshops and a lot of "networking opportunities".
Stuff which I mostly consider bullshit, but I never would've figured how effective it is to put on a smile and feign interest in things.
Some of that feigned interest turned into actual interest and we "networked" for hours.
It was a good training for social interactions outside my direct comfort zone.

Thank you for reading the ramdump of my mind.
$./felix
Segmentation Fault
Core dumped

I failed at university, spent too long there without ever graduating. I learned a lot through self-study, though. The only company I worked at was an arrangement with a friend whose company needed people, so I stepped in, but eventually I deserted the job after the company went out of money and I went two months straight working without getting paid. Now I feel apprehensive of putting that job experience in my resume because I didn't come out of it in good terms with the company. I have many unfinished projects but keep them private on GitHub because I feel like the code is too bad to show off. How do I even get a job, now? Should I just quit the industry altogether? Aaaaaaaaaaaaa

Right now I'm just self-studying some things I had wanted to do since college (namely computer graphics and trying to build a game engine) but never actually got to study formally because I kept failing at the prerequisite courses because I always kept distracting myself from my studies and just not putting enough effort. Anyway, I'm willing to listen to your advice and your judgment alike. I feel somewhat confident that I can actually do a good job, but I also don't feel confident enough to apply for jobs since I always feel like my skills are lacking. I know about impostor syndrome, but at the core of it is the matter: is this impostor's syndrome, or am I in fact *actually* consistently bad and incompetent? Rationally speaking I tend to feel like the latter, yet I know the only thing I can do is to try and be better. I guess.

Anyway, completely unstructured thing, just me venting off my frustration and desperation in a place where at least people will read it and possibly offer some advice. Thank you for reading this far.

Did I suffer through 2023? Hell yes! Fuck 2023! A LOT of doubt, anxiety, thinking that I live wrong somehow.

Yet, I’m completely satisfied with the results of 2023, with what I was able to accomplish. It means I do, in fact, live my life right. If I carry on doing what I do, I’ll be getting what I get. Here’s what happened to me in 2023:
- Cat!
- No more sugar
- No more smoking
- First time reading paper books in 15 years
- Made me a new website (miloi.am/engine) that, for the first time in my life, isn’t about me as a job candidate, but about me as a person.
- SENT MY DEVRANT LINK to my CEO! Dreaded this coming out for YEARS. Finally did it. He read my posts, told me I’m free to be who I am, told me he already knows me well, that he wasn’t surprised, and overall didn’t care much.
- New name, new pronouns
- Learned how to cook: soups, pancakes, falafel, other popular dishes. Most importantly, now when I go through the store, I’m not afraid of thinking about cooking. I look at something, and I know how to cook it, more or less.
- Found a good psychiatrist, got properly diagnosed, got properly prescribed
- Made a FIRE architecture at my work
- Conceived (and partly implemented) four monetizable side projects (that I can’t monetize yet because of my passport situation)
- Several VERY important insights that completely changed who I am. Several super crucial self-therapy skills.

Let’s see what happens in 2024 😛

What skills? 😂 Jokes aside, a few situations cause me to question myself, one is reading rants on devRant.

I always start questioning myself when I see others code, it inspires me but sometimes also makes me question my ability.

Last thing that often makes me question myself is reviewing all these requirements for jobs.

First and foremost, students should be carefully taught the logic and mentality behind programming. Most of the time I see that the introductory programming courses waste so much energy in teaching the language itself. So students kinda just get fucked cause many people end up ending the course without having actually gained the "programming perspective".
Stop teaching pointers and lambdas and even leave the object oriented stiff till later. If a student doesn't know why we use a For loop then how can they learn anything else.
I believe once that thing in your brain clicks about programming, everything goes smooth from there... kinda :P

Second of all, and this pertains mainly to the engineering and science disciplines.
We need a fundamental and strong mathematical foundation. And no I don't mean taking fucking double integrals. Teach us Linear Algebra, Graph theory, the properties of matrices, and Probability theory.
One of the things I suffered from most and regret in university is having a weak foundation in math and having to spend more time catching myself up to speed.
It's so annoying reading a paper on a new algorithm or method and feeling like an idiot because I can't understand what magic these people did.

Numerical Methods...
Ok this is more deeper, maybe a 2nd year course.
But this is something we take for granted.
Computers don't magically add and subtract and multiply.
They fuck up.
And it'll bite you in the ass if you're not even aware that the computer we all love so much isn't as perfect as we think

Some hardware knowledge.
Probably a basic embedded systems course with arduinos
just so you can get a feel for how our beautiful software actually makes those electrons go weeeeeeeee

And finally
Practice practice
Projects projects
like honestly
just give me the internet and some projects
Ill learn everything else
Projects are the best motivation
I hate this purely theoretical approach
where we memorize or read code and write these stupid exams
Test what we are capable off
make us do projects that take sleepless nights and litres of coffee
And judge our methods, documentation, team work, and output

Team work skills and tools (VCS, communicating, project management, etc.)

Documentation and Reporting
Properly
:)
maybe even with LaTeX :D

Yeah that's the gist of whats on my mind at the moment regarding an ideal computer science education
At least the foundations
The rest I leave it to the next dude.

I'm feeling burnt due to the lack of direction at my job instead of overwork.
I'm working as a data scientist at a large corporation and have been remote for a little over a year. I'm very savvy at programming and other technical skills but my manager wants me to develop my leadership skills and want me to move to a management role eventually. So he's been kinda "grooming" me to take on more leadership responsibility in the projects I'm currently involved in.

However, to be honest, I'm a little torn about getting more management or leadership responsibilities. I'm an extreme introvert and absolutely abhor meetings and having the same thing to people all the time and this sort of things stresses me out very easily. My manager seems set on pushing me towards pursuing a path towards leadership and just basically assumed that this is what I want out of my career and started putting me in the deep end without asking me what I want.

I really want to voice my honest thoughts about what I really want to do in my career (to be a technical specialist rather than a manager) but I've kinda procrastinated over the past year when he first started "grooming" me for a leadership role and it's my bad that I didn't tell him earlier.

Right now, I'm thrown in the deep end. I'm given a lot of projects without much of any direction and I'm asked to figure out the people I need to reach out to, the types of meetings I need to set with them, the relationships I need to develop both in and out of my department, etc. However, my real passions lie in writing code, fixing bugs, building models, understanding new technologies and applying them to the business, etc.

On paper, I'm involved in a ton of projects and I seem to be a really busy worker. But right now, I'm having a lot of difficulty reaching out and developing relationships with people that I barely have any actual work to do during the day, because I'm constantly waiting for replies from people or for permission or red tape to get some key information or access to a system in order for me to build something like a model or a program for a particular project. I'm spending maybe 1 or 2 hours of my workday actually "working" which is attending meetings, reading emails, etc., reaching out to someone for the n-th time (even though they continue to ignore me), etc. And that's because I'm blocked on all of my projects - I need an essential piece of information, data, or access to a system or server and the person I'm reaching out to to get this isn't responding. I brought this up with my manager and he says he's gonna try to reach out to these people to help me but so far, it doesn't seem like his help has been effective as I'm continuing to wait.

Though I get paid pretty well, I feel guilty logging in to work everyday and doing very little work, not because I'm lazy but because there really isn't much work for me to do because I'm waiting on so much here and I'm at a point where I can't make any progress in any of my projects without the approvals or other critical information that others aren't providing me.

I know I probably should find another job and I'm currently looking but in the meantime, is there anything else that I should be doing at my current job to hopefully make this situation better?

How many keywords are appropriate to put in a "skills" section on a resume?

Technically I've played with a lot of tech and stacks, and done tiny one offs, tutorials and independent projects but nothing that wasnt more than a day on any one of them.

Basically im fast at picking up a language and api and just rolling with it and getting something done, even without tutorials or tons of googling. Though I find myself constantly relying on manuals and reading apis.

Is this normal or should entry level be familiar with the api of something from the get go?

I see a lot of people say to game the system just to get your foot in the front door past the automated keyword filters and on to an interviews where the real requirements are listed.

But I'd rather not list under the skill section something I only used for all of ten hours in one or two sittings.

Also is it acceptable to list a "learning", "would like to learn/know more of", or "planned skill additions" section?

Also what do I add for extras? "Achievements"? "Volunteer work"? "Hobby projects?", "past times?"
Is any of this seen as necessary or well rounded?

If it is really just about the numbers I'll just go scrape junior and entry level positions and take their keywords and automatically fill out template resumes to automate applying.

Could even use SQLite to store the results and track progress lol.

I've never worked as a professional programmer, but it's the only thing I ever enjoyed doing for 12 hours a day.

Probably my language and communication skills.

I tend to think of programming as a conversation between the programmer and the machine.

Similar to being an effective communicator, the key to being a good programmer is knowing what to say when (deciding how to do a particular task, such as reading a file from disk) and not about simply knowing the different ways of saying the same thing (different ways of doing that task in your code).

Hey guys, first time writing here.
Around 8 months ago I joined a local company, developing enterprise web apps. First time for me working in a "real" programming job: I've been making a living from little freelance projects, personal apps and private programming lessons for the past 10 years, while on the side I chased the indie game dev dream, with little success. Then, one day, realized I needed to confront myself with the reality of 'standard' business, where the majority of people work, or risk growing too old to find a stable job.
I was kinda excited at first, looking forward to learning from experienced professionals in a long-standing company that has been around for decades. In the past years I coded almost 100% solo, so I really wanted to learn some solid team practices, refine my automated testing skills, and so on. Also, good pay, flexible hours and team is cool.

Then... I actually went there.

At first, I thought it was me. I thought I couldn't understand the code because I was used reading only mine.
I thought that it was me, not knowing well enough the quirks of web development to understand how things worked.
I though I was too lazy - it was shocking to see how hard those guys worked: I saw one guy once who was basically coding with one hand, answering a mail with another, all while doing some technical assistance on the phone.

Then I started to realize.

All projects are a disorganized mess, not only the legacy ones - actually the "green" products are quite worse.
Dependency injection hell: it seems like half of the code has been written by a DI fanatic and the other half by an assembly nostalgic who doesn't really like this new hippy thing called "functions".
Architecture is so messed up there are methods several THOUSANDS of lines long, and for the love of god most people on the team don't really even know WHAT those methods are for, but they're so intertwined with the rest of the codebase no one ever dares to touch them.
No automated test whatsoever, and because of the aforementioned DI hell, it's freaking hard to configure a testing environment (I've been trying for two days during my days off, with almost no success).
Of course documentation is completely absent, specifications are spread around hundreds of mails and opaquely named files thrown around personal shared folders, remote archives, etc.

So I rolled my sleeves up and started crunching as the rest of the team. I tried to follow the boy-scout rule, when the time and scope allowed. But god, it's hard. I'm tired as fuck, I miss working on my projects, or at least something that's not a complete madness. And it's unbearable to manually validate everything (hundreds of edge cases) by hand.

And the rest of the team acts like it's all normal. They look so at ease in this mess. It's like seeing someone quietly sitting inside a house on fire doing their stuff like nothing special is going on.

Please tell me it's not this way everywhere. I want out of this. I also feel like I'm "spoiled", and I should just do like the others and accept the depressing reality of working with all of this. But inside me I don't want to. I developed a taste for clean, easy maintainable code and I don't want to give it up.

Most developers are morons, pt 3

In this post, we'll discuss the top 13.6% of developers.

You might think, after reading the previous two posts, that I'm going to be praise these developers, or even claim to be in this cohort myself.

However, things aren't so black and white.

I've worked with many developers who are much smarter and more talented than me, and I can say safely say that about 90% of them are people I'd never want to associate with again.

These developers are usually on the spectrum and have amazing tech intelligence, but little emotional intelligence. Their people skills are minimal and they usually loathe having to work with other people. While they have dozens of algorithms and data structures memorized, their social skills only include rudeness and toxicity.

This only goes to show a lesson we all eventually learn: you can be the smartest person in the world, but if you're incapable of working with or understanding other people, you aren't getting anywhere. If you're an introvert, you've got an even harder job.

Doing hobby projects is a great way to improve new skills, helping people with their projects helps me to explain what I'm doing and reading stackoverflow posts!

!dev

My time management skills are abysmal. I am in my senior year in school and a few months back decided to appear for the informatics Olympiad. So now I am reading a book on discrete math, while reading books on algorithms and data structures. I code every day for around two hours. I have my math syllabi in school which is all calculus. My physics syllabi consists of all of EM and Optics along with nuclear physics. I haven’t touched chemistry since the beginning of this year. I try to give a considerable amount of time to math and physics because I f***ing love studying those. But doing that means slacking off on the Olympiad stuff. I am completely overwhelmed. My midterms are two weeks away and I am so unprepared. I am really clueless on how to manage time.

So, I told the interviewer that my frontend skills are bad. He said that I should not worry as the tests where backend centered, good. Later, I got the job, now the interviewer, which happens to be the head of tech in the company I work for, has assigned me two tasks involving 99% of work on the frontend.

FFS, I've been searching on Internet and reading Kendo UI documentation for 4 hours to figure how to trigger the KendoGrid editable popup with populated data to enable the user to update such data. AAAAARGH!!!

!rant
Experienced devs please tell help me.

Learning software development has been a challenge. Many times it's frustrating.

I also learn languages and I find them to share one trait with software development, which is complexity.

At first I looked at languages the way I'm currently doing with software. I'd look in a new language and after decided it's cool to learn it, I would stare at it for a few weeks trying to realize what the heck I was going to do. I wouldn't even know how to get started.

Eventually this stage goes away and I think that is about to happen with me with software.

But then a new challenge would come, which is me not making progress as I wanted. That's sort of happening with me by learning software as well, bit in language I now know how to deal with it.
That's because I work full time with something that isn't in my interests and when I arrive home Im tired and want to relax. So I decided my language learning had to go slower as long as I have this job, meaning no hours spent in front of books or a pc studying - that's what I could do with English, I was a teenager and had 12 hours a day to do whatever I wanted.

So I usually spent 5 minutes here and there learning something in my target language when I can, no frustration needed, my only rule is: practice everyday, even if I don't learn anything new.

With software, that doesn't apply though.

So, what I mean by tracing a parallel between these to fields is that I have a strong conviction is that once you get the principles on how a certain kind of learning works, you can apply it everywhere in the field. But with software it's been harder.
Anyways, I see that are some principles that apply, cause trying to learn software is changinge and teaching a lot of things like:

*you have to read a lot (of documentation) . At first I thought all documentation was painful to read and understand, but I found out some software are well documented and one can use those only to get used with it.

*immersion / discipline are important. I'm not very disciplined, I'm better with immersion but both are important if you need to acquire complex subjects/skills

*how to deal with complexity. I installed Arch Linux a few days ago. Just to install it I ended up reading more than 20 pages of documentation (install guide, Wpa supplicant, systemd, networkd, xorg, etc etc). Gradually I'm realizing that when you have to install/tweak something in that distro you necessarily spend a bunch of time trying to understand how it works, otherwise you don't get too far like in Ubuntu or Debian.

*and lastly the one that bothers me. Constantly getting frustrated and feeling crap about my poor skills. No matter how much I progress, it still seems like I'm stuck.
(that's when I ask your help/opinion :) )

Gotta question about the job market,

I'm having a very tough time getting a job, still jobless from when I quit my job awhile back, anyway all the jobs I look up that contain the words software/android/app/java developer seem to include web development skills.

Something of which I don't know much of, I wouldn't mind learning sure but for things like android development I can use Java just fine to create apps, yet the moment I start reading they want developers that know react.

Is this a normal thing? I can get to learning new languages and all but it'd be sad if my skills in Java for both software and app development are never used once I join that company.

Forgot to add this is for New Zealand job market, not sure it's normal for other countries.

Its been a month since i opened Android studio, and am feeling so weird doing the things now i do.

I had been learning and developing apps for almost an year( not exactly any big apps, but kinda in a learning phase, making prototypes, learning about the internal workings, reading blogs/articles,etc ) . Although i did got a few internships and earned some money, i didn't felt any good calling myself an Android developer with insufficient skills.

Frustrated, i just thought of taking a break, as my college was also giving a pressure of its own. Meanwhile i got a python data analytics scholarship from some 1 day competition at clg., So last September and October have pretty much gone into that. Python being an old friend seems like a pretty fun thing to do, and am totally into it (for now)

But java seems to let go of my hands even faster. Even though i used to waste much of my time reading how stuff works or checking out ui/animations , i did coded some stuff and made cool prototypes. i had a feeling that one day this all learning will be over and i will be able to code apps with ease... But now, it feels am going back to stage Zero. I feel as if i can't even write a hello world app.

I hope my poor little codebase is documented well enough to accept me back.
Don't leave me, java . We are on a break :'''(

[Career Advice]

Hi folks! I'm in a bit of a career dilemma for which I sincerely need your help.

TL;DR
How do I go from being a React Native Developer to an Android developer, considering I have 2x more experience with React Native than Android, with React Native being the more recent one ?

More details -

I started as an Android developer in 2015, using Java as my primary language. Up until the end of 2017 I kept working as an Android developer, adding different native mobile tech skills to my skillset.
At the end of 2017, my employer asked me if I could also learn React Native as he had many big projects that required a more hybrid stack. I had always been eager to learn new things (perks of being a programmer I guess), so I said yes and started working on React Native in 15-20 days.
From that point onwards, I kept doing more and more projects using React Native (in my day job) and over the years, I became more of a React Native Developer than an Android one. At this point in my career, I have about 4.5 years of React Native experience and 2.5 years of Android.

However, now I am at a point where I want to make a switch (for better pay and more exciting projects) but when I looked at the job postings for React Native this morning, they were all for startups with great pay but kinda average products, whereas the Android job listings were for companies like Uber, Reddit, etc. (basically great companies with good projects and great pay).

I really want to go back from being a React Native Developer to an Android developer full time but I don't know how. I've personally seen so many people switch jobs from one field (say React Native) to another (Backend development) - and when I asked them about how they did it, they said it didn't really matter to their companies what specific tech stack they'd worked with, which is kinda hard to believe because every job listing I've seen companies list every single technology very very specifically.

Any help/suggestions would be appreciated.

Thanks for reading!

!rant, reality check.

This may sound odd, but sometimes i deny wanting to learn a term or meaning of something because it is a severed thing from my knowledge.

E.I.: i read "Hey you can use LINQ for this!" as i am programming in C#. I do not mind reading up on what LINQ is, why LINQ is etc.

But, if i run into something like hey you can use XAML or whatever the hell, which i can't mentally link to anything i know, i flatout even refuse to look it up, or try to find out if it is related to my skills and if not, flat out ignore anything besides the basic concept.

Eventually i could still end up learning it, but if it doesn't click from where i am at right now as a programmer, i just skip it as unrelated noise.

Technically i deny to learn something, making me a bad "student" in a way. Otherwise i use my time optimally to only expand my knowledge on the borders or my current knowledge.

Does anyone else does this? Anyone longer then 4 years? Does anyone also apply this outside of programming? How did all that go for you? Is it a bad habbit or a good one?

I’m about to finish reading “Bad Blood” by John Carreyou. It’s an amazing story about this Sociopathic young woman managed to dupe so many people with her blood testing startup Theranos which turned out to be a fraud. Low key I’ve been reading too many biographies/novels. It’s about time I focused on my core skills— like coding and docker container orchestration.

depends,

the me who started learning at first felt proud that i gained skills all alone by watching tutorials, reading docs and making projects for fun. He would have said boot camps are for lazy and unmotivated people

the present me would say, i wish i could be spoon-fed everything i need in a bootcamp rather than spending hours on learning new tech

Upgrading my tech skills.. Once again I feel my personal my personal dev environment and told are much more up-to-date than what I use at work.... Though the book Kim reading is on TDD and was written 3 years ago.

Maybe I should read another on in cloud services and ML... but don't have any motivation for these topics.

I need TDD for work because now we're emphasizing unit test coverage...

I usually only use manual functional tests to verify the final outputs as either the testing framework is broken (JS) or I don't have time to relearn the frameworks for the particular language...

Anyway got off topic... So questions after:

1. Do you ever feel your technologically always more ahead than what you do at work and essentially you bring skills to the job but you don't learn much out of it?

2. How do you test? I actually got into a bit of a argument/discussion with my colleagues about how to implement unit tests. Apparently there are 2 ways to test? Black box vs WhiteBox. She said she tests only Public methods using mock inputs, dependencies. She read online and seems there is an opinion that should only test public functions and if you can't then your app is designed incorrectly, not separated enough.

For me I test the private functions individually (WhiteBox/Java reflection) because the public one is like generateReport and as a whole is like a Pachinko machine, too many unique paths that would need a test case for.

So thoughts? Yes sorry for turning it into a remake I guess...

Currently, I am pursuing a master's in MSc I.C.T.
Next year in June there is a company placement in our college. currently, I am Improving my communication skills and English for improve my English I am reading think and grow rich. How do I prepare for the tech interview for Java and javascript any suggestions or any personal tips to remember when I sit in the placement?