HN user

over190bpm

7 karma
Posts0
Comments6
View on HN
No posts found.

I could actually get almost all of the last third correctly by choosing the option that's the longest, has a semicolon, or a coma.

Aside from that, I didn't like that most of the words only had one or at most two definitions that sounded viable.

A lot of these words have either Latin or Greek origins, for most questions you can deduce the correct answer by asking the question: "Which of these would make sense to develop into a separate word through the mostly non-modern history of the language?".

I would enjoy it way more if all four options sounded equally viable, and I couldn't deduce the correct answer without actually being sure about the meaning of the word. I understand that coming up with choices like that for each question is way harder if you actually validate all of them manually.

I got a score of 76000 best estimate with 85 being correct, even though English is not my native language and I'm not that good at it.

My experience working on "medium sized" B2B apps in 10-20 people teams is that the cleanest way to design API-s is to have a regular REST API for the basic CRUD operations on the entities, and then have more specialized endpoints for specific pages, tables, dashboards etc. on top of that. Having specialized endpoints is kind of required, as the data often needs to be searchable, sortable, filterable and paginated, which would be pretty wasteful, or sometimes even impossible to do on the frontend. I find these kind of REST API-s pretty straight forward to design and implement for the most part, and as others pointed out, onboarding is extremely easy if the new developer on the team has worked in software dev at least for a year or two. This also makes it pretty easy and quick to transition to a fully public API if needed (although I have rarely seen this as a requirement).

Edit: fixed a typo.