smonff

Also, people complaining on back button removal, but it is not removed.

Obviously, frustrated people complains, when happy users just remains silent.

Google Play applications reviewa is broken and untrustful (either you write quality reviews since ten years or poorly reactive ones since one week, you are considered the same) and writing articles about those users feedbacks is meaningless.

So unfair. People do no want to learn how to go to the preferences and set the address bar back to top.

Also I saw people asking for tabs back, when they are still there. So conservative...

Just invested in a small house in far Paris suburb and it comes with 2 garden sheds.

No internet for now though.

Not worth mentioning that health care is free for everyone in france thanks to all the money employees "steal" from startup founders.

Tmux, Emacs, Perl, jQuery.

I've worked in places where people cannot understand the necessity of most of the things you list.

If I don't do those steps, they are fine with it at long as it works. If I want to setup all the minimal stack, as long it don't multiply the planning per 3, they are fine with it.

I think it is extremely discouraging, because even if you do all those good steps that would surely improve the product quality overall, it is not something that people can see or will consider. This is not a thing customers can see. Things will just work most of the time, and in case of a problem, you will be able to fix them in no time and it will go back to normal fast because you built all the toolkit before. Customers won't even have the time to complain.

Your standards are highly reasonable, but if you ask some sales person if you should spend 5 days on a feature or 7 days with better quality and full test coverage (ok it would be more like 10 days), they will always say no, don't do it or it's fine, we'll take care of this later.

Documentation? Oh, you'll do this next summer.

Explaining why you should do all this to a team is a long term work: it can take one to two years before they start to understand what the hell you are doing (I mean, maybe you'll have better results than the rest of the team or your infrastructure will be somewhat a little bit more stable).

But it is extremely discouraging, keep yourself warm and don't get too tired. Just do the things the way you are used to do and try to setup the things that are missing so hopefully one day other people will want to use them too.

Last time I used create-react-app, it was installing 30 000 files. Only this number is a problem by itself.

« For centuries, it had been the food of nomads and wanderers. Cooked over campfires, it had been carried in knapsacks from Beijing to Barcelona, from Modena to the Maghreb. »

Real programmer don't eat in front of their screen.

Excellent dish for programmers.

Good satire that explain the cultural meaning that would stay hidden otherwise.

This « excitement » about anything became quite trendy everywhere in the world: you can't read a newsletter or an announcement that don't start by « We are very excited of/to... »

You can have geckos. They are quite effective and don't care of human presence. They just stay on the wall or on their branch.

It's always amusing how people are shocked when stuff like are discovered, although Gmail is designed to serve those kind of things. This is a free service, and as a free service they have to make money with something. I don't see any problem with that. If you don't want this, don't use Gmail, there are lots of available alternatives.

Strange that the study take place in a lab: you definitively not behave the same in a lab or on the road.

A colleague just sent 1000€.

Forget about it. Use Thunderbird with IMAP.

Also, what about Stack Exchange profiles?

Apologies have nothing to do with bugs.

Something that is also worrying is this culture of competition, by showing, right after the start of the post, "best" contributors, as if lined of code was a key of quality development.

I remember some tools that I appreciate, that quote all contributors, in a non hierarchical way. Even if you contributed something minor, you are listed with "main" contributors.

Love Christmas Camelia!

"Plain bad documentation" on CPAN? It is unfair...

Same. I did quite dirty stuff with Thunderbird and it always behave well and it never crash. Plus, it's quite ergonomic.

It is unacceptable.

It looks like a very good shinny little toy to convince those who have not Chrome installed yet that Chrome is a good browser.

It surely is, but for me, it seems weird that a huge company like Google will give you these marvelous toys for free and they don't take anything in exchange.

What I mean is that putting people in a g-bubble like this is bad. I also wonder what the shinny 3 dimensional thing can add as a value to a standard map. In term of education for example: people don't even know how to read a map without a GPS and a map app now. I don't say that map apps are bad, but I don't know...

All my bookmarks collection inside browsers always end up turning to a horrible stack of junk: I don't know how to get rid of the old stuff, you know something that interested you at some point won't be interesting later but you never know...

With the intelligent address bars of the browsers, you can search and find for most of the recent stuff that you used, and even sometimes very old stuff.

I don't use bookmarks anymore, and I feel like the bookmark bar is most of the time a useless distraction.

If there is things I really want to keep, I post it in a public Shaarli[1] instance where I force myself to use tags, description and informative title.

[1] https://github.com/shaarli/Shaarli

Edit: removed markdown

It is also a way to write down and share very complicated command lines that you want to generate only one time because it is a pain to type it each time. So, a kind of self-documentation.

I would also like to know.

3) Maybe a language don't need to be that "elegant", it's not required in all situations. I think I would prefer a "practical" language over "elegance" but like the appearance.