Ulad Ramanovich
@uramanovich.bsky.social
Senior Fullstack Engineer passionate about TypeScript/JavaScript ecosystems.
Sharing pragmatic tech tips & exploring AI-powered development workflows.
Let's build better software together! 🚀
Sharing pragmatic tech tips & exploring AI-powered development workflows.
Let's build better software together! 🚀
Pinned
Ulad Ramanovich
@uramanovich.bsky.social
· Nov 16
I'm new to Bluesky! I'm a Full-Stack Engineer diving into "build in public", focusing on React.js projects and sharing tech insights along the way.
Looking forward to connecting with fellow builders, sharing learnings, and getting feedback from the community!
Looking forward to connecting with fellow builders, sharing learnings, and getting feedback from the community!
Do you know the newsletter with weekly sharing what happened in the AI or Web development?
I’m trying to find newsletter with analysis what happened for the last week, instead of raw links
#frontend #ai #wevdevelopment #react #nodejs
I’m trying to find newsletter with analysis what happened for the last week, instead of raw links
#frontend #ai #wevdevelopment #react #nodejs
June 9, 2025 at 8:16 AM
Do you know the newsletter with weekly sharing what happened in the AI or Web development?
I’m trying to find newsletter with analysis what happened for the last week, instead of raw links
#frontend #ai #wevdevelopment #react #nodejs
I’m trying to find newsletter with analysis what happened for the last week, instead of raw links
#frontend #ai #wevdevelopment #react #nodejs
Tired of slow Jest tests? I cut my test suite time by 67% with these two simple tricks:
1. Add `maxWorkers=50%` to utilize available CPU
2. Implement `shard` to split and run tests in parallel across multiple jobs
The big challenge? Collecting coverage data from separate jobs. Solution below
1. Add `maxWorkers=50%` to utilize available CPU
2. Implement `shard` to split and run tests in parallel across multiple jobs
The big challenge? Collecting coverage data from separate jobs. Solution below
April 26, 2025 at 9:58 AM
Tired of slow Jest tests? I cut my test suite time by 67% with these two simple tricks:
1. Add `maxWorkers=50%` to utilize available CPU
2. Implement `shard` to split and run tests in parallel across multiple jobs
The big challenge? Collecting coverage data from separate jobs. Solution below
1. Add `maxWorkers=50%` to utilize available CPU
2. Implement `shard` to split and run tests in parallel across multiple jobs
The big challenge? Collecting coverage data from separate jobs. Solution below
Senior devs spend 20% of time on code reviews. If you don't, either you're not senior or your team culture needs rework.
Good code reviews:
- Catch bugs before they cause outages
- Share knowledge across the team
- Build better architecture through diverse perspectives
Good code reviews:
- Catch bugs before they cause outages
- Share knowledge across the team
- Build better architecture through diverse perspectives
April 25, 2025 at 9:21 AM
Senior devs spend 20% of time on code reviews. If you don't, either you're not senior or your team culture needs rework.
Good code reviews:
- Catch bugs before they cause outages
- Share knowledge across the team
- Build better architecture through diverse perspectives
Good code reviews:
- Catch bugs before they cause outages
- Share knowledge across the team
- Build better architecture through diverse perspectives
What is your next action when you have an incident and the last PR in the list this one?
February 19, 2025 at 6:30 AM
What is your next action when you have an incident and the last PR in the list this one?
Confusing by word 'token' when working with AI? Me too 🤔
I spent time understanding how it's calculated, here's simple math:
- Token ≠ word
- 1 word ≈ 1.3token
- 1 tweet ≈ 35 tokens
- Emojis cost extra tokens
shorter words = fewer tokens = lower costs
I spent time understanding how it's calculated, here's simple math:
- Token ≠ word
- 1 word ≈ 1.3token
- 1 tweet ≈ 35 tokens
- Emojis cost extra tokens
shorter words = fewer tokens = lower costs
February 14, 2025 at 2:40 PM
Confusing by word 'token' when working with AI? Me too 🤔
I spent time understanding how it's calculated, here's simple math:
- Token ≠ word
- 1 word ≈ 1.3token
- 1 tweet ≈ 35 tokens
- Emojis cost extra tokens
shorter words = fewer tokens = lower costs
I spent time understanding how it's calculated, here's simple math:
- Token ≠ word
- 1 word ≈ 1.3token
- 1 tweet ≈ 35 tokens
- Emojis cost extra tokens
shorter words = fewer tokens = lower costs
Skipping tests to save time? Think twice.
While writing tests feels chore, the real cost hits during refactoring.
Use AI for basic tests, but guide it - create mocks & define key scenarios. Keep logic simple, and review all the code produced by AI.
Future you will thank you
While writing tests feels chore, the real cost hits during refactoring.
Use AI for basic tests, but guide it - create mocks & define key scenarios. Keep logic simple, and review all the code produced by AI.
Future you will thank you
February 12, 2025 at 4:29 PM
Skipping tests to save time? Think twice.
While writing tests feels chore, the real cost hits during refactoring.
Use AI for basic tests, but guide it - create mocks & define key scenarios. Keep logic simple, and review all the code produced by AI.
Future you will thank you
While writing tests feels chore, the real cost hits during refactoring.
Use AI for basic tests, but guide it - create mocks & define key scenarios. Keep logic simple, and review all the code produced by AI.
Future you will thank you
You're missing one primary concept when coding with AI.
AI doesn't own the code, the person who approved this code is the owner of the code.
AI is a tool - your expertise in reviewing, validating & owning the implementation is what matters
AI doesn't own the code, the person who approved this code is the owner of the code.
AI is a tool - your expertise in reviewing, validating & owning the implementation is what matters
February 11, 2025 at 7:19 AM
You're missing one primary concept when coding with AI.
AI doesn't own the code, the person who approved this code is the owner of the code.
AI is a tool - your expertise in reviewing, validating & owning the implementation is what matters
AI doesn't own the code, the person who approved this code is the owner of the code.
AI is a tool - your expertise in reviewing, validating & owning the implementation is what matters
1/5 How to manage database access in monorepo with NestJS?
I faced this problem a few times:
• Duplicated database logic
• Multiple connection configurations
• Inconsistent testing patterns
• No clear structure
Let me explain how I fixed this with the Data-Access Pattern 🧵
#NestJS #nodejs #webdevb
I faced this problem a few times:
• Duplicated database logic
• Multiple connection configurations
• Inconsistent testing patterns
• No clear structure
Let me explain how I fixed this with the Data-Access Pattern 🧵
#NestJS #nodejs #webdevb
February 10, 2025 at 3:17 PM
This is env management I bring for each project. Don't rely on process.env directly - use Zod validation instead.
Type-safe + clear errors = no more missing configs
#TypeScript #WebDev #nodejs
Type-safe + clear errors = no more missing configs
#TypeScript #WebDev #nodejs
January 29, 2025 at 4:26 PM
This is env management I bring for each project. Don't rely on process.env directly - use Zod validation instead.
Type-safe + clear errors = no more missing configs
#TypeScript #WebDev #nodejs
Type-safe + clear errors = no more missing configs
#TypeScript #WebDev #nodejs
Will AI replace your job? 🤔
AI isn't replacing jobs directly - it's automating tasks. Think of it as a tool that helps process work faster, not a robot employee.
Humans still handle complex cases, AI handles repetitive ones. 🤖
AI isn't replacing jobs directly - it's automating tasks. Think of it as a tool that helps process work faster, not a robot employee.
Humans still handle complex cases, AI handles repetitive ones. 🤖
January 27, 2025 at 5:20 PM
Will AI replace your job? 🤔
AI isn't replacing jobs directly - it's automating tasks. Think of it as a tool that helps process work faster, not a robot employee.
Humans still handle complex cases, AI handles repetitive ones. 🤖
AI isn't replacing jobs directly - it's automating tasks. Think of it as a tool that helps process work faster, not a robot employee.
Humans still handle complex cases, AI handles repetitive ones. 🤖
The 70/30 rule of AI coding: While AI can scaffold 70% of your code, the crucial 30% requires deep engineering expertise.
Best practice: Use AI as a drafting tool, maintain atomic conversations, and own your code through meaningful review.
#AI #SoftwareDevelopment
Best practice: Use AI as a drafting tool, maintain atomic conversations, and own your code through meaningful review.
#AI #SoftwareDevelopment
January 24, 2025 at 5:33 PM
The 70/30 rule of AI coding: While AI can scaffold 70% of your code, the crucial 30% requires deep engineering expertise.
Best practice: Use AI as a drafting tool, maintain atomic conversations, and own your code through meaningful review.
#AI #SoftwareDevelopment
Best practice: Use AI as a drafting tool, maintain atomic conversations, and own your code through meaningful review.
#AI #SoftwareDevelopment
🎨 Building new website? Here's a harsh truth:
Most projects fail not because of dev speed, but waiting for "perfect design"
Quick win:
- Ship minimal design in 2 weeks
- Test with real users
- Iterate based on feedback
Stop guessing what users want.
#buildinpublic
Most projects fail not because of dev speed, but waiting for "perfect design"
Quick win:
- Ship minimal design in 2 weeks
- Test with real users
- Iterate based on feedback
Stop guessing what users want.
#buildinpublic
January 22, 2025 at 3:21 PM
🎨 Building new website? Here's a harsh truth:
Most projects fail not because of dev speed, but waiting for "perfect design"
Quick win:
- Ship minimal design in 2 weeks
- Test with real users
- Iterate based on feedback
Stop guessing what users want.
#buildinpublic
Most projects fail not because of dev speed, but waiting for "perfect design"
Quick win:
- Ship minimal design in 2 weeks
- Test with real users
- Iterate based on feedback
Stop guessing what users want.
#buildinpublic
Post-interview clarity hit me hard today 💡
Spent 2 weeks learning algorithms, only to get asked about building an actual product feature. Classic over-preparation for the wrong battle.
Lesson: Always check type of interview you're participating. The interview format tells you what you need to know
Spent 2 weeks learning algorithms, only to get asked about building an actual product feature. Classic over-preparation for the wrong battle.
Lesson: Always check type of interview you're participating. The interview format tells you what you need to know
January 21, 2025 at 7:00 PM
Post-interview clarity hit me hard today 💡
Spent 2 weeks learning algorithms, only to get asked about building an actual product feature. Classic over-preparation for the wrong battle.
Lesson: Always check type of interview you're participating. The interview format tells you what you need to know
Spent 2 weeks learning algorithms, only to get asked about building an actual product feature. Classic over-preparation for the wrong battle.
Lesson: Always check type of interview you're participating. The interview format tells you what you need to know
Multiple tabs sending same requests? Been there 🔧
Solution: Leader Election pattern!
- Tabs form a team
- Pick ONE leader tab
- Only leader makes API calls
- If leader closes, new one steps up
Used broadcast-channel lib. Now instead of 5 requests → just 1
#frontend #javascript
Solution: Leader Election pattern!
- Tabs form a team
- Pick ONE leader tab
- Only leader makes API calls
- If leader closes, new one steps up
Used broadcast-channel lib. Now instead of 5 requests → just 1
#frontend #javascript
January 20, 2025 at 7:50 PM
Multiple tabs sending same requests? Been there 🔧
Solution: Leader Election pattern!
- Tabs form a team
- Pick ONE leader tab
- Only leader makes API calls
- If leader closes, new one steps up
Used broadcast-channel lib. Now instead of 5 requests → just 1
#frontend #javascript
Solution: Leader Election pattern!
- Tabs form a team
- Pick ONE leader tab
- Only leader makes API calls
- If leader closes, new one steps up
Used broadcast-channel lib. Now instead of 5 requests → just 1
#frontend #javascript
Multiple tabs sending same requests? Been there 🔧
Solution: Leader Election pattern!
- Tabs form a team
- Pick ONE leader tab
- Only leader makes API calls
- If leader closes, new one steps up
Used broadcast-channel lib. Now instead of 5 requests → just 1
#frontend #javascript
Solution: Leader Election pattern!
- Tabs form a team
- Pick ONE leader tab
- Only leader makes API calls
- If leader closes, new one steps up
Used broadcast-channel lib. Now instead of 5 requests → just 1
#frontend #javascript
January 20, 2025 at 4:00 PM
Multiple tabs sending same requests? Been there 🔧
Solution: Leader Election pattern!
- Tabs form a team
- Pick ONE leader tab
- Only leader makes API calls
- If leader closes, new one steps up
Used broadcast-channel lib. Now instead of 5 requests → just 1
#frontend #javascript
Solution: Leader Election pattern!
- Tabs form a team
- Pick ONE leader tab
- Only leader makes API calls
- If leader closes, new one steps up
Used broadcast-channel lib. Now instead of 5 requests → just 1
#frontend #javascript
Discovered today Docker Compose profiles and was surprised.
Instead of juggling multiple docker-compose files for prod/dev/test, just add "profiles: [dev]" to your services and run:
docker compose --profile dev up
Perfect for managing different environments in a single file!
#docker
Instead of juggling multiple docker-compose files for prod/dev/test, just add "profiles: [dev]" to your services and run:
docker compose --profile dev up
Perfect for managing different environments in a single file!
#docker
January 7, 2025 at 6:16 PM
Discovered today Docker Compose profiles and was surprised.
Instead of juggling multiple docker-compose files for prod/dev/test, just add "profiles: [dev]" to your services and run:
docker compose --profile dev up
Perfect for managing different environments in a single file!
#docker
Instead of juggling multiple docker-compose files for prod/dev/test, just add "profiles: [dev]" to your services and run:
docker compose --profile dev up
Perfect for managing different environments in a single file!
#docker
Tired of TypeScript being "stupid" with filter()?
When you filter out undefined, does TS still think they might be there?
🪄 Magic solution: Add "is" type check!
#typescript #webdev
When you filter out undefined, does TS still think they might be there?
🪄 Magic solution: Add "is" type check!
#typescript #webdev
January 7, 2025 at 7:47 AM
Tired of TypeScript being "stupid" with filter()?
When you filter out undefined, does TS still think they might be there?
🪄 Magic solution: Add "is" type check!
#typescript #webdev
When you filter out undefined, does TS still think they might be there?
🪄 Magic solution: Add "is" type check!
#typescript #webdev
I prefer Claude over ChatGPT for both its superior code assistance and projects feature (Claude Pro).
With projects, you can create custom prompts with specific output requirements - perfect for recurring tasks like architecture planning or article title generation
With projects, you can create custom prompts with specific output requirements - perfect for recurring tasks like architecture planning or article title generation
January 1, 2025 at 2:42 PM
I prefer Claude over ChatGPT for both its superior code assistance and projects feature (Claude Pro).
With projects, you can create custom prompts with specific output requirements - perfect for recurring tasks like architecture planning or article title generation
With projects, you can create custom prompts with specific output requirements - perfect for recurring tasks like architecture planning or article title generation
Why didn't I know about this must-read React document for so long?
Just found the Rules of React. You should follow them to simplify updates for the newest version of React and support the React compiler in future releases.
react.dev/reference/ru...
Just found the Rules of React. You should follow them to simplify updates for the newest version of React and support the React compiler in future releases.
react.dev/reference/ru...
Rules of React – React
The library for web and native user interfaces
react.dev
December 30, 2024 at 1:51 PM
Why didn't I know about this must-read React document for so long?
Just found the Rules of React. You should follow them to simplify updates for the newest version of React and support the React compiler in future releases.
react.dev/reference/ru...
Just found the Rules of React. You should follow them to simplify updates for the newest version of React and support the React compiler in future releases.
react.dev/reference/ru...
🤖 AI & Engineering Growth
AI speed up Senior Engineers but can hurt Juniors. And when non-engineers use AI for coding? Recipe for disaster.
Pro tip: Before hitting Senior level, use AI to learn, not just copy/paste. Understanding > shortcuts.
AI speed up Senior Engineers but can hurt Juniors. And when non-engineers use AI for coding? Recipe for disaster.
Pro tip: Before hitting Senior level, use AI to learn, not just copy/paste. Understanding > shortcuts.
December 19, 2024 at 8:45 AM
🤖 AI & Engineering Growth
AI speed up Senior Engineers but can hurt Juniors. And when non-engineers use AI for coding? Recipe for disaster.
Pro tip: Before hitting Senior level, use AI to learn, not just copy/paste. Understanding > shortcuts.
AI speed up Senior Engineers but can hurt Juniors. And when non-engineers use AI for coding? Recipe for disaster.
Pro tip: Before hitting Senior level, use AI to learn, not just copy/paste. Understanding > shortcuts.
🔄 Solved my NestJS DB headaches by creating a Data Access module - a dedicated layer that handles all database operations, migrations, and models. It manages both Postgres & MongoDB, centralizes connections, and makes testing easy.
Writing an article to share my complete setup! 📝
Writing an article to share my complete setup! 📝
December 19, 2024 at 7:55 AM
🔄 Solved my NestJS DB headaches by creating a Data Access module - a dedicated layer that handles all database operations, migrations, and models. It manages both Postgres & MongoDB, centralizes connections, and makes testing easy.
Writing an article to share my complete setup! 📝
Writing an article to share my complete setup! 📝
Using AI for coding? Great tool if you know what you're doing! But here's the catch: always write tests. AI can miss edge cases you won't spot when code gets complex.
E2E testing is ideal, but even unit tests will save you from countless bugs. Test everything you generate 🤖✅
E2E testing is ideal, but even unit tests will save you from countless bugs. Test everything you generate 🤖✅
December 17, 2024 at 8:22 PM
Using AI for coding? Great tool if you know what you're doing! But here's the catch: always write tests. AI can miss edge cases you won't spot when code gets complex.
E2E testing is ideal, but even unit tests will save you from countless bugs. Test everything you generate 🤖✅
E2E testing is ideal, but even unit tests will save you from countless bugs. Test everything you generate 🤖✅