Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Things I Don’t Know as of 2018

overreacted.io

Post reply on HN
Print view View original

91–100 of 119 posts

Re: Things I Don’t Know as of 2018

#91

Post by recursive »

worik wrote: post #36

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…

Lots of things can be learned from books, but there are only so many hours in a day.

The vast majority of web developers I've worked with don't know TCP, and I'd count myself in that group too.

Re: Things I Don’t Know as of 2018

#92

Post by rantwasp »

watermelon59 wrote: post #34
nemo1618 wrote: post #17

I'd love to see lists like this from more high-profile programmers. What does John Carmack not know? What does Dan Bernstein not know? What does Bryan Cantrill not know?

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 :)

that's a feature not a bug. you see... in today's world if you need to attach the debugger to understand something you have already lost. why? because you should not be able to attach a debugger to a production system (if you can that is another can of worm). ideally the logging + metrics of what you are building is enough for you to understand what is going on.

there is one notable exception to the no debugger rule: if you are learning/exploring a new code base on your dev machine and/or when writing tests [to cover legacy code]. but apart from that, unless your work is really special, you should not need a debugger.

Re: Things I Don’t Know as of 2018

#93

Post by dreamcompiler »

efiecho wrote: post #18

> Electron. Never tried it. And nothing of value is lost.

The first time I spun up my own Electron app, I simultaneously had two feelings:

1. That took a lot of futzing around.

2. But way less futzing around than I expected for a fully cross-platform application.

I still think the idea of Electron (using modern web technologies to develop applications) has merit. It just needs a better implementation (i.e use native webviews rather than shipping an entire browser.)

Re: Things I Don’t Know as of 2018

#94

Post by ogre_codes »

jodrellblank wrote: post #85
ericmcer wrote: post #61

Earlier quoted context omitted.

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.

I simply don't believe he lacks those skills. He says " Python. I feel bad about this one — I have worked with Python for several years at some point and I’ve never bothered to actually learn it. " 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…

> I suspect he is more capable than he's making out; politely talking himself down.

Why?

If you are heads down working on core Javascript technologies, why do you step over and dig into learning more than the basics of Python? Likewise most of these languages/ skills.

Re: Things I Don’t Know as of 2018

#95

Post by vncecartersknee »

watermelon59 wrote: post #34
nemo1618 wrote: post #17

I'd love to see lists like this from more high-profile programmers. What does John Carmack not know? What does Dan Bernstein not know? What does Bryan Cantrill not know?

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 :)

No one has ever really used the debugger at any of the c++ shops I've worked at almost exclusively logging. No one even knew how to get the build system to produce debug symbols at my last job.

Re: Things I Don’t Know as of 2018

#96

Post by ogre_codes »

jiofih wrote: post #52
ogre_codes wrote: post #31

Earlier quoted context omitted.

> you’ll most definitely need those when building actual products for the web. You should take a good look at who posted the article . Fundamentally, who he is and what he's done in the community is the context of the blog. Without understanding that, you miss the entire point.

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.

Not that I agree with your list of "essential" skills for a front end web developer. You are still missing the point.

Dan isn't a frontend engineer in the usual sense. He works on the underpinnings of the language, he's not building web sites.

Re: Things I Don’t Know as of 2018

#97

Post by ZephyrBlu »

valenterry wrote: post #90
ZephyrBlu wrote: post #88

Earlier quoted context omitted.

What's wrong with the design of Redux?

It is not composable. I.e. you cannot use one "redux-application" within another one. 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.

Why isn't possible to embed one Redux application into another? You can have multiple Redux stores so I don't see how Redux applications are unable to be composed.

I _think_ this demonstrates something similar to what you're talking about: https://redux.js.org/recipes/isolating-redux-sub-apps

I'm also curious which parts of Redux weren't executed well, especially considering how small the library is.

Re: Things I Don’t Know as of 2018

#98

Post by a4444f »

MeinBlutIstBlau wrote: post #22

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…

The older I am, the more experience I have, the harder i find landing a job. 10+ years of experience, multiple companies. Also, not that many techs/skills from earlier years are applicable now, it seems that there were couple of technology cycles since then, and more experienced persons may have no much advantage over younger persons.

If people you know do not know much, then the people you know do not know much, there are also people you do not know.

Re: Things I Don’t Know as of 2018

#99

Post by valenterry »

ZephyrBlu wrote: post #97
valenterry wrote: post #90

Earlier quoted context omitted.

It is not composable. I.e. you cannot use one "redux-application" within another one. 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.

Why isn't possible to embed one Redux application into another? You can have multiple Redux stores so I don't see how Redux applications are unable to be composed. I _think_ this demonstrates something similar to what you're talking about: https://redux.js.org/recipes/isolating-redux-sub-apps I'm also curious which parts of Redux weren't executed well, especially considering how small the library is.

Thank you for your link. I think the link captures it quite well. It says:

> These s will be completely independent. They won't share data or actions, and won't see or communicate with each other.

and

> This pattern is not recommended for parts of the same app that share data.

This is precisely where it gets interesting. Composition is important to combine things without these things knowing that they will be combined in advance and having to change them.

So imagine there exists a redux application that shows a dashboard which lists sales within a timeframe. Now I build a new redux application that wants to use two of the existing redux applications next to each other, using one to show sales for last year and one to show sales for this year, using the same timeframe (months/days) but for different years. This is a very very simple case of composition, but it becomes tricky fast.

Question: how do can I align the timeframes within the two sub-applications? I want to make it so that if the user changes the timeframe within one of the subapplications, it should translate to the other one and vice versa. Can I do this _without modifying the code of the sub-applications_?

Re: Things I Don’t Know as of 2018

#100

Post by krimbus »

a4444f wrote: post #98
MeinBlutIstBlau wrote: post #22

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…

The older I am, the more experience I have, the harder i find landing a job. 10+ years of experience, multiple companies. Also, not that many techs/skills from earlier years are applicable now, it seems that there were couple of technology cycles since then, and more experienced persons may have no much advantage over younger persons. If people you know do not know much, then the people you know do not know much, the…

> Also, not that many techs/skills from earlier years are applicable now, it seems that there were couple of technology cycles since then

Out of curiosity, could you elaborate on that?

Post reply on HN