Live data from Hacker News

Advice to Young Web Developers

tumblr.beesbuzz.biz

131–140 of 328 posts

Re: Advice to Young Web Developers

#131

1) Nobody has any idea what they're doing 2) If you think you know more than your manager – you are absolutely right 3) HN is 3 years ahead of mainstream, but 10 years behind the edge 4) React was made by an OCaml programmer 5) if you want to be that good, learn emerging languages (all of them) 5) don't optimize for money too soon, if you follow these instructions you will quadruple soon enough 6) Whatever your probl…

what / where is "the edge", in your mind?

Re: Advice to Young Web Developers

#132

1) Nobody has any idea what they're doing 2) If you think you know more than your manager – you are absolutely right 3) HN is 3 years ahead of mainstream, but 10 years behind the edge 4) React was made by an OCaml programmer 5) if you want to be that good, learn emerging languages (all of them) 5) don't optimize for money too soon, if you follow these instructions you will quadruple soon enough 6) Whatever your probl…

What is your reasoning behind the recommendation to learn Clojure? I am generally unfamiliar with it but saw it was a general purpose language. What makes it so valuable to be included in your list?

I'd think anything in the LISP family would qualify

Re: Advice to Young Web Developers

#133
post #42
post #25

There are two that stand out to me: > Always validate your data server-side; anything that comes from the client is suspect. At least sanitize in a way that won't break the server but will throw an error. For internal applications and side projects it's ok to just respond with a 40X or a 50X and move on. > To the developer, “isomorphic” code breaks down the barrier between client and server. "Breaks down the barrier"…

OTOH, if you use Flow or Typescript, it is amazing to be able to share type-safe interfaces across the stack (not code). I suppose you could get this from any compiled-to-JS language too.

100%

Re: Advice to Young Web Developers

#134
post #132

Earlier quoted context omitted.

What is your reasoning behind the recommendation to learn Clojure? I am generally unfamiliar with it but saw it was a general purpose language. What makes it so valuable to be included in your list?

I'd think anything in the LISP family would qualify

You must understand the point I am missing. Why learn a language in the LISP family as a young developer? Does it somehow improve you overall?

Re: Advice to Young Web Developers

#135
post #34
post #20

I feel like posts like this are just somebody missing the web how it used to be. I mean the Web IS an app platform now.

I didn't get that sense from the post. I took that they were advocating for basic HTML/JS when appropriate. A reminder that it's still a valid way of doing things. If you're building an app, yeah use React. If you want to put some contact info on the internet, there's no reason it can't be vanilla HTML. Or at least that's how I read it.

you could also use gatsby to generate static sites in that case -- imo react offers enough developer quality of life features where it's pretty hard to justify not using it

Re: Advice to Young Web Developers

#136
post #132

Earlier quoted context omitted.

I'd think anything in the LISP family would qualify

You must understand the point I am missing. Why learn a language in the LISP family as a young developer? Does it somehow improve you overall?

Once you have grokked Lisp, everything else feels weak by comparison, as I understand it.

Mostly the appeal is how easy it is to extend the syntax (because there is barely any syntax at all).

Disclaimer: I have written a good hunk of Emacs Lisp and also written Scheme professionally, but I have yet to grok macros.

Re: Advice to Young Web Developers

#137
post #86

Earlier quoted context omitted.

How would the site we’re communicating on right now be improved if it were rebuilt as an SPA?

Threading could be clearer. Less data would need to be loaded on each page load. I can imagine that a lightweight SPA to handle the a few standard views (e.g. listItems, itemDetails, profile, changePassword, submit) would cut down data transfer by a significant margin (20-30%, maybe more). The UI could also be much better on mobile, and we could give users the option to cache certain pieces of content offline.

Offline use already works great, unlike in any SPA I've ever used.

1) Load the page.

2) The page is now fully loaded and ready for reading without any need for further network requests.

For even more offline use, try printing it! HN threads work superbly when printed, again unlike most modern sites.

Re: Advice to Young Web Developers

#138
this article feels lacking in nuance, strong claims that aren't universally true lead to bad reasoning.

to any "young developers" read I would say not to blindly adopt these opinions without understanding them.

Re: Advice to Young Web Developers

#139
post #131

1) Nobody has any idea what they're doing 2) If you think you know more than your manager – you are absolutely right 3) HN is 3 years ahead of mainstream, but 10 years behind the edge 4) React was made by an OCaml programmer 5) if you want to be that good, learn emerging languages (all of them) 5) don't optimize for money too soon, if you follow these instructions you will quadruple soon enough 6) Whatever your probl…

what / where is "the edge", in your mind?

it’s a git repo sitting unused on some 20-something’s laptop, because anybody rich enough to market it doesn’t know enough to recognize it

Re: Advice to Young Web Developers

#140
post #41

Earlier quoted context omitted.

You mean the specific experience when back buttons aren't working? Or when urls don't make sense? Or when you can't just share the content by copying the url because it no longer identifies the conten? Or when you can't say if something is loading, missing, or broken? This is my user experience with SPAs regarding navigation.

If an spa is behaving like that, the coders have failed at their job.

"PHP is fine, it's just poor developers making bad sites".

And then people stopped using PHP.

Post reply on HN