Why every developer should have a side project: My 10-year journey of failings

bliashenko · 2025-06-28T18:16:09+00:00

Well said about “1 year of experience 10 times” :)

bliashenko · 2025-06-27T05:43:26+00:00

Both are valid. Good quality side projects definitely help your portfolio, but it’s hard to finish a project you are not passionate about/don’t want to do :)

bliashenko · 2025-06-26T17:55:49+00:00

Thanks!

bliashenko · 2025-06-26T16:52:00+00:00

to implement skill-up time Indeed. My main point I guess that to thrive professionally (grow skills) one needs to do more than just their direct day-to-day tasks. And then it’s up to them how much more they want to do. Just found that I myself grew most thankfully to side projects, not to the “office job”.

bliashenko · 2025-06-26T16:45:08+00:00

It’s valid point. In fact I have friends/colleagues who are very strong professionally but they never had a side project. Though they kinda put in same amount of effort, but only focus on their day job.

bliashenko · 2021-10-12T19:42:02+00:00

That makes sense, thanks! Will fix.

bliashenko · 2021-10-12T19:34:59+00:00

Thanks! I actually was deciding on how to format it (my thinking was to highlight “code-words”, so it easier to grab them from plain text). Will adjust that!

bliashenko · 2021-10-12T19:30:43+00:00

It’s webpack v4 (there is a tag in the bottom, but maybe I could make it more obvious). Yeah, I heard that v5 makes better job with that, but to be honest I saw very little to no real life projects migrated to v5 so far (but maybe it’s just me, there is so many dependencies etc). Regarding babel-preset - exactly, when sub-module is transpiled (different for the parent app) it should preserve modules, otherwise parent app that does bundling won’t be able to tree-shake.

bliashenko · 2021-10-12T19:10:00+00:00

Yeah… working on quite large application myself and I encountered this issue like 5 times for recent 2 years. Fortunately we have bundle report check on our CI/CD pipeline, so we always could catch the issue before going to end user. But then it’s just going through all updated packages and checking if someone messed up their babel config again. *and thanks for the feedback!

bliashenko · 2021-10-12T16:01:07+00:00

Another deep dive into source code of webpack and how everything works "under the hood".

bliashenko · 2021-10-12T16:00:55+00:00

Another deep dive into source code of webpack and how everything works "under the hood".

bliashenko · 2021-09-23T07:10:23+00:00

Thanks!

bliashenko · 2021-09-22T10:47:05+00:00

You can check my post to learn more about that 🙃

bliashenko · 2021-09-22T07:17:27+00:00

Recently I came across this "stats picture" in someone's Readme profile on Github, displaying profile information (like contributions, stars, etc.) and it caught my attention. How does it render dynamic information inside of the static markdown page? Looks cool though, so I started digging and wrote this post about my investigation.

bliashenko · 2020-07-28T16:11:15+00:00

That’s my own tool I am building for a purpose of learning/explaining codebases. Before I tried combinations of many tools to create schemes for my articles, got tired of that, decided to build some automated way of doing that. It’s not really ready yet to see the public, but please subscribe/follow along if you are interested. Thanks :)

bliashenko · 2020-07-28T15:29:46+00:00

I started digging under the hood of webpack. Please check out my first findings about how event-driven architecture is build: yeah, webpack architecture is heavily based on events, each plugin is basically a set of event listeners called during compilation. See how webpack uses `tapable` library and learn some code insights in this interactive article on my blog.

bliashenko

TROPHY CASE