81–90 of 119 posts
This is a list of known unknowns. Those are usually not a problem - the problems come with unknown unknowns.
https://overreacted.io/the-elements-of-ui-engineering/
Reading it I feel that creative problem solving is more important than simply knowing stuff. I wonder if knowing too much stuff is actually detrimental to exploring new ideas and trying them out.
no offense, but from this list the author is either 1) stuck in a particular domain or language or 2) not very proactive in broader learning or side projects. I agree it’s ok to not program C or understand network/transport layer in depth. but things like unix shell basics, python, micro services, docker - these are all fundamentals I assume everyone (backend, frontend, mobile, or game engine) has working understandi…
Co-creator of redux, he was partly motivated to write the article to counter ideas you need to be fluent in everything, often propogated (intentionally or not) by "as a hiring manager...red flags" posts like yours. Fwiw: https://github.com/gaearon
Earlier quoted context omitted.
Not exactly that, but when reading Coders at Work I was surprised to learn that a lot of big names in our field use "printf debugging" and don't like actual debugging tools. Made me feel less bad about it :)
As a distributed software developer, I have found debuggers less useful these days. If I need a debugger, it probably means I don't really know the code that I am working on. Good IDEs with good static analysis, good unit test/integration test/e2e test coverage, a true understanding of the code base before changing it, all these avoid most bugs. When the production hits a bug, good monitoring and logging can help roo…
Earlier quoted context omitted.
I know exactly who posted the article, thank you. I simply disagree that you can be a frontend engineer in the usual meaning it has without some level of those skills. Doesn’t mean anyone is less capable, deserving or cannot make a living that way.
But he is literally one of the most successful front end engineers of all time and lacks those skills. Your takeaway from the article is it’s antithesis.
He's skilled at JavaScript and C# and worked with Python for years, what's the betting he's as good as any typical Python developer, if not better? Pretty good, I'd think.
> "I struggle to read either LISP-inspired (like Clojure), Haskell-inspired (like Elm), or ML-inspired (like OCaml) code"
How many people don't know Haskell but can successfully struggle through reading it instead of having their eyes glaze over and completely refuse to try?
> "CORS. I dread these errors! I know I need to set up some headers to fix them but I’ve wasted hours here in the past."
"I don't know it - but I've also worked on it and know how to fix it and done so" - hmmmm. I suspect he is more capable than he's making out; politely talking himself down.
This article really makes me feel good as a current intern and comp sci student. I thought I clearly defined what a junior dev could be if I worked at it for another year. Having read all the stuff this guy doesn't know and what I've learned at my internship, it's almost any hint of imposter syndrome I might of had went away. Now I'm not saying he doesn't know how to program. I'm just saying it's very interesting to…
This article really makes me feel good as a current intern and comp sci student. I thought I clearly defined what a junior dev could be if I worked at it for another year. Having read all the stuff this guy doesn't know and what I've learned at my internship, it's almost any hint of imposter syndrome I might of had went away. Now I'm not saying he doesn't know how to program. I'm just saying it's very interesting to…
During my last job hunt three years ago, I had interviews every week. On my current job hunt, I'm having problems booking just one.
There will always be a combination of factors that can make your job search easier or harder.
Earlier quoted context omitted.
Co-creator of redux, he was partly motivated to write the article to counter ideas you need to be fluent in everything, often propogated (intentionally or not) by "as a hiring manager...red flags" posts like yours. Fwiw: https://github.com/gaearon
On one hand I agree with his sentiment. But being a co-creator of redux is not really a good argument. I would probably flat-out reject members of the core redux team when hiring, considering redux's design.
I am not sorry, this does not impress me. From the comments it appears this person has done some significant work in YetAnotherJavaScriptFramework. Boasting that: Fuzzy on the details of how TCP/IP works (hello web developer, read a book!), does not understand order complexity specifically or algorithms in general - as one commenter pointed out - no wonder JS front ends are such shit if this is the level of intellect…
If the knowledge is not relevant or applicable to what you are working on, what is the problem?
Knowing that things exist is more important than in-depth knowledge of those things.
Earlier quoted context omitted.
On one hand I agree with his sentiment. But being a co-creator of redux is not really a good argument. I would probably flat-out reject members of the core redux team when hiring, considering redux's design.
What's wrong with the design of Redux?
Some ideas of redux are great, but the execution could have been much better. I think lack of experience (maybe also related to Javascript) is the reason.