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

How to make websites that will require lots of your time and energy

blog.jim-nielsen.com

Post reply on HN
Print view View original

241–247 of 247 posts

Re: How to make websites that will require lots of your time and energy

#241

Post by brokegrammer »

austin-cheney wrote: post #240
brokegrammer wrote: post #238

Earlier quoted context omitted.

I would love to see some numbers then. Until then, I'll just assume that using build tools and frameworks means one is a junior developer to be bogus claim.

> I would love to see some numbers then Nobody is stopping you from gathering numbers. Again, that is the difference between an actual engineer and a junior developer.

Engineers who speculate about currently non-existent metrics instead of getting work done while shaming others for wanting to make progress should look for employment in academia.

Re: How to make websites that will require lots of your time and energy

#242

Post by martin82 »

superasn wrote: post #38

Always use ORMs and then spend the next year debugging N+1 queries, bloated joins, and mysterious performance issues that only show up in prod. Migrations randomly fail, schema changes are a nightmare, and your team forgets how SQL works. ORMs promise to abstract the database but end up being just another layer you have to fight when things go wrong.

Skill issue.

In the hand of a good team, ORMs and migrations are an unbeatable productivity boost.

Django is best in class.

Re: How to make websites that will require lots of your time and energy

#243

Post by teddyh »

brokegrammer wrote: post #232
teddyh wrote: post #220

Earlier quoted context omitted.

Every pinned dependecy is a security vulnerability, sooner or later.

Once a dependency turns into a security vulnerability, you can either replace it, or write your own library like I suggested. It's more cost effective and time efficient than writing your own libraries from scratch for every project. For example, I'd rather install React Router for routing in a React app instead of writing my own routing library. I guess some people will reply "grrr React, just use static HTML bro".…

> Once a dependency turns into a security vulnerability

How will you know if/when that happens?

Are you subscribed to the development channels of all your dependencies? Do you examine every one of their commits for security fixes?

Re: How to make websites that will require lots of your time and energy

#244

Post by Bigpet »

victorbjorklund wrote: post #200
Bigpet wrote: post #70

Earlier quoted context omitted.

I don't think you're arguing against anything that was said in that post. There was never an "at all cost". The author was hedging even in the headlines ("indiscriminately", "before you know you need one" and "always, always").

Have a hard time imagine when you would benefit from just html files (unless it is literally a one pager that will never change)

You make it sound like there isn't a very wide range of solutions between "just write html files" and "use a complete website framework". There's a space in there where a large percentage of web projects used to be located in.

Re: How to make websites that will require lots of your time and energy

#245

Post by johnisgood »

epolanski wrote: post #207
johnisgood wrote: post #68

Earlier quoted context omitted.

That is why you can include a header.html, nav.html, and footer.html if you so wish! There are many ways to do this. :P Depends on your use case.

And then you need a dependency to glue them together...And now you want to provide data..And now you want to put content in children. And you went from a simple nginx extension to again full blown software.

I said it depends though. You could easily do this or some of it in an nginx config using OpenResty or nginx + Lua extension.

Re: How to make websites that will require lots of your time and energy

#246

Post by deterministic »

Don't use code generators to automate 90% of your code.

Hand code everything, including the protocol encoders/decoders, dialogs etc.

Use a framework that is brand new and full of shiny new bugs you can spend months of enjoyable time fixing, until the framework is dropped by the developer(s) and you can recode everything to the next new and full of shiny new bugs framework. Repeat infinitely.

Also pick a shiny new programming language FooBar, to write both the server and client, that "really soon now!" will have all the libraries and bug fixes you need to use it in production. Spend time writing all the missing libraries and contributed it to the 5 other developers using the language. Spend hours complaining on HN that other developers are too stupid to realise the obvious benefits of rewriting everything in FooBar.

Re: How to make websites that will require lots of your time and energy

#247

Post by cdaringe »

austin-cheney wrote: post #219
rckt wrote: post #33

The post feels more like a rant, like the author has a beef with some sort of a project or a client. Even a static blog is easier to manage with tools rather than writing it in pure HTML. I have my personal website running on svelte. When I decided to have a blog, I quickly came up with a solution to use markdown to html converter and just added a couple of routes to existing setup and voila, the blog is up and runni…

No it doesn’t. This post reads like someone tired of working in an industry run by extremely insecure people that just need a little help at absolutely every step of the journey. Other industries call that unqualified .

Seems like you’re projecting, to me.
Post reply on HN