How to make websites that will require lots of your time and energy
blog.jim-nielsen.com
How to make websites that will require lots of your time and energy
1–10 of 247 posts
Re: How to make websites that will require lots of your time and energy
#2On one hand I agree, one should approach issues as they come, but there's solutions that are hard to ignore such as the need for reusable fragments/components on different pages which already make a cry for dependencies.
Even admitting one wants to go with bare bone web components authoring and maintaining them is expensive, requires lit or something.
Thus, what's the solution? Some sort of templating? Again, you're bringing on dependencies.
Re: How to make websites that will require lots of your time and energy
#3I enjoyed the concept of "a complication step". Can't see the results of changes until my code has finished complicating.
Re: How to make websites that will require lots of your time and energy
#4On one hand I agree, one should approach issues as they come, but there's solutions that are hard to ignore such as the need for reusable fragments/components on different pages which already make a cry for dependencies. Even admitting one wants to go with bare bone web components authoring and maintaining them is expensive, requires lit or something. Thus, what's the solution? Some sort of templating? Again, you're…
I think the emphasis is in 'indiscriminatly'. The goal is not to have absolutely zero dependencies, just don't depend on dependencies that you could reasonably implement yourself.
A classical example might be https://www.npmjs.com/package/is-odd
Re: How to make websites that will require lots of your time and energy
#5The problem isn't the tool or the dependency—it's the developer's temptation to over-engineer. We grab a framework because we lack the discipline to keep something simple. Is self-control in coding just a lost art now?
Re: How to make websites that will require lots of your time and energy
#6On one hand I agree, one should approach issues as they come, but there's solutions that are hard to ignore such as the need for reusable fragments/components on different pages which already make a cry for dependencies. Even admitting one wants to go with bare bone web components authoring and maintaining them is expensive, requires lit or something. Thus, what's the solution? Some sort of templating? Again, you're…
> but there's solutions that are hard to ignore such as the need for reusable fragments/components on different pages which already make a cry for dependencies.
honestly ctrl+c, ctrl+v of hand written html. and i'm cool as a cucumber.
Re: How to make websites that will require lots of your time and energy
#7On one hand I agree, one should approach issues as they come, but there's solutions that are hard to ignore such as the need for reusable fragments/components on different pages which already make a cry for dependencies. Even admitting one wants to go with bare bone web components authoring and maintaining them is expensive, requires lit or something. Thus, what's the solution? Some sort of templating? Again, you're…
> Thus, what's the solution? Some sort of templating? Again, you're bringing on dependencies.
If your "dependency" is yourself because you wrote your own template for your specific needs, is that still a dependency?
I wrote a templating solution for my own repeated sections and I'm so glad. It does exactly what I need, it's simple for me to understand if ever it grows large and I need a refresher, and easily expandable.
Re: How to make websites that will require lots of your time and energy
#8We are good at not even getting that far. Have a platform team and spent a month setting up CI, github repo, onboarding, writing terraform and stuff and not even get around to doing a web site in the first place!
Re: How to make websites that will require lots of your time and energy
#9Gacha Web!
Finally we have our web 3.0!
...
Re: How to make websites that will require lots of your time and energy
#10I don't see the value in posts like this. It's just a random list of things that can go wrong in software projects, with no discussion of trade-offs at all. Where's the engineering?