Recently, I was screen-interviewed for coding speed with a fairly easy project. The company used a 3rd party platform which gave me 90m to complete 4 levels, each one building upon the other.
I think that was a nice test, but the platform is too buggy to recommend.
One tell is: if you can code that hero there's no excuse for the silly bugs.
For example, the hero is fairly impressive in mobile but it's broken in desktop. And then you scroll down to the next section and there's overflowing text.
Just so I understand what you are asking about. You have a ESI chunk which is a cache miss and the backend is fetching it, but you want the delivery of this specific chunked to have a streaming delivery?
> In contrast, bug reports to a typical end-user application go into a black hole from the moment they’re submitted.
True, but not always, I've heard PMs saying: "this was a user-submitted bug", meaning you better fix this ASAP.
But yes, for the most part they don't like it. I recall reporting a bug and then they obfuscated their SPA bundle.
Funny enough, today I spent like an hour thinking: should I report this, should I ever report bugs at all. It was a P0 but I didn't report it, and I noted it as my first time considering giving up on my career.
Last week I reported a list of medium-bugs and I ended with: "I'm not sure if you'll ever read this, so I'm not adding more details that could help you debug, but feel free to reach out…" They responded: "We will share this feedback with the appropriate team. No further action is required on your end. Your ticket 124443 is solved. Please rate us!"
> I've heard PMs saying: "this was a user-submitted bug", meaning you better fix this ASAP.
There are certainly developers with a practice of triaging and action user-submitted reports, but unfortunately it’s opaque to the one who reported it.
> fetch, XMLHttpRequest : Nothing — these are the ones everybody checks.
That's one of the things I don't like about security scanners, they just check for fetch and friends, and without context, they downgrade your security score.
For example, I have a fully local client-server package that makes no external requests but it gets flagged with "Supply Chain Risk" because it uses `fetch`.
One project is a proportional coding font, Camelana, which has left-padded uppercase letters when they are part of a camel case identifier.
Also, it has custom ligatures. e.g. the keywords ‘return and ‘throw look like a sticker with a solid background, so it is easy to spot exit points.
https://github.com/ericfortis/camelana
Another project is TabularEye, which renders some code blocks in columns without editing the whitespace.
https://github.com/ericfortis/tabular-eye
And other little projects like that
reply