Szczepan Faber

Go great code reviews! Many thanks to colleagues at @LinkedInEng for amazing feedback and help with the article: thenewstack.io/linkedin-code-…

Carlo Ancelotti: "Does the decision to register Dani Olmo adulterate the league? No, I don't think so."

📅 MAR-13 #DPE Lowdown "How GitHub #Copilot does DPE with AI" 👇 gradle.com/dpe-lowdown/gi… This Lowdown features @GitHubCopilot joined by @AirbnbEng to describe the impact of AI on real-life developers! cc @JavaAtMicrosoft

Hey @SourcegraphCody. Congrats on launching enterprise support. Double checking something real quick: do you support GitHub Enterprise Server (self-hosted)?

@bintray can you *un* rate-limit "LinkedIn" organization on Bintray? I suspect that the rate-limit kicked in when we reached the quota in the OSS tier. However, we upgraded the account an hour ago and the rate-limit is still preventing a couple of teams from publishing. Help pls!

Identify what is the core of your software and make it great! Core vs. edges linkedin.com/pulse/core-vs-…

About to watch @DanielPink live in our @LinkedInEng campus in Sunnyvale. I vividly remember "Drive" book and learning about the 3 key components of human motivation: Autonomy+Mastery+Purpose

Empathy, clear communication, and humility: three important soft skills for software engineering. Read more from our own @matrixtek on @devopsdotcom: devops.com/the-importance…

New @MockitoJava "lenient()" API is a step towards the new major version linkedin.com/pulse/new-mock…

Attending dev productivity meetup today at Google: engineeringproductivity.splashthat.com Are you coming, too?

Today we host Dev Productivity #meetup at LinkedIn Sunnyvale. Join us!!! …roductivitytoolsmeetup.splashthat.com

Submit your talk for Code One (previously Java One :)! twitter.com/java/status/98…

Do less and obsess. Be great at work. I like it! Advice from @MortenTHansen and @danielpink: danpink.com/pinkcast/pinkc…

"If you don't make mistakes, you're not working on hard enough problems. And that's a big mistake." Frank Wilczek

Fully automated pipeline: 1. Merged pull request -> 2. New version released -> 3. Pull requests with version bumps opened to the consuming projects -> 4. Waiting for their CI builds to complete -> 5. Merge! All automated. That's how it should be done.

Learning from @TonyRobbins how to get the back to an early morning routine. After Xmas+NY break and traveling, I want to get back my early mornings!!! Happy 2018 everybody! youtube.com/watch?v=GL9Onm…

I love this feature of @intellijide! Thank you for reminding us about a quick way of testing regexp right there in our favorite IDE. twitter.com/ppvi/status/94…

"If you want to build a ship, don't drum up people to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea" - Antoine de Saint-Exupery. Inspiring @QConSF talk about innovation and creativity: infoq.com/presentations/…

Managers climb hills, leaders take mountains: infoq.com/presentations/… One of the best talks of this year's @QConSF by @ZenTeknologist

In #Shipkit library, whenever we build new version, we automatically open PRs with version bumps to consuming projects. This way, we reduce the lead time of production deployment of a Java library. It's awesome! Next step: avoid proliferation of PRs: github.com/mockito/shipki…

@panthomakos nice talk at @ProdEngSV!