IAmNotAFix

Whoever has the best uptime wins.

I think it's more the way you access the information than the information itself.

Wikipedia averages 598 new articles per day et 2 edits per second.

https://en.wikipedia.org/wiki/Wikipedia:Statistics

Yes, the title is not quite scientific.

10x software engineers are mostly 10x problem solvers who happen to be programmers. The driving attitude is refusing to work hard to accomplish something of low significance, which is mostly done thanks to: finding clever solutions, reducing feedback loops when debugging or testing, gaining proper understanding of systems to avoid empirical tweaking, asking around quickly when getting stuck, and also cleverly navigating company politics in order to ship something in environments where it is hard.

You can identify problems and think for solutions without letting it frustrate you each minute of the day.

At this point how do you even make the difference between their genuine behavior and the behavior that is part of the research?

I find it reassuring in some way. The day Python turns to an ecosystem as dynamic and community-driven as JavaScript is the day it turns to shit.

France be like what the hell are you talking about.

The web is eating the world because it's the easiest way to ship an application. It has nothing to do with whether developers like to do it or not.

Google consistenly tries to make it harder for their competitors to grab user data.

This is true at every level of chess. The thinking optimum is somewhere between "playing without caution" and "over-analysing". Over-analysing is theorically the best but because we're not computers there are mistakes in our resulting assertions.

I have the same opinion except it's not that programming is more complicated than before, but that enterprise programming is more complicated than week-end programming. Side-projects are fun because they're free of so much of the bullshit. How much of this bullshit is actually a necessity to build something serious and maintainable is not entirely clear, but it's not 0 nor 100%.

> AWS knows that if they take too much of ES' market that they won't survive.

If they can take the market like that they'll do it, that's what companies do. The limits of taking the market has never been ethics, but sales.

On the other hand, the fact that it stays unsolved and isn't predicted to be solved in the near future (and it's not sure whether we'll one day have enough computing power to solve it by brute force) indicates that it probably has a long life ahead. Games only are really ended when they're solved.

Alone != Lonely.

> it's impossible to keep up with the workload

I don't know about employees keeping up with their workload, but what I can say for sure is that the workload keeps up with how much the employee is willing to take.

All is well until you need merges, which is where the confusion happens and minds are lost.

- You have a branch `master`.

- You have a branch `feature` which contains commit C, which conflicts with `master`.

- You merge `feature` into `master`, fixing conflicts.

- You log the commits of `master`.

  * First is the merge commit, whose diff contains code added by commit C (including the conflict resolution).

  * Next you see commit C, whose diff contains code added by commit C (obviously)

Wait, how can 2 commits in a row have a diff that modifies the code in the same way? Well, mind you, the diff of a commit doesn't correspond to the moment the patch of the commit was added to the current branch, it only corresponds to the moment it was added to its own branch.

Was this controlled for social interaction? For young people screens are just the standard fallback when you have nobody to hang out with (although surely not the healthiest one).

Are we supposed to have non-movie-like memories about the past? I mean, other than remembering "knowledge" such as sentences or dates or numbers or geography, etc, it seems that all memory about my "actual life" is movie-like.

I don't understand the step where the author is logging in with Facebook.

Was that a legit OAuth 2.0/OpenID Connect log in? (In this case this must have been OAuth 2.0 with a scope giving the application write access to business stuff.)

Or was it a phishing page in which the author gave his facebook password?

Linus Torvalds:

> I am not a visionary. I'm an engineer. I'm happy with the people who are wandering around looking at the stars but I am looking at the ground and I want to fix the pothole before I fall in.

Apollo 11 engineers:

> ok boomer.

L’ABBÉ. — Madame, madame, un bon mot ne prouve rien.

LE COMTE. — Cela est vrai ; mais un bon mot n’empêche pas qu’on ne puisse avoir raison.

--

The Clergyman -- Madam, Madam, a witty saying proves nothing.

The Count -- That is correct; but a witty saying doesn't prevent being right.

https://fr.wikisource.org/wiki/Le_D%C3%AEner_du_comte_de_Bou...

Very true. I would add that if you believe it's your team then your team is probably talking about leadership with variations of the few lines at the top of the article.

Maybe that's because Ford makes cars.

This assumes the URL is publicly available, or is there an on-premise offer?

How does it go beyond the headline and general info?

> despite positive experiences in the past

I think the author mentions it is the first time he buys an ebook.

Also if you think the problem is systemic ("it seems that all the restaurants in this chain behaves this specific way I dislike") then you might as well move on and don't try your chance a second time.

> services like Spotify, Apple Music, Youtube, etc

Which are all subscription-based and not unit-based. There is no cost to explore and listen to random songs when you've already paid your subscription anyway. Switch to unit-based and suddenly way less exploration. So it's unit-less pricing + convenience.

https://txti.es/ comes to mind, but I guess its lack of account system makes it not very blog-friendly.