Details
-
Aboutexisting with pain and a typo
-
Skillswhatever fucking thing that brings bread in the table(except butt stuff)
-
Locationunhappy island
-
Website
-
Github
Joined devRant on 6/4/2022
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Never been so fit, so able, so sublime.
Being 26 year old, I know it won't last forever, but I will cherish it.5 -
My innocent-pretending “I din do nuffing” ass after destroying multiple managers careers by manipulating the company opinion against them bc they try to play that scumbag move first but I’m just more conniving, powerful, and just a fucking beast.10
-
You !
Yes You !
Relax your forehead.
Unclench your jaw.
Straighten your back.
Okay, you can now continue scrolling.9 -
"with that said" is the most overused phrase in meetings.
Not sure if it‘s a just a German thing when we speak English.10 -
All is well until one of the interviewers starts dropping questions like:
- Where do you see yourself in x years
- What gets you out of bed every day
etc.
that give you some nice mid interview existential dread.4 -
One of those days, you start daydreaming, and wonder how the whole fucking month went by.
Slow down, u f'ing clock....2 -
I want to talk about my last six months at work. Who wants to hear it?
Spoiler alert : from introverted nerd to Talkative flirt
What did it cost? Everything.14 -
There’s a junior on my team, who has an ego problem.
Within 6-8 months, they have not progressed much, up to the point they still struggle with language and framework syntax.
Yet, they want to get the credit for doing big and important tasks, the ones they have no clue at all how to execute.
Our team tried to break more the tasks and tickets almost to the point of a tutorial. Junior got upset and complained that they did not want the tasks to be broken for them.
If we give space, tasks take forever to get completed. If we try to pair, Junior does everything in their power to cut the meeting short and again take forever to complete anything.
If we prioritize our own tasks, Junior complains that nobody pairs/assist them.
Took one for the team and started to work on finding ways to get this wonderful person to learn. Junior does not learn. In fact, almost feels like things enter from one ear and leave from the other instantly. Despite being repeated multiple times. Chewed. Presented in all sorts of way. You name it, I’ve tried.
Yesterday was the last drop. They fucking rolled their eyes while was explaining something.
This person is dead for me and I will make my personal crusade to not go out of my tasks to help them.
Thanks for coming to my TED rant.7 -
Ok so I'm trying to focus on reading docs on a game engine to do some game dev
And wife busy disturbing
wife: come do this for me
wife: come sit with me
wife: come talk to me
wife: come massage me
wife: come do this to me
Its like a stream of endless error messages13 -
New JoyRant TestFlight build 11:
* Posting Rants
* Improved Notifications Category selection UI with unread indicators (screenshot attached)
Posting this rant from JoyRant right now 😄
The app is now in a state what I consider to be the first major milestone.
There are still features missing (see github https://github.com/WilhelmOks/...) but the most important and most frequently used stuff is done.
https://testflight.apple.com/join/...3 -
I’m back on this platform after an awesome year of progress in my dev career. Here is the back story:
1. I was a junior dev at a financial technologies company for a little over a year.
2. The company was looking to hire an Integration Manager for its software with both our vendors and customers.
3. The pay was good and I was offered that position as a promotion.
4. I accepted it and said to myself that this is temporary. It will help me pay the bills and secure a better life, which it did.
5. Lost two years of my dev career in that position doing nothing but basic integrations (rest apis, web and mobile sdks, and work arounds for what does not work). Zero challenge. This is when I started to use devRant often.
6. On the bright side, the bills were paid and life style got better.
7. Two years in, any way out of the integration department is something I am willing to accept. So I approached every one and worked extra hard as an Application Support Engineer for every product in the firm for free, in the hopes of making good connections and eventually be snatched by someone. This lasted six months.
8. Finally! Got an offer to become the Product Manager for one of the apllications that I supported.
9. Accepted the offer, left the department, and started working with the new team in an Agile fashion. This is when I stopped using devRant because the time was full of work.
10. Five months in, I was leading a team of developers to deliver features and provide the solutions we market. That was an awesome experience and every thing could not have been better.
Except…
Every developer was far better than me, which made me realize that I need to go back on that track, build solutions myself, and become a knowledgable engineer before moving into leading positions.
11. After about a 100 job applications online, I’m back as a Junior developer in another company building both Web and Voice Applications. Very, very happy.
Finally, lessons learned:
1. The path that pays more now is not necessarily the one you wanna take. Plan ahead.
2. There is always a way out. Working for free can get you connections, which can then make you money.
3. Become a knowledgable and experienced engineer before leading other engineers. The difference will show.
4. Love what you do and have fun doing it.
Two cents.1 -
Did any of you managed to pull off 2 fulltime positions while working remotely? What was your experience? Im working in one job where I have standups late in the evening and in a given week I work maybe max 10 hours. Im thinking of finding another fulltime job.7
-
Had QA call my "simple, quick" ticket a "monster ticket" in front of everyone. Hear it and weep, micromanager!
Also had them tell me i thought of everything, it was beautiful, and that i have a knack for frontend :)8 -
FuckYou Google. I don't understand. I'm an Iranian, so what? Can I make a nuclear weapon with Android, am i?10
-
Every 2 months without fail:
Manager: I don’t understand what the point of writing tests is. They only ever pass and when they fail we just fix them so they pass again! It’s completely redundant!!! An exercise in absolute futility!
Dev: …19 -
- Hey I have to add new field, but this class is autogenerated, I do not know what tool generates it"
- Your fingers
- But this class has over 20k lines of codes and the header says it is autogenerated.
- It is a inside joke, it was generated by hand6 -
Static HTML pages are better than "web apps".
Static HTML pages are more lightweight and destroy "web apps" in performance, and also have superior compatibility. I see pretty much no benefit in a "web app" over a static HTML page. "Web apps" appear like an overhyped trend that is empty inside.
During my web browsing experience, static HTML pages have consistently loaded faster and more reliably, since the browser is immediately served with content useful for consumption, whereas on JavaScript-based web "apps", the useful content comes in **last**, after the browser has worked its way through a pile of script.
For example, an average-sized Wikipedia article (30 KB wikitext) appears on screen in roughly two seconds, since MediaWiki uses static HTML. Everipedia, in comparison, is a ReactJS app. Guess how long that one needs. Upwards of three times as long!
Making a page JavaScript-based also makes it fragile. If an exception occurs in the JavaScript, the user might end up with a blank page or an endless splash screen, whereas static HTML-based pages still show useful content.
The legacy (2014-2020) HTML-based Twitter.com loaded a user profile in under four seconds. The new react-based web app not only takes twice as long, but sometimes fails to load at all, showing the error "Oops something went wrong! But don't fret – it's not your fault." to be displayed. This could not happen on a static HTML page.
The new JavaScript-based "polymer" YouTube front end that is default since August 2017 also loads slower. While the earlier HTML-based one was already playing the video, the new one has just reached its oh-so-fancy skeleton screen.
It would once have been unthinkable to have a website that does not work at all without JavaScript, but now, pretty much all popular social media sites are JavaScript-dependent. The last time one could view Twitter without JavaScript and tweet from devices with non-sophisticated browsers like Nintendo 3DS was December 2020, when they got rid of the lightweight "M2" mobile website.
Sometimes, web developers break a site in older browser versions by using a JavaScript feature that they do not support, or using a dependency (like Plyr.js) that breaks the site. Static HTML is immune against this failure.
Static HTML pages also let users maximize speed and battery life by deactivating JavaScript. This obviously will disable more sophisticated site features, but the core part, the text, is ready for consumption.
Not to mention, single-page sites and fancy animations can be implemented with JavaScript on top of static HTML, as GitHub.com and the 2018 Reddit redesign do, and Twitter's 2014-2020 desktop front end did.
From the beginning, JavaScript was intended as a tool to complement, not to replace HTML and CSS. It appears to me that the sole "benefit" of having a "web app" is that it appears slightly more "modern" and distinguished from classic web sites due to use of splash screens and lack of the browser's loading animation when navigating, while having oh-so-fancy loading animations and skeleton screens inside the website. Sorry, I prefer seeing content quickly over the app-like appearance of fancy loading screens.
Arguably, another supposed benefit of "web apps" is that there is no blank page when navigating between pages, but in pretty much all major browsers of the last five years, the last page observably remains on screen until the next navigated page is rendered sufficiently for viewing. This is also known as "paint holding".
On any site, whenever I am greeted with content, I feel pleased. Whenever I am greeted with a loading animation, splash screen, or skeleton screen, be it ever so fancy (e.g. fading in an out, moving gradient waves), I think "do they really believe they make me like their site more due to their fancy loading screens?! I am not here for the loading screens!".
To make a page dependent on JavaScript and sacrifice lots of performance for a slight visual benefit does not seem worthed it.
Quote:
> "Yeah, but I'm building a webapp, not a website" - I hear this a lot and it isn't an excuse. I challenge you to define the difference between a webapp and a website that isn't just a vague list of best practices that "apps" are for some reason allowed to disregard. Jeremy Keith makes this point brilliantly.
>
> For example, is Wikipedia an app? What about when I edit an article? What about when I search for an article?
>
> Whether you label your web page as a "site", "app", "microsite", whatever, it doesn't make it exempt from accessibility, performance, browser support and so on.
>
> If you need to excuse yourself from progressive enhancement, you need a better excuse.
– Jake Archibald, 20139