Stop using progress bars on your résumé/CV!

Back when we were looking for people to join us, we got hundreds of résumés in the mail and online, and I saw so many of them using these progress bars to indicate competency in a particular skill or programming language.

Yknow what that says to me, and to my colleagues?

"Yeah, I'm ok at this, but I'm even worse at THIS"

Your résumé is about selling yourself!
We don't want someone who's '68%' in Photoshop or '82%' in JavaScript. We want someone who knows they're good at what they do and knows they can learn if they need to.

You might feel like you're being 'big headed', but that's what a good resume SHOULD be! Sell yourself to be as if you're the solution to all of my problems and you might just get a job!

Rant over.

My teacher at school who taught me programming. We were taught Java.

You see, Java is not a beginner's language, most say. But the way she taught it, the examples, the analogy, the explanation; she made it so easy.

She made us execute our first Hello World program (using BlueJ) and proudly said, "you're all programmers now!", that was when fascination took me over. I remember​ that moment till today.

Also, unlike regular exams, the programming exams required extreme competency. Marks were split up for algorithm and syntax. There were also questions like find the error in this algorithm for this output. She would always surprise us at the exams!

I had several glorious moments in class by being the first to answer most of her questions. At 13, it was kind of a big deal for me.
(Okay, who am I kidding, it still is :-P)

*sigh*

It was mostly just self learning from there. I switched schools and then there was college. Attending classes in college was like going to the gym with fat trainers. Utterly useless :-/ It just made me appreciate her even more.

Do not hire a team of full stack developers such that the entire teams' core competency is back-end development and then wonder why they can't hurry the fuck up to design and build usable, device-friendly interfaces.

Hire a damned front-end dev.

So I've been applying to jobs. I, purposely, have been putting down that I am female (since they all harp on diversity, I'd like to see if they even bother reaching out to me. Also anything to get my resume past the bots).

Spoiler alert - getting similar ratios to male counterparts, 100+ applications sent, maybe 4 phone interviews. No offers yet. Still made to do code challenges.

Well, I just found out where all that diversity hiring went to. Buddy of mine who works at a mid tier company said that they have a special program that onboards women into tech.

Specifically, women who have literally zero background in computers.

Teachers, social workers, etc. They get a week or so of some coding bootcamp and then get full time positions over more skilled applicants.

This infuriates me. I literally would be in a better situation to be hired had I not have had any technical background, taken this particular bootcamp and finally net the elusive entry level position I need.

And guess what? That move has antagonized the existing male employees who see that they have zero interest and zero competency instead of having an integrated workplace.

10/10 for incredible bullshit.

Got the ideal job right now. Over market salary. 100% remote. Mornings to myself until the rest of the team in another time zone comes online. Working within my competency with just enough challenge to make it interesting. Free products for being an employee. Only wish it came with paid health insurance but I do get a partial reimbursement.

Highschool culture...

Here in Italy we run a few exam simulation in order to prepare for finals in June.
One of the two categories of simulations, one of which revolves around the core subjects of our technical course which in my case is CompSci and Networking.

"Sounds good!" one would say.
And I'd agree, if only our CompSci professor graded solutions in a sensate manner.
If one does not exactly copy and paste the solutions we repated in class 100 times (which, by the way, are all EXACTLY the same solution but with different data in diagrams and other sections), the grade WILL be insufficient: no but's or why's.

This is only one of the prime examples of what school revolves around. Sometimes it just feels like we are trained to be sheeps in a world of wolves. Rinse and repeat over and over. No technical competency is (almost) ever valued or allowed to be expressed and is often looked down upon by old school professors who literally care about everything but their subject, students and school in general.

I'm glad this is almost over, and that greener pastures are ahead :)

Am I the only one that thinks it's extremely fucking stupid that the software engineering industry is simultaneously experiencing a "shortage of talent" and maintaining the same ATS that filters legitimate talent just because the resume doesn't fit keyword specifications?

We see it every day. People with years of experience that should never be allowed to touch important code. People with little to no experience that learn fast and perform well. Fuck years of experience being the only thing some recruiters see.

"We generally don't hire people with less than 3 years experience" shut your fucking mouth. Ridiculous. You hire people out of college, don't lie to my face.

Oh and don't even get me started on how many people fabricate their industry experience and get interviews from it. That's what happens when recruitment patterns fail to catch up to an industry that increasingly trains people better up front, and in shorter time periods, and values skills that ATS doesn't give a shit about.

Crazy idea: make job applications test problem solving competency instead of weeding out quality candidates.

Job searching is frustrating.

My university alerts all student and staff any time a phishing email is reported. I've yet to attend one class, and I've received a few dozen emails alerting you of phishing emails being sent. It's sad people can't notice the pattern of the emails, and realize right away "Hey this is a bullshit email" and not rely on the alerts.

It's the 21st century; basic computer competency is a necessity.

Another day, another shitty set of JIRA tickets.

In this week's edition, we run into an issue you'd think is a meme, something you couldn't even make up: three tickets with IDENTICAL titles, but miraculously, they actually refer to three DIFFERENT tasks! (Also comical, they're not bugs, they're tasks, but mouth breathers don't really know the difference, and at this point I just don't have the energy to attempt to explain what could be explained to elementary school children.)

I present a rare look into our national archives!

This document features two exhibits:

Exhibit A: product owner's original ticket titles

Exhibit B: translated-into-competency-because-i'm-not-mentally-deficient ticket titles

Just more proof that 'product owners' don't own shit, the devs are the real ones who actually know what is going on.

I mean just LOOK at Exhibit A's titles. As a big smart manager, do you write those tickets, smile, and say to yourself "Ah, yep, that's very clear, I'll definitely remember what each of these mean literally 5 seconds from now!"

Is asking for literally 30 seconds more of thought too much to ask for? Apparently.

Just kill me

Happy friday ☠️

It's utterly frustrating to work with someone who has been in the same job for five years but still hasn't bothered to learn the basic tools necessary to do their job effectively. It's like they're stuck in a time warp, refusing to adapt and improve their skills.

How can you possibly expect to be successful in your career if you're not willing to invest time and effort into learning the tools of your trade? It's not rocket science, and these tools are there to make your job easier, not harder.

And what's worse is when these same people complain about their workload, blaming the tools for their inefficiency. Well, guess what? If you took the time to learn how to use them properly, maybe you wouldn't be drowning in work right now.

It's not even about being tech-savvy or a quick learner. It's simply about taking some initiative and responsibility for your own professional development. It's about having the basic level of competency required for your job.

Not to mention that constantly asking for help and guidance on tasks you should be able to handle on your own is not only a waste of your colleagues' time but also reflects poorly on your work ethic and reliability.

So, please, if you've been in the same job for five years and still struggle with basic tools, do yourself and your team a favor and take the time to learn them. It will make everyone's lives easier and improve your chances of success in the long run. Don't stay stagnant and hold yourself back – embrace opportunities to learn and grow. Your career will thank you for it.

The tools in question is Kubernetes and it's directly related to the persons day-to-day work (SWE + SDET mainly), 5 years is more than enough time to learn and adapt to a new toolset, and yet this particular person refuses to invest time into it. It's frustrating, to say the least, but also a disservice to themselves as they are limiting their potential and hindering their own career growth.

Talking with manager about C++ ...

ME: ... and those are the main differences when coming from C03 to C17.

MGR: OK. I think I got it... are these changes those kind of changes that when we know them we can work in any industry if they use C++?

ME: No they are not, sorry. They are like basic enablers to even start considering entering some industries. What you mean are standards. AUTOSAR standard for example is for automotive industry.
The standard requires some level of C++ standard competency.

MGR: Are these standards like plugins for C++...

ME: ? ... no. They specify rules and architecture, conventions and such.

MGR: ... aah. Architecture, I know that word. So in fact they are plugins....like...like...Eclipse IDE has architecture and it can have plugins....right ? ... and you just plugin that AUTOSAR standard to C++ language.

ME: I think you mixing stuff up on multiple levels here. I think we are not ready to talk C++ competency as a strategic decision yet... lets get some basics down first and discuss this stuff in one month.

MGR: ... ?..but, but I mean it can't be that hard. I think I almost got the gist. I just misunderstood at some point.

ME: Sure, sure. No worries...you almost had it *with deep sarcasm*.

So I got in contact with a recruiter who said they have a possible job for me. The catch is it's in c# (I am a python java dev) and that there is a assessment test for the language to test for competency. I told the recruiter that's fine but I would need a week to highlight the main differences between the two languages and at least do a couple of educational programs for my learning sake. All was fine and that was the plan.
The next day the recruiter notifies me that the test is being called off on account of the company being swarmed. So the recruiter then proposes another similar test (in c#) the recruiter will use to measure my skills and that the recruiter will send the test via email that same day. Later that day I check my email and don't see the test. So I message the recruiter and never get a response. Next day comes and I decide to give the recruiter a call; no response. I then wait until the next day and message him on linkedin that I still needed the test. Linkedin was showing he read the message, but of course didn't respond.
I told my brother about this and he said to send a message saying: "Hi [recruiters name] because of the lack of further feedback I decided to go with another opportunity. Best regards, Lane"
After I send it I get a message the next day from the recruiter saying: "Hey, sorry I haven't gotten back to you. We had to install a new phone system yesterday so it was a busy day."
"I'm going to send it to you today so that you can look at it over the weekend. "
I can't help but think the recruiter is full of shit, but I may be jumping to conclusion. I know they can have a busy schedule, but if you have time to look at a message on linkedin how long would it take to type a short message explaining what's going on? I would like to know any opinions or insights on this.

I was asked to make proof of concept small frontend app with some simplified requirements, they asked me because it should be written in the stack I done most of my career work with. I do it in 3 days instead of 5, using those 2 days to optimise the app and explore different approaches. I noted down my findings, what to avoid and reasons and also what is good to use and reasons and shared with everyone.

We waited for the project to start, I started working on another project in the meantime and there was a big rush to make project go live etc., so I was consumed 100% on that new project.

So they put in charge backend php developer to do frontend js work. I said ok, do you need help in starting out? Nah, my proof of concept repo is enough.

4 days before that small project goes live they asked me to do code review. All things I noted down to avoid are in the codebase, few bad practices but everything is over-engineered (in a very bad way), some parts should be more flexible as current setup is very rigid, having almost all kinds of CSS, I saw SASS, CSS variables, 2 different CSS-in-JS tools with some additional libraries that is used to toggle classes.

I don't know how to approach this as I am not asshole as a person and I don't want to say to my colleague that his codebase is completely trash, but it is.

The worst parts: They called me to help finish the app and budget is almost spent!

I would rewrite the whole app as the state of the current app is unusable and everything is glued with bad Chinese ducktape that barely holds.

Additional points because it won't bundle as everything is f**ked.

I am seriously thinking of duplicating master branch and refactor the whole fricking app but won't do that as I am burning midnight oil on other two projects. Don't worry overtimes are paid.

I hate those shitty situations, this project was supposed to be tiny, sweet and example of decent project in this company but it is instead big fat franken-app that will be example how smart it is to avoid putting backend dev to do frontend work (I also agree for vice versa)!

No wonder it’s hard to hire devs with even a basic level of competency or some kind of promise that them might be able to learn shit given time, opportunity and guidance. The sheer amount of idiocy and stupidity and straight up incompetent cringe I witness on every platform giving us devs a voice (yes, including here) is mindboggling…

The feeling of incompetence when you realize all your life you've copied and extended tutorial code from the internet. So much so, that the thought of coding from line 0 sends a chill down your spine.

It's a challenge working with people that aren't as competent as yourself. Having another programmer misunderstand some system's design and throw copypasta around; or an artist who wants to chime in on low-level system design. It's hard to communicate not only how things work, but that a person should stick to their designated role and competency - without bruising egos.

I think one of the hardest experiences as a junior is the oscillation from perceived competency to perceived incompetency.

I just spent the last 4 weeks putting together my first major UI set of components for a financial calculator. Uses Vue, Quasar, a lot of data transformation and reactive UI programming. I felt quite chuffed. Its pending merge.

Then my lead asked me to help him debug something on the flagship and legacy project; for educational purposes, not that he actually needs my help. The application is 100x the size of the one I have been working on, and monolithic. Orders of magnitude more complex.

The jump from a sense of “I might be able to do this” to “I could never do that” was almost soul destroying. Like looking back over the last ten meters you ran, realising that running is hard and you did it. Only to look ahead and realise there are easily 100 miles ahead of you.

How the fuck do you cope with that.

Do you have an issue with Equifax hiring a Chief Security Officer having a music degree or do you think that it has nothing to do with her competency and it shouldn't be brought up as an issue after this hack.. Go!!

So I've been helping with recruitment at work for a lead developer. Our first stage is pretty standard for all levels and it essentially a technical interview because CVs are useless really. We're a C# house so we have questions on framework internals such as how the dictionary class is implemented, locking and thread synchronization techniques. Then some pen and paper coding excercises, like reverse array.

I'm not a big fan of these and I think they are too constrained to detail implementations and not about concepts.

So I ask what stuff do you do at your company to get an idea of some ones competency?

What’s the point of having side projects if your just asked to do leetcode to show your competency 😞

Why is instagram so thoroughly broken and a user experience torture.

I know the standard answer of "As long as the core flows that hold up the popularity work, no one cares much", and yeah, true, but that's a reason for why no one fixes the broken stuff.

What I want to know is why is it so thoroughly broken in the first place? Granted, Facebook isn't the best of places but one would expect at least a certaim level of competency from a team coming from the same organisation that gave us React JS(even if Instagram did not originate there, they have been in the Zuck empire for a while now). Why do such thoroughly messed up UI/UX and features get pushed to prod in a company that has the time, resources, and talent to do things professionally(read: better than the mess that instagram is). Not to mention a fuck ton of missing simple features that would make using it much better experience (JUST LET ME AT LEAST COPY COMMENTS GODFRKINDAMNIT IF ENABLING EDITING COMMENTS WILL COST YOU YOUR FIRSTBORN'S SOUL)

Maybe I am somewhat biased since I use Instagram desktop more than the mobile app, but my point should still stand.

I do not feel insecure in my competency as software/Firmware engineer but i started feeling really insecure about being an engineer , mostly because the way Society in general place us
usually it's like

surgeon > physician > Scientist (or any basic science person) > engineer

i didn't realise this before but recently i noticed and i stopped introducing myself as engineer to the people i meet either from my family or from dating apps. Here is the conversation that usually happens

Person: what do you do ?
Me: I build things
Person: so what do build ?
Me: My work involves building lot of things related to smart phone's wireless capabilities.
Person: oh so you manufacture phones ?
Me: No i work in connectivity part of it like bluetooth , wifi
Person: I don't understand, does it involve staring at computers all day (makes a face )
Me: yes 90% of it , I like building things making something new HW or SW and most of them do require a use of computer , even if I was a mechanical engineer computers would be necessary
Person: Hmm if i was not a surgeon i would be hair dresser , because i can't do anything that involves staring at computers all day.

same conversation happened multiple times.
no matter how good you are at writing code or how important task that code is performing , society consider's Software Engineering as a mundane task of " staring at screen "
if that song Remember the name is written for software engineers it will go like

This is ten percent luck
Twenty percent skill
Fifteen percent concentrated power of will
Five percent pleasure
Fifty percent pain
And a hundred percent reason to live in disdain

What is your perception of the minimal competency required by a fresh junior developer in both soft-/hardskills?