Avatar builder now live on desktop web! You can add/edit your avatar from your profile. We had a little help from our friends over at Toptal with some React work, if you're ever in need of some freelance skills you're lacking, check em out.

Oh you're a frontend guy? Good, we need one of those.

Oh you're a backend guy too? Good, we need one of those.

Oh you're a security guy too? Good, we need one of those.

Oh you're a devops guy too? Good, we need one of those.

Oh you're a QA guy too? Good, we need one of those.

Oh you're an SEO guy too? Good, we need one of those.

"Well, sorry to say fullStackCraft, but we found your cloud architecture skills just a little too lacking for this position. We really need someone who can do frontend, backend, security audits, QA assessments, SEO, AND build scaling cloud architecture. Oh and while you're at it, can you turn fucking water into gold? We need that at our company too. You didn't get the position, but it'd be great if you could refer us to someone who is very advanced in fucking alchemy. Thanks!"

Absolutely toxic the way software people are treated I swear. The money may be the only good thing that is left.

Okay, seriously, are there some secret question-asking ninja skills i am lacking, or does some people just insist on confusing people and wasting time?

I was working on this small bug. Super tiny. Basically a counter that was way off since it counted some duplicate values. Simple, right?
I decided to ask a clarifying question to the lead dev, since i am still new to the company. Really simple. Do we remove duplicate values, do we ignore them in the count when they occur, or is it actually working as expected?

He decides to answer with a long message on what the issue is. That is not what I asked, so I ask again in a slightly different way, thinking he didn't understand the question.. and he answers the same, in a slightly different way.

We go back and forth like this for 30-40 minutes, until I got tired of it and directly asked "I am asking what solution we want, not what the issue is"..
He finally picks option A. Fine. I made the adjustment and pushed my code. He checks it out, and apparently it's wrong.

After a long series of questions (again), it turns out the solution he now describes is exactly what I listed as option C...
A bug that should take 10 minutes to fix ended up taking over 2 hours. Awesome waste of time.

Managed to land 2 interviews:

The first one was for a startup that was looking for a react programmer (I've never used react before).

The later was a php job at a big company. They told me they used cakephp which is a framework I had not used before either.

Still, I'm more familiar with php than react so I felt more confident with the second interview. However, I felt there was a lot of good chemistry going on in the first interview.

The interviewer was incredibly nice (he was the lead dev, not an HR person as opposed to the second interviewer)

He gave me a small react test to be completed within a week. I barely managed to do it in time but I felt good about the solution.

Just as I was sending it, I get a call from the second interviewer saying I landed the php job.

I wasn't sure if my novice react skills would be impressive enough to secure me the react job (and I really needed a job) so I accepted.

After explaining everything to the guy who was interviewing me for the react job, he understood and was kind enough to schedule a code review where he walked through my novice code explaining what could be improved, helping me learn more in the process.

I regret not accepting the react position. The PHP they got me working with is fucking PHP5 with Cake2 :/

Don't get me wrong, I like the salary and the people are nice but the tech stack they're using (lacking source control by the way!), as well as all the lengthy meetings are soul-draining.

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!"

Seeing how cool the community's work stories here, and how they know a lot and how they work in organized companies makes me feel like an absolute piece of shit who's lacking a lot of industry skills.

Remotely working for a startup that lacks any sense of organization, CTO is a volunteering web developer who never shows up. A lone wolf I am. I never signed to be a lone wolf. A product that is based on an absolute garbage product that is in turn based on another utter garbage product. It feels so much pain every time I have to deal with that garbage that I end up watching some stupid anime instead. Decent salary for a junior, very friendly people, and a very empowering non-profit cause but still... technical side is just shit and I don't think I can keep with this.

Sigh :(

Who else feels like your JavaScript skills are lacking? I have only been coding for about 6 month's and JS for about 2 1/2 of it but still I am not an expert and I understand. But still . . .😥

Ok Rust help you write robust safe code and is very fast.
But at what cost ?
But why on earth the syntax is very disgusting. It takes time to familiarize with the horrible syntax.
And I feel like the sadistic rust cult members actually enjoy making it hard to read so that they can jump on any occasion to shout at you : you still lacking rustlang skills

Fuck that shit I'd rather write in golang or just deal with C++ . At least their syntax doesn't make me wanna puck

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.

I'm envious of Backend developers who can just 'see' the problem domain and start creating an architecture. I can't see shit - I just stare blankly at the project and I think: hm, what models do I write?

I know I'm a structured person, but I lack the knowledge and practice. One day I'll be able to do this, but for now I have to keep doing things ad hoc.

I really don't belong in the Backend but unfortunately that's how my career is turning out for now. All I know is I have to get better at this.

Hey all, just wondering what it was like for you when starting out your career.

I'm a newish dev, been full time for about a year hired right after my internship. My role has a bunch of hats ranging from DevOps/sys admin to software engineering, sort of a weird mashup of skills so it's not pure software engineering. I mainly work with python, Ansible, and some terraform.

However I still just want to say I'm sorely disappointed in my undergrad classes.

I have a "concentration" in software engineering. I did struggle in classes as I was working full time to pay for classes without taking out loans, but I don't really remember learning a whole lot that was useful in industry.

Overall I just feel like just paid money for a degree that didn't teach me very much useful stuff. Maybe I'm just lacking experience? Maybe what I learned I just don't notice myself applying because it's subconscious?
My coworkers have taught me so much, and I'm very thankful they invested that time into me. I still get ripped to shreds during code reviews lmao (definitely not as much compared to when I first started but I'm also still learning and will always be)
Plus our company docs are pretty good so I can always read through them or search our codebase for examples on how to utilize in house tools etc.

I definitely hit the jackpot with this job, just feeling like I should have been prepared more.

My main project in work is making program in C# (right now .NET Standard) that can read scans of invoices that are sent from contractors. I'm working on it for almost two years now (with breaks and only halftime because university). Alone. And for last two months I've been redesigning, refactoring and making whole app "better", using experience and knowledge gained in the last two years.

Obviously my boss wasn't happy with that but I got him to accept it, promising that it'll make it work faster, expansion will be simpler and I'll make core as a separate library that can be used anywhere, not only in the JobRouter ecosystem.

And so I reworked most of the code, made it cleaner, I hope, and a tad quicker. And I was happy with it while testing on a package of invoices. Today I made first integration with customer's JobRouter.

The results aren't any better - in some cases they are much worse. Especially while searching for invoice entries, which can be in any shape or form and on any of document's pages.

I guess, being a Junior, I wasn't really up to the task. I'm sick of working on a "guessing" program that has to work with every invoice template users can imagine. I'm sick of not getting any recognition for what I did good. And I'm sick of constantly being pushed to make it work better when I just don't have any more ideas or my skills are just lacking.

To be honest, I don't know what to do. I'll probably have to work on making it search the data better. But it's not trivial to just look at the code and see errors. Iterating on the code while working with different invoices worked for a bit in older versions, but I reached the point where changes made to make one invoice be read better, made another one worse.

Its like on those GIFs where you squish one bug to make another two appear.

So yeah, I'm currently really doubting my career, skills and intelligence.