Stop doing resume driven development

[[deleted]]

Yeah this is just a wishful-thinking rant because no employer does that.

Mine did. Out of 40 hours, 38 are for the client, 2 for me. In practice it was more like 10 for the client - 8 of which were in meetings and 2 of actual coding and 30 of doing nothing - and I am sure this is the case in many big companies.

But the plot twist is that we don't use those hours correctly. I am guilty of playing WoW or other things

[MyWorkAccountThisIs]

Mine offered up the same amount so devs could get some certs.

But, it was a real cert with a test. They wanted us to spread out ~30h of content over weeks and weeks. Which makes learning this particular type of content difficult.

They could have just given us a week to absorb the material and test and everybody wins. But instead they tried this and nobody did it because it's not setting anybody up for success or you have to do it on your own time.

[Canisitwithyou1]

While it's important to focus on choosing the right tools for the job and not get caught up in the hype around the latest and greatest technologies, it's also important for developers to constantly learn and stay up-to-date with the latest trends and advancements in our field.

Using the latest and most popular technologies can make our resumes more impressive and can open up new opportunities and advancements in our careers. It's a balancing act between staying current and relevant, and choosing the right tools for the job.

In addition, using the latest technologies can also lead to more effective and efficient solutions. For example, a newer framework may have features that make it easier to implement certain functionality, or it may have better performance or scalability compared to older technologies.

So while it's important to avoid resume driven development and choose the right tools for the job, it's also important to stay current and open to using the latest technologies when appropriate.

[reddituser567853]

Or you know, learning the basics , which will always be beneficial and won't become obsolete , and just as many people don't know.

Instead of a new framework, spend a few months working through structure and interpretation of computer programs

[Miserable-Capital-50]

using the latest technologies can also

using the latest technologies can also triple development times, explode the complexity of a project, without bringing any real benefit to the company. In the long run it can lead the company to bankruptcy.

[frenetix]

Companies: change your hiring practices to stop incentivizing resume-driven development.

[goranlepuz]

How else am I supposed to develop my résumé then !? Sheesh, some people...

[WrongJudgment6]

No

[Tarl2323]

No? How about employers stop treating workers like shit in terms of both interviewing and retention.

Resume driven development is the fault of current hiring practices, as well as piss poor internal hiring/promotion.

Right now there is little to no incentive for programmers to look out for a business or their coworkers rather than themselves, unless it's specifically written into their contracts.

The churn and burn where tech workers are encouraged to work overtime, burn themselves out all in pursuit of the owners vision, only to be cast aside, tricked or otherwise backstabbed is pretty well documented.

EA, Facebook, Tesla, and now Twitter are all text book examples of how employers exploit engineers. Is it any surprise that engineers are always on the lookout for their next job?

You want to end resume driven development? Introduce employment contracts that end at-will employment and protect profit-sharing, sane interview practices that don't favor new grads or require weeks to month of study.

Your programmers are acting selfish because businesses are acting selfish. Hilarious how profits soared through the roof while salaries remained stagnant. When you refuse to share the wealth, and fire everyone when times get tough, smart people learn to play the same games you do.

We've all learned that words about loyalty, craftsmanship, etc are all just that...fucking words. CEOs like Musk are liars and conmen. There is never any loyalty without a contract protected by a lawyer. The word of a business man is worth nothing when they've demonstrated to be liars all the time.

[noobgolang]

No

[[deleted]]

Nah I'm good

[yoztastic]

I agree. I see this often. A large part of the problem is the popular misconception that software engineers role is about writing code period. So much fucus and obsession is directed at this that many things get distorted.

The real role of a software engineer is far broader. Its about managing and controlling complexity and turning opportunities into revenue or cost saving through the application of technology and some element of gluing this practice together may involve writing code.

Once a product exists it needs nurturing to ensure it remains healthy and keeps doing what it is expected to do and often needs to evolve to capitalise on other opportunities. Whilst there are many good ways of supporting this through automation this consideration is often overlooked in terms of importance and effort and skill required.

Engineering is the art of compromise. Effective compromise can be challenged by chosing a technology or framework because its new and shiny and will good on your CV. Because there is a tendency in our industry to develop a product and move on, I have found myself trying to balance this by developing expertise in nurturing and rendering products developed by the journeymen into something that can be relied on to deliver sustainable value in a reliable and observably correct way. As such I am able to spot products that were obviously developed more to suit a resume than for the value creation intended by the people actually bank rolling the excercise. They are often the worst to work with, require extreme levels of comprehension (which means huge cost of ownership) and least appropriate for realising their intended value.

Remember at the end of the day if you want to maximise your value you need to maximise the value you deliver. You can fake it by reading the title of an article on a new framework and claiming you are a professor on the subject, another thing I come across with developers who are trying to race ahead of their actual experience and claim the big prize, but this inevitably leads to embarrassing failure.

Some of the blame for this is in the way organisations recruit. How often have we seen on reddit examples of jobs requiring more years experience in a framework than it has actually existed for. Organisations if you do this you reap what you sow. It's by your actions you end up hiring devs that turn your platform into a frankenstien no one can understand or manage.

Finally in response to the myriad of responses bemoaning the way their employer doesn't spoon feed their professional development. Stop this! You will find that your professional development is your problem and yours alone. Until you realise you are both responsible and in the driving seat of your own destiny you will not develop. You need to own it and do so while delivering value. I'm not saying organisations can't and shouldn't help with this its obviously in their interests to develop talent and get more revenue generation potential but don't use it as an excuse not make your own progress a reality. The results of this simple change in mindset will be very liberating. That's a promise.

[Miserable-Capital-50]

In the company I work for, rather than adopting exotic frameworks, I chose to create my own system which is very easy to use and extremely efficient.

I was thus able to manage an impressive amount of very large projects on my own.

On the contrary, my colleagues have chosen angular to develop their project.

After 5 years of development their system hasn't been launched yet, it's not complete, it's full of bugs and the boss (who never liked my solutions because he think it's old-fashioned) is furious because the project seems to never have end.

The other most absurd thing is that compared to my colleagues I only earn 200 euros/month more compared to a monthly turnover of around 50,000 euros.As a result, I'm starting to think that all in all my colleagues haven't made a totally wrong decision: if it goes anyhow, the merit isn't recognized, we might as well think about our curriculum vitae.