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

181–190 of 226 posts

Re: Things I Don’t Know as of 2018

#181

Post by jtolmar »

mywrathacademia wrote: post #176
jtolmar wrote: post #51

Earlier quoted context omitted.

Here's some other senior dev's list: Don't know: start with Dan's list, it has many similarities. I know more Bash, but not enough to write a shell script more complex than my aliases file. I vaguely know z80 and 6502 assembly. I know Java extremely well, but am faking C++ and C#. I understand flexbox but not CSS floats. I don't even know what sockets and streams even are in this context, they don't sound like the so…

From your "do know" list you sound like a video game developer. I would think that a video game developer would be strongest in C++. Are you telling me your "do know" list is applied using Java?

Video games are a hobby, my day job is GPS algorithms. More of the list is relevant for those than you might think.

Most of my games have been done in Java or Javascript.

Re: Things I Don’t Know as of 2018

#182

Post by rpeden »

irq11 wrote: post #92
douglaswlance wrote: post #89

Earlier quoted context omitted.

He invented Redux, and is a core contributor to React.

Honestly, hearing that a core contributor to React doesn’t know much of anything about basic engineering topics is disheartening, not encouraging. Not memorizing the algorithm book is one thing, but being considered a “rockstar” when you don’t know basic sorting algorithms...

Consider that actual rock stars often aren't the world's best musicians from a purely technical perspective - but they're experts at delivering what their audience wants.

Dan made a bit of a name for himself in a couple of ways I can think of: creating a very popular library (Redux) and communicating extremely well in English about React and Redux.

"Able to communicate about with a broad audience about complex technical topics" is a skill I wish more developers had.

So he's able to create things his audience wants and then communicate to his audience about those things. Sounds exactly like a rock star to me.

That's meant as a compliment, not an insult. The ability to communicate well and the ability to be honest about you don't know are two things the developer community needs more of.

Re: Things I Don’t Know as of 2018

#183

Post by coldtea »

crimsonalucard wrote: post #67
jchw wrote: post #53

Earlier quoted context omitted.

>My "thing I dont know as of 2018", just for good measure: How to build complex front-end applications without making a complete mess of things! If you find anyone that truly knows the answer, please let us know :) I'm sure plenty of people claim to, and many more will just claim that the mere concept is flawed so there's no point, and there are even more non-answers. But the actual problem is very difficult. I remem…

There is a core issue with UI development that makes things harder and less elegant than the backend. It's the io loop. Components must change state and react to state. This where the complexity arises. If you remove the loop by having components only react to state, you will find your programs to be simple, modular and more beautiful. The feedback loop of IO destroys the functional and modular nature of UI. Function…

>however ui development is inheritly an object oriented problem due to the IO loop

There's nothing OO about the IO loop. The main thing that calls for some OO in UIs is the widget hierarchy.

Re: Things I Don’t Know as of 2018

#184

Post by leesec »

commandlinefan wrote: post #179
pelotom wrote: post #178

Earlier quoted context omitted.

The idea of Dan Abramov having trouble finding employment is beyond comical.

Well, I hope so - the author of Homebrew ended up having trouble finding employment: https://twitter.com/mxcl/status/608682016205344768 . Stranger things have happened.

Getting rejected from a single company does not constitute having trouble finding employment.

Re: Things I Don’t Know as of 2018

#185

Post by crimsonalucard »

coldtea wrote: post #183
crimsonalucard wrote: post #67

Earlier quoted context omitted.

There is a core issue with UI development that makes things harder and less elegant than the backend. It's the io loop. Components must change state and react to state. This where the complexity arises. If you remove the loop by having components only react to state, you will find your programs to be simple, modular and more beautiful. The feedback loop of IO destroys the functional and modular nature of UI. Function…

> however ui development is inheritly an object oriented problem due to the IO loop There's nothing OO about the IO loop. The main thing that calls for some OO in UIs is the widget hierarchy.

IO loop necessitates OO unless you do some obscure tricks like passing closures and using a global event emitter. The most obvious way to implement UI is to do OOP.

Widget hierarchy does not necessitate OO. Hierarchies can be built with plain data structures. OO comes into play when you place methods within the data structure. Methods coupled with data is essentially an object as described by OOP.

Why would you need integrate a method inside data structures?

Because IO.

Re: Things I Don’t Know as of 2018

#186

Post by mlevental »

yakshaving_jgt wrote: post #156
danabramov wrote: post #139

Earlier quoted context omitted.

Personally I’m not saying JavaScript “counts” as FP — which is why the post says “unless _you_ count”. ;-) But there are certainly FP subcultures in the JS community which only use the functional subset: https://github.com/jfmengels/eslint-plugin-fp https://github.com/fantasyland/fantasy-land https://ramdajs.com/ That subculture is what I was referring to. If you’re splitting hairs over such definitions without ackno…

Culture means different things to different people. If a candidate were to suggest they were only interested in the “pragmatic parts of FP”, implying that developing an understanding of category theory is somehow frivolous and not pragmatic (which I think you did earlier), I would acknowledge this as a poor culture fit.

you're arguing with the guy that built redux and he's being nice about it. you think maybe you should reconsider your position?

Re: Things I Don’t Know as of 2018

#188

Post by ryandrake »

erulabs wrote: post #45

This is an awesome article! I like the idea of being more forthcoming with what we don't know. > Containers. I have no idea about how to use Docker or Kubernetes. (Are those related?) I have a vague idea that they let me spin up a separate VM in a predictable way. Sounds cool but I haven’t tried it. > Deployment and devops. I can manage to send some files over FTP or kill some processes but that’s the limit of my dev…

I also admit that I still have no idea what a Kubernet is or what Docker and containers orchestration or any of those things are all about. I mean, I visited their web sites and read a few wikipedia articles. But I'm primarily an embedded/mobile guy and whatever problem space containers solve is something I've just never even remotely encountered.

Same with enterprise software development. It's kind of neat that the world of software engineering is so big that one can go 20 years into their career and be totally experience-deficient in large spaces of the industry.

Re: Things I Don’t Know as of 2018

#189

Post by acemarke »

askmike wrote: post #144
acemarke wrote: post #124

Earlier quoted context omitted.

Yeah, the docs can't solve everything, but I'm hoping we can improve the structure, the content, the reading flow, and how the prerequisite concepts are handled. As part of that, I definitely want to have new category sections on "Using Redux with a UI" (which would include both how that works in general, and specific pages for use with React, Angular, Vue, Ember, etc), and "Real World Usage" (which could cover thing…

> As for the "boilerplate" line... everyone throws around this word, and everyone means something different. Could you clarify what specific things you're thinking of when you say that? As stated before I haven't done a big JS project for about a year now. In the last project I did we used redux in a create-react-app. At the time the best practice was creating presentational and container components[1]. The biggest b…

FWIW, I've always felt that having duplicate / parallel "container" and "component" folders/files just for the sake of separating them is completely overkill. Most components are only connected once - just do that in the same file and export the plain and connected versions separately. I wrote some thoughts on that here: https://gist.github.com/markerikson/ea312b5ee398627ffceb09f8...

Similarly, I'm actually thinking that in the upcoming Redux docs revamp, I'd like to have the tutorials and examples switch from a "folder-by-type" approach to either a "feature folder" or even a "ducks" approach, and maybe even cut down on having separate action constant variables. There's valid reasons to do things in multiple files, but it's also not _necessary_, and I want to simplify things.

Yes, I totally agree immutable update logic is a pain to write and write correctly, which is why Immer is awesome, and why the starter kit uses Immer internally. My only concerns are that the code _is_ mutating unless you wrap it in RSK's "magic" `createReducer` utility that uses Immer, and it's going to be hard to figure out how to teach this properly. But, in terms of LOC and simplicity, it's a huge win.

Please let me know how well it works for you, and if you've got any other suggestions for what it should include!

Re: Things I Don’t Know as of 2018

#190

Post by acemarke »

pbowyer wrote: post #142
acemarke wrote: post #124

Earlier quoted context omitted.

Yeah, the docs can't solve everything, but I'm hoping we can improve the structure, the content, the reading flow, and how the prerequisite concepts are handled. As part of that, I definitely want to have new category sections on "Using Redux with a UI" (which would include both how that works in general, and specific pages for use with React, Angular, Vue, Ember, etc), and "Real World Usage" (which could cover thing…

> As part of that, I definitely want to have new category sections on "Using Redux with a UI" (which would include both how that works in general, and specific pages for use with React, Angular, Vue, Ember, etc), and "Real World Usage" (which could cover things like app structure, code splitting, choosing a side effects approach, and so on). Those new sections sound awesome! Kudos for thinking about adding them to th…

Sure! If you'd like to look at our plans and discussions, see these issues:

https://github.com/reduxjs/redux/issues/2590

https://github.com/reduxjs/redux/issues/3313

I'm particularly hoping to do some brainstorming about the revamped docs structure and content over the next couple days.

Post reply on HN