New Junior Developers Can’t Actually Code.
-
to play the devil's advocate: this can be done to exemplify what you complain about as opposed to complaining about an abstract concept
-
To be fair, most never could. I've been hiring junior devs for decades now, and all the ones straight out of university barely had any coding skills .
Its why I stopped looking at where they studied, I always first check their hobbies. if one of the hobbies is something nerdy and useless, tinkering with a raspberry or something, that indicates to me it's someone who loves coding and probably is already reasonably good at it
-
Nevermind how cybersecurity is a niche field that can vary by use case and environment.
At some level, you'll need to learn the security system of your company (or the lack there of) and the tools used by your department.
There is no class you can take that's going to give you more than broad theory.
-
Lately I have been using it for react code. It seems to be fairly decent at that. As a consequence when it does not work I get completely lost but despite this I think I have learned more with it then I would have without.
-
We stay away from riddles, and instead focus on CS concepts. We'll rephrase to avoid jargon if you don't have a formal education, or it has been a while. Here are a few categories:
- OOP concepts like SOLID
- concurrency vs parallelism, approaches for each (generators, threads, async,' etc), and tradeoffs
- typing (e.g. is a Python strongly or weakly typed? Java? JavaScript?), and practical implications
- functional programming concepts like closures, partial application, etc
- SQL knowledge
- types of tests, and approaches/goals for each
And some practical details like:
- major implementation details of our stack (Python's GIL, browser features like service workers, etc)
- git and docker experience
- build systems and other dev tools
That covers most of it. We don't expect every candidate to know everything, we just want to get an idea of the breadth and depth of their knowledge.
-
On the bright side, you might be able to cash in on some bug bounties.
-
that is your leaderships fault
-
This is probably because of a lack of training data, where it is referencing only one example and that example just had a mistake in it.
The one example could be flawless, but the output of an LLM is influenced by all of its input. 99.999% of that input is irrelevant to your situation, so of course it's going to degenerate the output.
What you (and everyone else) needs is a good search engine to find the needle in the haystack of human knowledge, you don't need that haystack ground down to dust to give you a needle-shaped piece of crap with slightly more iron than average.
-
Love it. So much to look into. Appreciate your time.
-
Yeah, I'm not even that down on using LLMs to search through and organize text that it was trained on. But in it's current iteration? It's fancy stack overflow, but stack overflow runs on like 6 servers. I'll be setting up some LLM stuff self hosted to play around with it, but I'm not ditching my brain's ability to write software any time soon.
-
That's simple. They use an LLM to find the right people for the job /s
-
Might sound a bit unrelated, but have you been noticing an apparent rise on ageism too? The social media seem to be fueling it for some reason.
