AboutFrontend developer. Worked on ton of legacy projects. Jamstack is my jam right now!
SkillsReact, SCSS, CSS-in-JS, Typescript, good practice enthusiast
Joined devRant on 6/28/2018
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
So fellow dev asked me design suggestion knowing that I did design way before, I provided him with ok-ish solution and he said to me: 'this is way better response than designer gave me!'. So curious as I am I asked him what did he said? He said : 'Yeah, sure!' on everything he asked if it is ok to add to screen!
That feeling when devs are better designers than designers you have at disposal!3
When you feel that only you and maybe one other guy from the team care about product and do effort to actually refactor legacy spaghetti code while others just patch it up or even build changes on top of legacy spaghetti!4
What a vast and great eco-system we have (refering to js and npm) almost every time I am trying to use two libs and combine them to work together some shit happens.
So I wanted to have lean and good written code without introducing unnecessary renders and logic.
Ended up doing just that because 'we know about issue with our library, many users told us that, too bad we wont fix that shit', so I feel like a 'workaround' developer at some hackathon right now!
My least successful project was:
social network for student exchange. I did it for the student organization that after launch decided that they really don't need that and shut it down.
Idea was for students to subscribe to internships of their interest (for example 'developer internship') and then they get notifications when someone from the network publish internship within subscribed interests.4
so yeah let's have conference about security but its perfectly fine to have registrations over non-secure connection!4
doing documentation in word and having meetings about it, code reviews where people say great code quality with all good practices but... we would like to do it differently, reasons? less lines of code but real reason is not understanding design patterns, also 6 levels of hierarchy and wasted effort to prove that approach is good and considered as good practice just to be changed by someone who doesn't write code anymore. Decisions that other approach is better because they did it that way 10 years ago on last project where they were developers on totally different tech stack. dear friends, welcome to corporation!1
have some ideas but only ones that i consider startup material are not software but hardware based!1
Listened my PO talking with client and she explained why we did it the way we did (so the app user flow has more sense) ending the sentence with "... so if you look it that way, this is not a bug, it is a feature!"
title: 'headless CMS separation of concerns',
desc: 'there is special circle in hell for those who put styling flags and parts of logic in headless CMS data '
title: 'legislatives from computer illiterate politicians',
desc: 'we don't need fast-lan-internet-for-more-money, we also don't need new cookie or GDPR notifications'
title: 'snowflakes are offended',
desc: 'nobody gives a sh1t, man up and deal with it like the rest of us do'
after seeing this -> https://theverge.com/2018/9/...
I feel so frigging great that i ditched that abysmal piece of $h1t long ago!2
ditched windows for good 2 months ago. never been happier!
"I really miss unexpected and time consuming OS updates!"
- no one ever10
reactjs project i got to work on has one "main" component and "modals" components referenced in it, that's it, one parent with many children. parent has nearly 1000 lines of code, child on average is nearly 500!
Let's talk about components! LOL :'/2