HN user

zcmack

50 karma
Posts0
Comments30
View on HN
No posts found.

Eventually, humans are going to get used to the constant spam and start mentally tuning out these hyper personalized initiatives.

haven't we already been doing this since email templating was a thing?

i share some of this sentiment as well and i think a lot of my hesitance is that these solutions seem born of the popularity of rust. we have had c and c++ for as long as javascript has been a full-stack workhorse. is it just the barrier of entry / novelty of rust has prompted longtime js devs to make the leap into building tooling? along with it, it seems the "new framework every week" jab at javascript can be applied to the build system as well. in any case, i welcome the speed improvements and this certainly does not preclude me from using these new tools where i'm able.

i completely agree. use the right tool for the job. if you need significantly dynamic content, you should consider another framework such as rails (as the author indicates).

if netlify is being portrayed as the only platform to deploy a statically generated site from git commit, then i suppose yes, the sane defaults of these frameworks are not the right tool _for you_.

it is very sad. i personally would much rather someone walks through their problem solving approach and identifies shortcomings/edge cases than to regurgitate a memorized algorithm.

it's really easy to identify code that is not optimal at code review time. it is far more challenging to have a conversation with a algorithm-regurgitating robot that their entire approach was wrong because they misunderstood the abstraction or that their code wasn't needed because Larry is refactoring that part of the system to a separate service already.

i think TDD is a great method, but not dogma. likewise with code coverage. being prescriptive about one or the other just leads to angry people who get fed up with the principle and rebel.

don't know much about fly.io, but i would have definitely deployed my go binary + caddy w/config in a container, rather than setup a systemd service on the host. just me?

the keyboard is so small, why not just use your cell phone? yes your on screen keyboard is far from ideal but it has already built some muscle memory. typing on a tiny keyboard with a non-standard layout is just painful.

in my experience, having access to the aws dashboard rarely indicates mastery of the platform and knowledge of which tool is best for the job. it is incredibly common to lift and shift on premise workloads to ec2 with an rds instance to save the cognitive load of application refactoring. this creates a different flavor of infrastructure complexity without taking full advantage of the services on offer.

i almost bought a Kobo earlier this year but talked myself back into the Kindle ecosystem just for whispersync. while i vastly prefer reading on the kindle itself, i do often find myself reading on my phone during unexpected downtime. MOBI sucks but even self-converted epub MOBI seamlessly syncs progress.