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

101–110 of 226 posts

Re: Things I Don’t Know as of 2018

#101

Post by InGodsName »

ritchiea wrote: post #95
InGodsName wrote: post #91

It's on tangent but I owned an agency before and my employees under NDA wrote opensource projects for celebrity developers. It was effectively a GhostCoders for hire service. Out of them a few developers got very popular. It was a matter of luck more than anything. Anything can catch wind anytime, we just needed to keep up with the trend. One way to catch this is coding style. Since, we employed GhostCoders - style v…

How effective is an NDA in this case? A lot of NDA's are effective because BIGCO you signed the NDA with has piles of money & resources to sue you. If a developer is ghostcoding for ROCKSTAR and it gets out ROCKSTAR hires ghostcoders. ROCKSTAR is screwed and maybe he was making pretty comfortable money at BIGCO but his pockets are exponentially smaller than BIGCO's. And he doesn't have a legal department to handle th…

1. Yea, we had a law firm on contract.

2. We didn't hire contractors, they are employees and have more skin in the game.

That said, no employee ever went on Twitter or court.

Re: Things I Don’t Know as of 2018

#102

Post by danabramov »

alexdowad wrote: post #80
pepijndevos wrote: post #69

What I miss from this article is what he does know. Not to boats, but to contrast. I know some of the things he does not know, and I'm sure he knows things I don't know. But without knowing what his expertise is, it's easy to think you know more than him.

This. Never heard of Dan before today. Now he is "a guy on the Internet who writes about programming but doesn't know much about it".

Hi, author here.

Maybe you can read some other articles on the blog (it’s new so there’s not many) to get a sense of my interests.

I also have a StackOverflow profile: https://stackoverflow.com/users/458193/dan-abramov

Re: Things I Don’t Know as of 2018

#104

Post by gbear605 »

yesenadam wrote: post #100
Vinnl wrote: post #72

Earlier quoted context omitted.

I think the assumed background for the reader is knowing who Dan Abramov is - he's the guy who started Redux, and is currently on the React team. The rest of his blog so far is basically about things he does know.

In the spirit of this page: I don't have a clue what Redux or React are.

React is an extremely popular web front end library developed primarily by Facebook. Redux is an important library commonly used with React.

Re: Things I Don’t Know as of 2018

#105

Post by tashoecraft »

jchw wrote: post #53
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…

>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…

You definitely aren’t restricted to lazy loading when using RouterModule.forChild, idk where you got that, just define a module, add forChild with your routes, and import it into another module. Im doing this all over our codebase.

I can understand you’re opinions about the module system, but I disagree. For a small to medium size app it can seem like annoying boilerplate that gets in the way. If you’re working on a large app across multiple teams then it’s very helpful. You have a single entry point for all relevant code. You can define the api for that module so other teams don’t misuse what you have built. It can get frustrating when you have a single component that you want to share and you need to wrap it in a module, that feels very unnecessary, but I know the angular team is working on that.

I actually really like that my components are in the dom, I can see clearly where it is, not which div with which class or Id it is. It makes inspecting the tree very easy.

RxJS can be difficult and hard to learn, which doesn’t help that the docs are meh and you can never find exactly where to go. Juniors really need someone to help them not leak subscriptions. Though if you follow Angulars promoted idea of using the async pipe, then that will automatically clean up your subscriptions. Again, for small components/apps it feels way overkill, but it feels oh so nice when your trying some complex async stuff and can handle it and pass it along so easily.

Re: Things I Don’t Know as of 2018

#106

Post by [deleted] »

mettamage wrote: post #37

I would like a list to see what he does know, according to himself. Somehow I get giddy making a comparison between what he knows and doesn’t know. I want to make a mental model of what a real dev looks like, even if it is a biased one.

[deleted]

Re: Things I Don’t Know as of 2018

#107

Post by azizinnnjo »

I very much enjoy working as a programmer, but, to be honest, there is constantly a little anxiety in the back of my mind that I do not get FP/docker/devops/insert-latest-buzzword-here enough not to look like a clueless coder in a watercooler-side chat with a fellow. So I really appreciated this article, it made me feel better about myself :-)

Re: Things I Don’t Know as of 2018

#108

Post by commandlinefan »

azizinnnjo wrote: post #107

I very much enjoy working as a programmer, but, to be honest, there is constantly a little anxiety in the back of my mind that I do not get FP/docker/devops/insert-latest-buzzword-here enough not to look like a clueless coder in a watercooler-side chat with a fellow. So I really appreciated this article, it made me feel better about myself :-)

It’s deeper than that - you won’t just look like a “clueless coder”, you’ll find yourself unemployable. I learned early on that it doesn’t matter what credentials you have or how much experience you have, never admit there’s anything you don’t know, or they’ll pass on you to hire somebody else who confidently insists that he does know absolutely every single thing there is to know. I feel bad for the author of this piece, because putting his name to this _will_ cost him employment at some point in the future.

Re: Things I Don’t Know as of 2018

#109

Post by tokyodude »

commandlinefan wrote: post #108
azizinnnjo wrote: post #107

I very much enjoy working as a programmer, but, to be honest, there is constantly a little anxiety in the back of my mind that I do not get FP/docker/devops/insert-latest-buzzword-here enough not to look like a clueless coder in a watercooler-side chat with a fellow. So I really appreciated this article, it made me feel better about myself :-)

It’s deeper than that - you won’t just look like a “clueless coder”, you’ll find yourself unemployable. I learned early on that it doesn’t matter what credentials you have or how much experience you have, never admit there’s anything you don’t know, or they’ll pass on you to hire somebody else who confidently insists that he does know absolutely every single thing there is to know. I feel bad for the author of this p…

I've gotten hired or an offer several times admitting I don't know something. I don't think I'm an exception

Re: Things I Don’t Know as of 2018

#110

Post by heydonovan »

Aeolun wrote: post #57
heydonovan wrote: post #41

After reading this, I feel like I've imposter syndrome as well. I know about 80% of those topics pretty well, but I don't think I could ever get a job as a junior dev. Maybe I focus too much on learning things that interest me, and not enough on things that land you that software engineer title.

So the main thing you are missing is the actual coding?

Hah! Probably. I'd rather learn about distributed systems, the idiosyncrasies of bash, how file systems work, dive into how http/2 & ipv6 will solve some of our problems, etc. Absolutely love fixing bugs in code though, but the actual act of coding an application from scratch bores me. Can't explain it!
Post reply on HN