Artem Sapegin

Author profile

Artem Sapegin

Coffee first developer, award-losing photographer, occasional leathercrafter, and dreamer of a boring life.

@sapeginThereWebsiteView on DEV

Articles by @sapegin

Browse the latest writing surfaced through DevArt.

Healing my open source addiction
#opensource#burnout#mentalhealth#hobbies

Healing my open source addiction

I started my first open source project in 2012 but 10 years later I quit it almost entirely because of its hostile culture. Recently, I found a hobby that gives me everything I liked about open source but without any of its downsides.

Artem SapeginArtem Sapegin3 min read
0 reactions0 commentsRead full article
Washing your code: avoid comments
#javascript#programming#cleancode

Washing your code: avoid comments

Some developers never comment their code, some comment too much. The former believe that the code should be self-documenting, the latter read somewhere that they should always comment their code. Both are wrong.

Artem SapeginArtem Sapegin5 min read
0 reactions2 commentsRead full article
Going offline
#opensource#burnout#work#hobbies

Going offline

The Coronavirus allowed me to reflect on what’s important to me, and to see my life from a different point of view regarding work, open source, hobbies, and social networks over the past two years.

Artem SapeginArtem Sapegin10 min read
8 reactions2 commentsRead full article
Writing cross-platform components for web and React Native
#reactnative#react#javascript#componentdriven

Writing cross-platform components for web and React Native

One of the selling points of React Native is code sharing between web, iOS, and Android — “seamless cross-platform” as they say on the homepage. Unfortunately, React Native gives us very few tools to write components that work on web and native, and the experience is far from seamless.

Artem SapeginArtem Sapegin5 min read
12 reactions0 commentsRead full article
Washing your code: avoid mutation
#javascript#programming#cleancode

Washing your code: avoid mutation

Mutations happen when we change a JavaScript object or array without creating a new variable or reassigning an existing one. Mutations make code harder to understand and can lead to hard-to-find bugs.

Artem SapeginArtem Sapegin14 min read
41 reactions6 commentsRead full article
Artem Sapegin developer articles | DevArt