We will never have enough software developers (2020)

Post by lokar » Tue, Jun 14, 2022, 11:00 PM UTC

commandlinefan wrote: post #249

cabraca wrote: post #7

Earlier quoted context omitted.

its not just the best ones. If you remove people from the grind for 1-2 days a week, give them a small budget and enough autonomy to do what they want, most people will fix shit that bugged them for a long time. The main problem is how micromanage-y the current development processes are. Everything has to be a ticket/user story and has to be planned and approved by some people that never even wrote a single line of c…

> has to be planned and approved It gets worse, too - as long as I've worked as a software developer there's been some sort of time tracking system in place, and it has to be planned up-front, and has to work out to at least 40 hours (after they "negotiate" your estimates down). Which leaves no time for the unplanned stuff that inevitably comes up. This always goes in a cycle like this: 1. Management demands that eve…

Post by spc476 » Tue, Jun 14, 2022, 11:05 PM UTC

sirsinsalot wrote: post #259

Guid_NewGuid wrote: post #181

Earlier quoted context omitted.

It sounds like SOC2 compliance requirements unfortunately. Plus process overhead on who can raise tickets. I've found compliance makes it harder to write good code. If you get a PR approval with optional suggestions you're heavily disincentivised from actually addressing those comments since if you push those changes you now need to wait for review again. Like everything process and compliance it's designed by low-co…

I fundamentally disagree with this. In our product, a change has the potential to cost businesses lots of money and also bring our customers into legal trouble, potentially making us liable too. That's why we have heavy-handed change control, code vetting and so on. Yes it makes things slower, but due to the risks involved. I've also worked on embedded projects where field updates are HARD and costly. We had heavy-ha…

Post by treis » Tue, Jun 14, 2022, 11:13 PM UTC

chadash wrote: post #406

csomar wrote: post #339

Earlier quoted context omitted.

Depends on what exactly your company is doing? Why do you care if an applicant understand how a hash map works; and what's particular about a hash map? I'd care more about an applicant understanding the concept of a hash; or hashing in general. If an applicant shows that he understands that a hash is a magical and fascinating mathematical concept; and it can have uses in Information/Computers, that would be more inte…

> why do you care if an applicant understand how a hash map works; and what's particular about a hash map? Because a hash map is: 1) a pretty basic concept in data structures 2) Variations on hash maps are used all the time in the real world. If you use objects in javascript, dictionaries in python, or maps in C++, then you are using things that essentially implement hash maps. Point number 1 is like if I went to an…

Post by mattnewton » Tue, Jun 14, 2022, 11:25 PM UTC

rootusrootus wrote: post #124

Patrol8394 wrote: post #110

There is no shortage of swe. What I see and what I have experienced first hand is that companies, especially the more hyped/small ones, pretend to be FAANG and gets very picky when interviewing. They often employ FAANG style interview. Now, if I really have to spend that much time prepping to interview at your unprofitable company (that most likely will go under) don’t you think that I would try my best to work at fa…

I definitely think "we do not do leetcode interviews" and maybe "we only have three interviews total" would be selling points on a job posting. People who are experienced in the field don't want to go through the same hoops that newbies do just to prove they know how to write basic algorithms.

Post by shagie » Tue, Jun 14, 2022, 11:38 PM UTC

dmitrygr wrote: post #447

shagie wrote: post #430

Earlier quoted context omitted.

The first issue I tackled at one of the jobs I had was slow JSP page performance. The code had some sizable chunks of JavaScript in Strings and looked at each authorization the user had. Its been awhile, but in dynamically generating that JavaScript (ICK!) it generated several megabytes of garbage Strings by doing `script = script + "little bit more";` way too many times. This was done for each page load. 8am and hun…

Must have been a long time ago. It's been almost a decade since that code pattern started getting compiled into calls to StringBuilder by javac.

    String foo = "foo";
    foo += "bar";

    String foo = "foo";
    foo = new StringBuilder(foo).append("bar");

    String foo = "foo";
    foo += "bar";
    foo += "qux";

    String foo = "foo";
    foo = new StringBuilder(foo).append("bar");
    foo = new StringBuilder(foo).append("qux");