First of All, I hate Redux. And there is a lot of reasons why.
When I was using Vue in my projects, I always hate moving my state to Vuex. You always think too much on whether you need this state to be global or not. Also, making another one store module always sounds as a big task, making your decisions even harder.
You need to create a whole module with its state, mutations, actions, then bind everything to your components… and you also have an awful interaction between modules through namespaces, which also uses string-based API (so say goodbye…
Hey guys! I know there was no posts from me for like a year or more. This year I was hard-working and hard-learning, my view has changed (yes, I use React now 😃)
Today I want to share the library I’ve discovered a half year ago and absolutely loved it!
This is Effector — application state manager that is the best match for my view on organizing business logic.
So let’s start from the idea and then I’ll show some simple example.
Hello guys! Today I want to share a little but very useful thing.
On my current project, I have a lot of reusable components (I named it “widgets”) that can be placed anywhere. And I ran into a problem with responsive design.
Finally, I understood that css
@media queries are absolutely unusable in my case.
Imagine that we have some
PostsItem component. We have
PostsPage with list of posts:
Hello everyone! 👋👋
Today I want to talk about remote work and to give some advice about how to do it effectively.
Before start, I want to say that I worked remotely for the whole of 2017. Then I tried working at the office and left this hell after 2 months so I’m a remote guy again 😎
So, let’s think why many people switch to remote work and don’t want to switch back
The long way to the office is often so boring. Especially when you use public transport and see many evil people who are apparently unsatisfied with…
Not so far I published a post about the most common mistake of writing API requests and showed some features of Apicase. You can read it here.
After this, I got one fair remark. As I said at the end, handling API requests inside services makes your API layer inflexible and inseparable from the application.
It’s not good, BUT… we can fix it! So, I won’t take a lot of your time.
Imagine we have API layer like this one:
Hello everyone! Today I’ll talk about API requests organisation once again and I’ll raise a little holywar
Most of guides and even frameworks documentations considered as “best practices” told us to go the following way
If you’re on Vue.js and Vuex, you probably often see smth like this:
Everyday I see the questions “How to work with API?”, “Can you give some best practices”, “How to cook axios” in frontend chats. They get a lot of answers but all of them can be reduced to three types
Fatal mistake. Tons of boilerplate code guaranteed, I have nothing more to say
Some people just use axios and don’t care about. In my opinion, it looks good only on “Hello world” examples. When we want to go deeper, we need to write own wrappers, handlers etc. …
So, you gonna be frontend developer in our company
Don’t you really think you learnt %framework_name% and can consider yourself a developer?
Ha-ha, developer, ha-ha-ha
Maybe, you can write a radix sort algorithm on paper right now? No? LOL
Maybe, you can tell me what is the size of array that modern PC can sort per minute? No? So, we will call you back =)))
Not so far I had an interview for “Frontend developer (React)” position.
Here is a list of questions that HR gave me before start. I translated it for you:
It’s no long-read there, I’ll share just a small mixin for one simple case :)
P.S. I had a little negative feedback about my previous post without any argumentation (even invalid). So, the note to people who’ll say “scratch that” — please, walk your way
So, imagine that we have component with some selection logic. E.g. products selector with products from store. And here is one moment — we want to remember users’s choice if he switches page:
Not so long ago, I got a new job. And when I saw the code base for the first time, it terrified me. Here I want to show the things you should avoid in Vue.js applications.
There are no reason to pass static properties to
data and especially in
computed. When you do it, Vue makes these properties reactive but it’s unnecessary.