5,743 karma · joined March 2, 2011
jacob@jacobrask.net https://github.com/jacobrask http://twitter.com/jacobrask
Gothenburg, Sweden.
* designers
* QA
* tech lead
* senior developers
* delivery lead
Is this because of my biased experience with consensus culture, or is the article a simplification?Also, an Engineering Manager would typically decide which technical experts are suitable for a given task, but would not be the one deciding which tech to use, apart from budget constraints.
Also don’t forget to check actual conversion and other important metrics for different browsers, not only number of visits.
Is there something like an Open Routing project where this dynamic data would make more sense than in OSM?
It’s useful if you need to call an API from the client in a Next.js application but modify the data first, or call multiple endpoints without introducing a waterfall to the client. What you described can be used in a similar way for filtering and processing etc, but only for the initial page load.
The dilemma is the balance between doing work that matters, maybe finding something where I care more about the outcome, or learn to brush things off and focus on other things in life that matters.
It’s of course tragic when parents make a bad position even worse, but addiction is a symptom of poverty and not the cause.
This was not really true back when browsers allowed sharing caches between domains because of different versions and fragmentation of CDNs, and is definitely not true now when a.com and b.com would not share a cache for skypack to avoid fingerprinting.
Most people also survived driving without a seatbelt before it became illegal.
Just because something is not dangerous or damaging in 100% of cases does not mean it’s not problematic or should not be made slightly less convenient to access. That prevention is not 100% effective also does not mean it will have 0 positive effect.
I’m still against age filters like this though, because they tend to also block access to legitimate sex education and info about HBT issues that can be life saving for teenagers.
- Code sharing - how do you share reusable snippets of code that includes both the SSR logic and the JS that is also required on the frontend. React’s component model is fantastic where a team can develop a component independently
- Skill set - getting 50 React developers to write HTML and JS should be fine if other problems were solved, but often the suggested solution is obscure things like Elm or Elixir
- Even if most of what a company builds is static marketing content, other parts can be more app-like and having developers be able to share code and use the same basic technology is a great productivity booster
There’s support for mocking in Node as well for SSR and jsdom tests.
I assure you that those of us who work on projects where this would not work are not simply bad at naming things and that’s the only reason we picked component based styles.
To me this invalidates SSG for any busy site with a somewhat large menu. Any time you change the order of some options or rename an item, everything needs to be rebuilt.
If you combine it with something like Edge Side Includes it could work I guess, only rebuilding the part if the page that’s needed.
I’ve been on parental leave myself and my small employer hired a replacement, and by the time I got back we were both needed because they ran a successful and expanding business.