_xhok

REST has the same problem as object oriented programming. It's too skeuomorphic. Lots of web applications are wrappers around conceptually monolithic resources, so it's convenient to use a protocol that makes that assumption. But as soon as you need to nest resources, or perform some action that has nothing to do with CRUD, or do just about anything interesting, the metaphor begins to fall apart.

(That's also why OOP has all these "patterns." Many are just attempts to cope with the "object" metaphor falling apart. "Is" an AttackingRock a Monster, or "is" it an Obstacle? Hmm...)

Also, you can compile a Lumen file to JS/Lua by running `lumen -c file.l -o file.js`. More info at `lumen --help`.

This is wonderful. Thank you for sharing! I've been putting off a JS coding project for some interview, which I now think I'll write in Lumen. Another pleasant surprise: it was written by the HN moderators.

Have you used this in any substantial projects?

I used to be the same way.

Wake up at 5am, meditate, exercise, and shower before starting your day. Stop eating processed carbs and sugar. Get off the computer at 9pm and sleep at 10pm. Clean your room. Schedule sprints of work for yourself, drag yourself over to your chair, and force yourself to start typing anything. Talk to your friends more often. Set 1-3 large goals at the beginning of the day and explain to yourself why they're important.

There are lots of reasons you might be feeling this way, and it's different for everyone. Maybe you're disorganized, or you feel your work is too easy, or your health is bad. You'll have to find out which one it is by trying a lot of different things.

If after doing all this you still feel the same way, please seriously consider the very real possibility of clinical depression, and seek professional help.

CoderPad is really, really good. I've interviewed using a bunch of alternatives, and CoderPad is far and away the only one that works reliably all the time. It always cheers me up when a company tells me they're using it, because I know it won't lag, the vi keybindings will work, the built-in terminal will work, there won't be weird interface glitches, every language I need will be there, etc.

This sounds hyperbolic, but I've never wanted a feature during an interview and found CoderPad to lack it.

I used to tell myself I couldn't code or write without the perfect font. I'd spend hours looking for it, and end up not getting any work done. When I finally did get around to actually working, five minutes in and I'd forget about the font completely.

I have a (rather lazy) friend who's been asking me to help him start a blog for years now. I've promised to after he produces his first block of content, and he keeps saying he can't write if he doesn't feel the design is aesthetically pleasing. If he'd spent his time writing instead of worrying about this, he'd have a crappy initial draft, several revised drafts, and probably something decent by now. But no, that prohibitively unattractive font!

It was nice of iA to write this up, and design posts are a fun read, but does anyone who's busy actually writing care about this?

3Blue1Brown is a treasure. The production value is excellent, and he's great at taking seemingly uninteresting ideas and painting a beautiful picture to connect them in twenty minutes. I used to go through a video before falling asleep each night.

If someone does something wrong, Alice tells them plainly, and they get offended, whose fault is it? Some people say it's Alice' fault for offending; some say it's the person's fault for doing it wrong in the first place, and for subsequently getting offended.

I think we're conflating is and ought here. It's probably a fact of reality that most people aren't happy to be told they're wrong. But arguably people ought to accept the consequences of being wrong, e.g. feeling bad when they're told.

I've talked to lots of startups in San Francisco. Most are failing, just due to the nature of startups, but can survive if they reach a finite set of straightforward goals. They've found product/market fit, they know what they have to do, they just have to do it, and the correct 10,000 characters of code input into a computer would solve all their business problems. There's often a lot of handwringing about why they're failing: the process is wrong; communication is wrong; something or other. But the largest reason they're failing is that they're insufficiently good at technology. You know who'd be really good at fixing that? A team of Alices.

I think Alices get too much flak. Bob is genuinely a toxic character. But if your only fault is telling the truth, which offends people, and you're otherwise excellent at your job--- there's a huge opportunity for twenty Alices to get together, bypass the inefficiencies of being offended, and win big. Tech has an obvious historical example.

Edit: I reread the description of Alice. All right, maybe don't browbeat your point into others.