almata

Maybe the button with the phone icon could be green and much larger than the other buttons. I think that would make it easier for users of this app to understand and remember where they need to tap to call the person on the screen.

There is a link on the About section: https://interactive-pathfinding.netlify.com

Any chance you still have that article around? I would like to read it if possible.

> Simply bookmarking the article itself to read later [...]

I actually send the HN discussion itself to my Reading List. So when I find some time I start with the comments here and then decide whether or not I should read the article. And tbf most of the times I get enough information here and never follow the link to the main reading.

Thanks for sharing this video. I had no idea who he was.

Did you explain your thoughts about the ideal mattress some time ago maybe? I'd say I already read those same arguments before and found them extremely interesting.

It's usually easier to just look for the paper somewhere else once you've decided you want to read it your own way. In this case, you can find it here [0]. As they often show kind-of-classic papers, many of them are publicly available through a Google search.

[0] http://library.lanl.gov/cgi-bin/getfile?00326866.pdf

Many thanks, I'll do.

After using several different blogging platforms/tools, I finally decided to use instead a GitHub repo for my notes. Something really simple that lets me 1) create a note in plain Markdown, and 2) run a publi.sh script. That's all. After that, the note is already in my GitHub repo ready to be ctrl-f'ed when I'm looking for something I know I documented. In case anyone is interested I used this tool [0], but it was first time in my life creating a Bash script, so fairly assume the code is, well... you know :)

[0]: https://github.com/almata/BlogGit/blob/master/README.md

Many thanks for taking the time to write such a lovely text.

Not exactly what you're looking for, but maybe you or someone else might be interested on this: http://fermatslibrary.com

Thanks Steeeve, really informative answer.

Many thanks for all these answers (I've upvoted all of them). Super useful. Really.

If you were a developer with 10 yoe looking for something new to get into, what would you choose at this moment and thinking about the near future: Haskell, Scala or F#?

:)))

Any advice on how to reorient your career into this maybe? :)

I actually think Ballmer really was the perfect finance-oriented CEO between tech-oriented Gates and Nadella. Except instead of 14 years it'd probably have been better a 5-8 years period or so. Sadly, 14 years was a too long period and maybe Microsoft lost some good trains along that time.

Location: Barcelona

Remote: YES

Willing to relocate: Nope, although I can be onsite 3 days a week (main European cities)

Technologies: iOS

LinkedIn: https://ie.linkedin.com/in/almata

Email: mata.albert (Gmail)

> I make sure to preface my suggestions to the team with, "Now, this is probably another terrible manager-idea, but how about we…".

Does this work for you? I mean, do you get more constructive criticism using this? I tend to think in real life we are programmed to agree with our managers most of the time. Have you received more sincere feedback when you start saying this?

Nah. It was just a (bad) joke. Should have added a :p

"The service is unavailable."

It seems no algorithm there taught you more useful things though.

It's not that I worry. It's just that I don't think it's correct. Same way as I don't have anything to hide in my email inbox but I don't like the idea of NSA (or anyone) having reading access to it.

Even when I don't agree with you (I may receive a mail notification with some private content) the system is totally useless as I can have an iPad next to my main computer and use it to spend all the time I want doing other stuff. Or just work with two computers. Or whatever.

From the Upwork FAQ: "You'll need to download and use the Upwork Team App—this tool includes the Work Diary, which ensures you are guaranteed payment. By taking work-in-progress screenshots every 10 minutes, it provides proof to your clients that you are hard at work."

Screenshots every 10 minutes? You mean... screenshots of MY SCREEN every 10 minutes? That was what made me close their website and totally forget it until I've seen this submission on HN today.

Just to mention one that's usually quite ignored, I love the simplicity and usefulness of the Levenshtein distance: https://xlinux.nist.gov/dads/HTML/Levenshtein.html

I once implemented it in typical scenario where sales people had to look for a client, but it could be written as: 1/ That Client With A Strange Name, Ltd. 2/ The Client With Strange Name, Ltd. 3/ That Client With A Strange Name 4/ [etc]

It worked really well and avoided lots of duplicated entries.

I'm reading the book Good Charts (https://hbr.org/product/good-charts-the-hbr-guide-to-making-...) and it talked about (and linked) your paper. I found it quite interesting, so I submitted it here in case others did as well.

> Just keep on going. Lesson: Be persistent, don’t give up.

All lessons are interesting and all ideas can be valuable, but in this kind of articles I always find that the most valuable advice is just this: be persistent, don't give up. I'd say this is usually the key for success in many areas of knowledge (and certainly in programming).

Totally. Being 38 myself this is one of the things I've liked the most from this case.

Isn't a short comment a much quicker method to get why something has been done that way instead of having to check git log? Also, if you rely on git log for that, don't commit messages become unnecessarily long and detailed?

Super interesting reading, thank you. Does anyone know similar papers on functional programming? I've sometimes found some that were much more difficult to read if you're not a mathematician.