I once reported this kind of interview scam repository with the full backstory and explanation why I was reporting it and Github's support asked for a proof that it was a scam. As if I was supposed to do the detective's work. I just wrote back to them that they can do whatever they want with it as I've done my part.
The incentive is in delivering first. When the free market saturates and profits are razor thin due to extreme competition, first movers always get the rewards of innovation
Counter: Netscape vs Internet Explorer. Netscape had a year lead, but it's hard to compete when Microsoft decided to bundle IE for 'free'.
If profit margins are razor thin, the Apples and Amazons and Microsofts of the world can happily copy an idea and hold their breath far longer than a smaller competitor can.
Role playing using common sentences is the best way to learn ANY language.
Start with a taxi lesson so you can move everywhere. Then a restaurant lesson so you can order from any menu at least the meals you like. Then a grocery shopping lesson. That'l cover 50% of your basic tourist needs. Then meeting people, elevator, bus, just remember the most important words 'sumimasen, onegaishimasu, kudasai, hajimemashite, arigato' and you'll be welcome everywhere you go.
20 years ago I saw the greatness of xml and xslt as I was coming from the painful inferno of an EDI shop. There is nothing more beautiful than sending plain data to a client and being able to see the whole document without any extra bloating, that's what XSLT was intended for:
That piece of data would be sent to millions of customers and they could open it and the XML was transformed in an invoice perfectly formatted for human consumption. Both flesh and silicon were living happy in perfect harmony.
Then it came SOAP and all the corporate suits and messed it all up into an extra complicated bloatness of anguish and suffering, but XML/XSLT were beautiful on their own (for data transformation, not web pages)
If we extrapolate it all to JSON, all we need to do is add two lines to the data file to reference the JSLT source and then use any templating system as default (ejs, mustache, handlebars) to do the transformation in the browser
! important thing to do
~ something already started but not finished
- thing to do
- another thing to do
x something done
x already done
? needs more thought
Been using it for the past 35 years, once I start a project I create a todo.txt file and start adding items, create logo, create database, etc
I think you're misreading the comment. The reasoning isn't missing, it's implied by decades of good design principles: simpler is better. A normal developer would intuitively prefer <output>, so the question isn't "Why suggest <output>?" but rather "Why is <output-format> necessary?"
And in the context of LLMs, this isn't just a matter of aesthetics. More verbose tags mean more tokens, and more tokens mean higher costs. It's a perfectly valid and practical piece of feedback.
I like it but I'd like to see images right in your page instead of going to an external website which sometimes is not even dedicated to stained glass making hunting for visual gratification really painful.
So, I'd add more visuals to the main page just like on your 'search' link, move the map to the bottom, let visitors know of every new location to keep them engaged and coming back for more, make a gallery sorted by most liked, viewed, commented, valuable (subjective based on history, cost, location, etc)
Be polite, say no, move on.
* I wish linkedin and github were more proactive on detecting scammers