Bohdan Liashenko

Building Previously

[Bohdan Liashenko @bliashenko]

It's time to share what I've been working on recently - better way to learn language while enjoying content.
https://t.co/oWAQvrhs2H #betterlingo

[Bohdan Liashenko @bliashenko]

I’m getting back to blogging! 🚀
Kicking things off with an article about why every developer should have a side project.
https://t.co/MXm4h8IJWQ

[Bohdan Liashenko @bliashenko]

@thekitze Building language learning app. But might add some AI enhancement later 🤓
https://t.co/oWAQvrhs2H

[Bohdan Liashenko @bliashenko]

Ahhah 😆 this is great! Vibe coder
https://t.co/Y9jRR55KeR

[Bohdan Liashenko @bliashenko]

@housecor @kc_dc Thanks for sharing, very good checklist! Probably deserves to be a standalone website.

[Bohdan Liashenko @bliashenko]

@thekitze 2 years later - “well, I wasn’t sure world was ready for everything I have to say, so I filtered out some stories… but here is my 3rd book with some hardcore stuff”.

[Bohdan Liashenko @bliashenko]

@DavidKPiano My attempt to solve this https://t.co/XepPvVLZHh. Still the solution is after the fact. AI yet to get that smart to generate abstraction layers from plain code.

[Bohdan Liashenko @bliashenko]

@ivanov_dev They increase complexity for reading code or making small changes but they reduce complexity when it comes to making big changes/refactoring/migrations etc. So one should choose wisely based on product size, stage of development or possible life time of the project.

[Bohdan Liashenko @bliashenko]

@ivanov_dev Grouping files in directories based on product features really helps to make project feel way smaller than it really is (unless working on some core functionality). Also, VCS operations are much simpler, directories clearly show what should and shouldn’t have been touched.

[Bohdan Liashenko @bliashenko]

Just released something cool I was working on recently - Codecrumbs App now supports integration with a local codebase directly in browser! It is even easier to get started https://t.co/BYDAvzQjhl 💪

[Bohdan Liashenko @bliashenko]

@kentcdodds Added one more... just out of curiosity about Kody the Koala teams 😂

[Bohdan Liashenko @bliashenko]

@bebraw Wow, cool... thanks!

[Bohdan Liashenko @bliashenko]

Finally finished one of the old drafts! Well, @webpack released new version while I still was reading source code for previous one 🙈
#javascript #webpack
https://t.co/aNXl6gcDlN

[Bohdan Liashenko @bliashenko]

@anuraghazru Thanks!

[Bohdan Liashenko @bliashenko]

New investigation with https://t.co/YAEii5A4Z2 is out - this time looking under the hood of github-readme-stats project
https://t.co/PA3TKIwu4h

[Bohdan Liashenko @bliashenko]

@hillelogram @hillelogram it’s exactly what I am solving with https://t.co/XepPvVLZHh, check it out!

[Bohdan Liashenko @bliashenko]

@IGrabill That knowledge is abstracted layer that only exists in heads of people that understand how codebase work and can see “big picture”. So Codecrumbs help you to write down that knowledge, share it, use it while working with a codebase.

[Bohdan Liashenko @bliashenko]

@IGrabill Exactly! Imagine when you are being onboarded into a new codebase, someone should sit with you and show all key points in code that define a feature. They can try to just explain you a feature but it never maps one-2-one to code.