Location: Manila, Philippines
Remote: Yes
Willing to relocate: Yes
Technologies: Fullstack Javascript; NodeJS, React/Native
Resume/CV: Available upon request; LinkedIn can be provided as well
Email: [email protected]
One particular use case that I might try this for is for (very) restrictive environments. One such case was with my previous work where we had to develop services for the client but we can only do it in a remote desktop with certain network and application restrictions. Instead of having conditions for the environment to load certain config, we can simply retrieve the secrets stored in AWS (ex. RDS credentials) via the agent.
It really should not happen, especially for fully remote teams and/or companies.
Current company has built a comprehensive career management that encompasses even remote workers. It's a very objective and simple approach. The challenge comes with crafting KPIs with each employee as basis for promotions, but so far it has been paying off.
jQuery changed the game for frontend web development. Instead of static pages on the browser, interactivity for the client-side proliferated because DX on top of jQuery was way better. Then they started cursing jQuery for its limitations.
Then came React -- which again changed the game for frontend web development. Instead of wonky scripts and targetting CSS classes, you get a modular and reactive approach in building the web. Then they started cursing React because of performance issues and implementation complexities.
Svelte was designed to behave like React but perform better and reduce the implementation complexities. I had the chance to work with Svelte 1 back then and as a React developer, it would really make you think "Why did React do that?".
This is probably on top of HN because people loved Svelte too -- but some followers are now questioning the direction as this change is gravitating towards solutions that React already implemented. As it happens, React did solve a lot of problems for the frontend, and they really nailed it.