https://github.com/tensorflow/rust

The title is clickbaity, but it’s not something other authors haven’t stated similarly. If you can through teamwork get your teammates to work more effectively and not become blocked, then you are far more than a 10x developer. There is wisdom in not fetishizing individual progress. Well at least if you are the person who owns the business. If you’re the worker bee then the only thing that matters is the appearance of your progress. You can appear to be a 10x by floundering everyone around you too… We had a guy who did that for several years before management figured out he wasn’t actually very good, he was just effective at draining the work capacity of his peers.

I wasn’t able to find titles on the article you were describing, though I don’t think those count as real titles, they sound more like twitter culture.

There’s a kernel of an idea here that the author doesn’t state explicitly, and others like Fred Brooks have. The idea is that no matter how capable any particular developer is, there is always a limit. One of the ways a capable developer can increase their productivety is to lead/build a team of highly productive developers. This author provides some ideas on behaviors that can benefit such a team. I don’t think there’s enough here to make an ordinary team a high performing team though.

I personally have had some success leading teams. The approach I take is that of a coach, and listening/observing to what each member needs from a leader. Some require constant coaching and guidance until a proficiency level is reached. Others take off on their own, and only need the lead for occassional guidance. A quote I really like is “the tide raises all boats”. The idea being the create conditions so all team members can improve.

So what are some coaching tips, or areas to concentrate on? Some examples I offer; using version control effectively, using development tools effectively, reading and interpreting requirements, when making assumptions is appropriate, and when seeking guidance from stake holders is paramount.

But ultimately, a lot of a teams productivety can be beyond it’s level of influence. For example in low function oranizations with chaotic product and project management, where requirements and priorities shift like the breeze off of a dead sea, delivering anything is often near impossible.

I’m not a Ruby developer but boy oh boy does RubyConf and RailsConf have some great talks year after year.

Technically Wrong: Sexist Apps, Biased Algorithms, and Other Threats of Toxic Tech - Sara Wachter-Boettcher

My AI assistant does not understand me, this tech is toxic. So much bullshit in this talk

Also relevant is John Johansen’s response.

What a difference between his first post and this one. In the first one he comes off like a colossally toxic asshat. I know this is no surprise to anyway, but still. That kind of behavior is not OK. Period.

This post on the other hand is clear headed and explanatory. It lays out the rules and why it’s important to follow them.

Maybe Linus just needs a 1h send buffer? :)

We already have the java tag, for the moment.

Right, but Java is not Kotlin. It’s a different language.

Also, when requesting a new tag, it’s usually best to list relevant submissions in support of an assertion that it’d help.

I’ve updated my original post with some relevant submissions.

There’s a scala tag, just saying. Though usually Scala posts are different enough from normal Java-ecosystem posts that they do merit their own tag, not sure if the same can be said for Kotlin.

I was asked in the chat room to elaborate on why I think this is a non-story, so here’s a quick reformatting:

Docker Inc owns a trademark for software named “docker” and doesn’t want random coders to name random projects “docker” (the next-to-last example in the story) because that’s confusing to anyone who runs into it when looking for the real docker. So a lawyer sends a “hey, please stop using our trademark for your project” note, which probably uses the legal terms “cease and desist” which mean “we’re formally asking you to stop it”.

There’s also projects related to docker using their name/logo (for example docker-charm) and the lawyer is asking “Hey, please do X/Y/Z to make it explicit to the public that you’re not officially affiliated with us”. That can mean removing logos, adding disclaimers, and sometimes renaming entirely depending on what the project is doing and how paranoid the lawyer is. I specifically noticed in the docker-charm issue that the lawyer only asked that they remove the logo, not that they rename the entire projects. That’s pretty chill of Docker to recognize that someone seeing “docker-charm” will understand that this project integrates docker and charm, rather than sending “omg you can’t even say our name in your name” which a lot of laywers do.

So I really think this is nothing. Docker is being polite, restrained, and using issues to fit into projects' standard workflows. GitHub surfers won’t run into projects and be unsure if they’re seeing an official docker project or not. This looks like a model story of trademark protection to me.

Sure, but Github will enforce the request

In this regard also slow.com

It’s not a gamble when apple is involved, it’s just stupid decision

The most charitable reading is roughly: “Don’t assume users will like/use your app just because it exists. Heavily consider whether the functionality you provide is a good fit for the context of a mobile application.”

Outlook, maybe? It has some pretty heavy feature overlap, and a pretty nice UI. (Note that Outlook on iOS/Android has nothing in common with the desktop Outlook other than its ultimate purpose. I wish they’d picked a different name.)

Google Inbox is carbon copy of Mailbox.

On iOS, Dispatch seems nice. It offers a lot of way to automate your email, although it doesn’t have the “save for later” feature of Mailbox.

If you use gmail https://inbox.google.com is at feature-parity with Mailbox.

know that this guy has mental illness, but could anyone explain how his illness made him racist and generally asshole ? Is there any explanation ?

Some mental illnesses make you terrified all the time. It didn’t make him racist but it sure breeds a mental space where racism has roots to grow. He’s still a racist asshole, and could choose not to be, but I’d imagine it’s harder to do so.

I’m waiting for Zed Shaw to come out with “Node is a Ghetto”.