https://github.com/cdr/code-server
I've been using it for the last couple of weeks on a development VPS and really love it. I'm considering moving my dev environment over to the server and just open a browser to do all the work.
472 karma · joined October 28, 2018
https://github.com/cdr/code-server
I've been using it for the last couple of weeks on a development VPS and really love it. I'm considering moving my dev environment over to the server and just open a browser to do all the work.
"Does these scores correlate to scores 10 years later/etc, or should we expect these children to recover?"
It may sound like a silly comparison, but puppies need to be challenged and introduced to experiences in the first weeks as there is a limited window of opportunity to stimulate neural development which results in brain development. During the first eight weeks of age, skills not acquired may be lost forever.
Maybe similar to how children can easily pick up a (new) language, but learning a language at a later age is a real struggle.
“It’s not subtle by any stretch,” said Deoni. “You don’t typically see things like that, outside of major cognitive disorders.”
I think we vastly underestimate the severe long-term effects of lockdowns.
https://www.theguardian.com/world/2021/aug/12/children-born-...
- The immune systems of more than 95% of people who recovered from COVID-19 had durable memories of the virus up to eight months after infection.
- The results provide hope that people receiving SARS-CoV-2 vaccines will develop similar lasting immune memories after vaccination.
They are covered under https://www.hrsa.gov/cicp Which has notable differences (worse) in injuries covered, appeal possibilities and benefits. Differences: https://www.hrsa.gov/cicp/cicp-vicp
The setup :
- Distributed file system using GlusterFS
- DNS load balancing using Amazon Route 53
- PostgreSQL HA clusters using Patroni
- A WireGuard mesh topology between all instances.
Even though it was much fun setting this all up, the ballooning complexity of all this outpaced the benefits and it felt more fragile than where I came from. I decided to just scale vertically and keep it simple.
Most of my refactoring these days is coming up with more simple, more manageable solutions.
Vuex, the goto state manager just wasn't built for it (I ended up using vuex-module-decorators). Type safe templates were only partially possible with Vetur (vs code extension) but it was slow and resource hungry. I'm sure in Vue 3 this is much better now, but while evaluating to migrate to v3 this wasn't the case.
I became interested in React, because I was looking for a way to generate type safe email templates. Started using .tsx files with a library called typed-html and loved it so much that I end up migrating to React (now rendering email templates with ReactDOMServer.renderToString(element).
Still miss Vue's simplicity at times but having rock solid TypeScript support is something I value more.
I do believe this request was pushing the legal boundaries as the law describes the request should be as specific and narrow as possible [0]. (with "as possible" being a rather big loophole)
(Dutch)
[0] https://maxius.nl/wetboek-van-strafvordering/artikel126nd
[1] https://maxius.nl/wetboek-van-strafrecht/artikel184/lid1#:~:...
Stuff like this really hinders adoption.
I'm personally a huge proponent of End 2 End Testing. You can think you covered everything in isolation, but the user is presented with bugs nonetheless. I have near 100% E2E test coverage. Yes it takes time to run, yes third-party integrations can result in failed tests. (Which probably signal an issue with you or your third-party anyway). I believe a full E2E test requires less maintenance and has a broader coverage than Unit Tests.
For instance I run TestCafe E2E tests that tests all possible user interaction from signup and paying for a subscription to account termination. I go as far as reading expected emails through a web email client and verify the content in the received email using TestCafe. I test cache invalidation, a host of automated member expiration, warning and authentication / security scenarios. All this should be done anyway, why not do it using E2E tests. I did a rewrite, switching from Vue.JS/SSR to React on Next.js I had only minimal code changes to my E2E tests. And with minimal I mean a couple of ID/Class DOM references to account for different components in Vue vs React.
Not only do you test code paths, but also all your components in the stack and the interaction between them, which for me are Node.js, Nginx, PostgreSQL, Redis, Amazon SES, etc. If something fails, you will have to do some digging, more so than a failed Unit Test. But more often than not you know what has recently changed and so where to look for possible issues. Your E2E tool makes a screenshot of the browser fail-state often highlighting the issue at hand.
Of course these types of tests work best on websites, and not so great on say low level GPU driver code. They may also become to cumbersome and slow on highly complex sites. The biggest drawback is probably the time it takes for a full test run which in my case can take up to 20 minutes in a headless browser.