Vladimir
@jovanovic.bsky.social
Senior Web Developer with focus on #frontend development, #webdesign and #nodejs tooling.
I prefer #scss, #typescript, #nodejs, #vscode, #gulpjs, and absolutely no #css related frameworks.
I prefer #scss, #typescript, #nodejs, #vscode, #gulpjs, and absolutely no #css related frameworks.
I used to love Mac for the development, but I’d probably have to sell my organs to get the performance of my 9950x, 3080, 96GB RAM and pro SSD’s on a PC.
I’ll keep mine 16” M1 Pro as a backup.
I’ll keep mine 16” M1 Pro as a backup.
December 8, 2024 at 2:00 PM
I used to love Mac for the development, but I’d probably have to sell my organs to get the performance of my 9950x, 3080, 96GB RAM and pro SSD’s on a PC.
I’ll keep mine 16” M1 Pro as a backup.
I’ll keep mine 16” M1 Pro as a backup.
One of the examples for that are my custom media query mixins. I can define named resolutions and default font sizes in json, and then just use something like
@ include media (mobile, phablet) {
... CSS
}
wherever I want. Code will be encapsulated, block will have its own dynamic variables etc
@ include media (mobile, phablet) {
... CSS
}
wherever I want. Code will be encapsulated, block will have its own dynamic variables etc
December 8, 2024 at 11:13 AM
One of the examples for that are my custom media query mixins. I can define named resolutions and default font sizes in json, and then just use something like
@ include media (mobile, phablet) {
... CSS
}
wherever I want. Code will be encapsulated, block will have its own dynamic variables etc
@ include media (mobile, phablet) {
... CSS
}
wherever I want. Code will be encapsulated, block will have its own dynamic variables etc
If you have to ask this, it was never for you, since you obviously didn't even scratch the surface.
I use it for several reasons:
- nesting
- programming with custom functions and mixins, almost like with JS
- data structures
- creating dynamic templates
I use it for several reasons:
- nesting
- programming with custom functions and mixins, almost like with JS
- data structures
- creating dynamic templates
December 8, 2024 at 11:08 AM
If you have to ask this, it was never for you, since you obviously didn't even scratch the surface.
I use it for several reasons:
- nesting
- programming with custom functions and mixins, almost like with JS
- data structures
- creating dynamic templates
I use it for several reasons:
- nesting
- programming with custom functions and mixins, almost like with JS
- data structures
- creating dynamic templates
I can understand them.
They know nothing, Dunning Kruger is strong in them, so everyone MUST be a fraud. Right?!
This is what happens when government corruption ruins public education. 🤷♂️
People, never stop learning. Someday, they might call you a fraud because of it 😂👍
They know nothing, Dunning Kruger is strong in them, so everyone MUST be a fraud. Right?!
This is what happens when government corruption ruins public education. 🤷♂️
People, never stop learning. Someday, they might call you a fraud because of it 😂👍
December 6, 2024 at 10:33 PM
I can understand them.
They know nothing, Dunning Kruger is strong in them, so everyone MUST be a fraud. Right?!
This is what happens when government corruption ruins public education. 🤷♂️
People, never stop learning. Someday, they might call you a fraud because of it 😂👍
They know nothing, Dunning Kruger is strong in them, so everyone MUST be a fraud. Right?!
This is what happens when government corruption ruins public education. 🤷♂️
People, never stop learning. Someday, they might call you a fraud because of it 😂👍
I fully agree with this quote:
"Tailwind is dogshit. Just use Sass."
"Tailwind is dogshit. Just use Sass."
December 5, 2024 at 8:41 AM
I fully agree with this quote:
"Tailwind is dogshit. Just use Sass."
"Tailwind is dogshit. Just use Sass."
Tried it right now, it is completely unusable to me.
Many false positives, doesn't recognize VueJS and it seems like it is very opinionated when it comes to how it thinks that the code should be organized.
Not for me, but at least I tried it out.
Many false positives, doesn't recognize VueJS and it seems like it is very opinionated when it comes to how it thinks that the code should be organized.
Not for me, but at least I tried it out.
November 30, 2024 at 2:56 PM
Tried it right now, it is completely unusable to me.
Many false positives, doesn't recognize VueJS and it seems like it is very opinionated when it comes to how it thinks that the code should be organized.
Not for me, but at least I tried it out.
Many false positives, doesn't recognize VueJS and it seems like it is very opinionated when it comes to how it thinks that the code should be organized.
Not for me, but at least I tried it out.
Reposted by Vladimir
Hey, thanks for reading! Yeah I’m a big Zod fanboy. Nowadays I love to use TS-rest. It’s a very lightweight layer on top of express which parses everything through zod before it gets to your endpoints ts-rest.com
🪄 | ts-rest
Incrementally adoptable type-safety for your new and existing APIs
ts-rest.com
November 29, 2024 at 11:35 PM
Hey, thanks for reading! Yeah I’m a big Zod fanboy. Nowadays I love to use TS-rest. It’s a very lightweight layer on top of express which parses everything through zod before it gets to your endpoints ts-rest.com