3,451 karma · joined February 27, 2010
Also, check out my Hacker News app https://hackerwebapp.com/
cheeaun.at.hn
---
meet.hn/city/sg-Singapore
Socials: - github.com/cheeaun - linkedin.com/in/cheeaun
Interests: Web Development, Open Source
---
- does the company provide the harness and specific model for this? Or the interviewee use whatever they have access to? If they don't do a good job, is it the fault of the harness or the model or the interviewee not knowing how to fully utilise the harness and model or alternative harnesses and models?
- if every interviewee uses different harnesses and models, how does the company ensure that it's a fair comparison between interviewees for the same role?
- will the interviewer go through all lines in the code generated or let AI do it?
HTML5 Shiv was needed, with added history https://www.paulirish.com/2011/the-history-of-the-html5-shiv... (2011)
> Unfortunately, making range requests in 80 GB files just doesn't work in production. It is fine for files smaller than 500 MB, but it has terrible latency and caching issues for full planet datasets.
Wondering which part incurs the latency here.
Remote: No, negotiable
Willing to relocate: No
Technologies: JavaScript/TypeScript, HTML, CSS, React, React Native, Node.js, Deno
Résumé/CV: https://docs.google.com/document/d/1kdfbN02qEBhfzSTJWmkn_JMD...
Email: cheeaun(at)gmail.com
Happy to answer questions and hear feedback.
Disclaimer: I maintain node-hnapi since 2011.
I’m not really sure if there’s a limit per user. It’s still beta and I can’t or don’t dare to increase the quota for now.
There's a limit of 250K "3D Tiles renderer requests per day" so it'll stop serving tiles if exceeded.
I've personally seen many (junior) FE engineers decide to switch to BE, "full-stack", data or devops (or even design) because of how messy FE can get.
I know it's a lot of things (organization, management, people issues, expectations, etc) and this is basically just what I observe in Singapore. Could be different in other cities/countries.
1. Job descriptions and interviews now are skewed towards "full-stack" or backend. Most interviews are lacking or outdated due to the fast and volatile nature of FE.
2. Literally no career progression if you're specialised in FE. Most BE or "full-stack" devs will be given a chance to become principal engineers, tech leads, engineering managers, CTOs, etc. I've seen folks with "FE Team Lead" titles but never goes beyond that.
3. FE is a subconsciously looked-down field. Neither a designer nor an engineer. Product/design team won't involve you in meetings (but will treat you like a code monkey). BE/"full-stack"/API engineers will think your job is easy and keep throwing business logic stuff to FE.