70 Followers
65 Following
299 Posts

`A dream will always triumph over reality, once it is given a chance.`(c)

Building things as a therapy. Sharing experience along the way.

bio.linkhttps://bio.link/skatkov

Mobile Firefox browser finally supports extensions - first mobile browser to do so!

Has been a couple of years in a making. Great to see this hit a stable branch!

Someone grew up in a bad neighborhood, was bullied as a kid. Learned to punch back and be tough.

Now there is no need for aggression. No need to have that bullied kid inside at all, even for a rare moment.

What would you recommend to that person?

Will be pitching to my company to have a company-wide open source policy. We already do a bunch, but there is just no "official stance".

Has anyone pitched OSS policy to upper management? Any learnings you can share?

I did it twice before and it never felt like success.

Wow, reddit became useless :-)

Imagine being a CEO of that company who runs it

That crushing realization, that all the code I wrote today will likely be gone within 5 years.

Leaving me with nothing but memories of my personal achievements. Nothing to show for to my kid.

I should pick up wood working or something to leave a lasting legacy.

We'll be writing how to start eliminating thousands of possible issues from production code auto-magically. And we need your feedback to write a really useful book - because we're doing it live.

Want to join us? Subscribe https://lintingruby.com!

Linting Ruby: Deliver consistent quality to production with a help of automated code checks

Nowadays, “linting” term is almost synonymous with “static code analysis”. A method of computer program debugging that is done by examining the code without executing the program.

I'm not a fan of this limiting synonym, but we will not go against the grain.

The term was derived from lint, the name for the tiny bits of fiber and fluff shed by clothing, as the command should act like the lint trap in a clothes dryer, detecting small errors to great effect.

Interesting fact:

Term “lint” comes from the name of the first lint tool, which was developed in the early 1970s by a team of Bell Labs researchers led by Stephen C. Johnson. The original lint tool was designed to analyze C source code for potential errors and stylistic issues.

Yeat, many teams don't take full advantage of amazing linting tooling available in Ruby ecosystem. Other teams obsess over things that don't really matter that much.

There is a healthier and more productive way to use these tools. And we're going to write about that.