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
-
Interview went well until i asked my questions about them.
"Are pet-projects a thing in your company"
... no.
"Can i attend programming gigs in a workweek, and are they paid by the company"
... no, no
"Any restrictions on the IDE"
... yes we only allow visual studio
"Wait, frontend web development in vs?"
... yes
"Do you develop in other languages then JavaScript"
... only Java
I calmly stood up, told them "I dont think that the company and I are a good fit. Thanks for your time."22 -
We need more JS devs for our frontend.
After half a year of PM complaining that he doesn’t find devs, he finally came back to us:
„Sorry guys, I found two devs, but they are not Java developers, they only do JavaScript“
Me:
Team:
*both speechless*
TeamLead: „... wait, you searched for Java devs half a year?“25 -
So, you start with a PHP website.
Nah, no hating on PHP here, this is not about language design or performance or strict type systems...
This is about architecture.
No backend web framework, just "plain PHP".
Well, I can deal with that. As long as there is some consistency, I wouldn't even mind maintaining a PHP4 site with Y2K-era HTML4 and zero Javascript.
That sounds like fucking paradise to me right now. 😍
But no, of course it was updated to PHP7, using Laravel, and a main.js file was created. GREAT.... right? Yes. Sure. Totally cool. Gotta stay with the times. But there's still remnants of that ancient framework-less website underneath. So we enter an era of Laravel + Blade templates, with a little sprinkle of raw imported PHP files here and there.
Fine. Ancient PHP + Laravel + Blade + main.js + bootstrap.css. Whatever. I can still handle this. 🤨
But then the Frontend hipsters swoosh back their shawls, sip from their caramel lattes, and start whining: "We want React! We want SPA! No more BootstrapCSS, we're going to launch our own suite of SASS styles! IT'S BETTER".
OK, so we create REST endpoints, and the little monkeys who spend their time animating spinners to cover up all the XHR fuckups are satisfied. But they only care about the top most visited pages, so we ALSO need to keep our Blade templated HTML. We now have about 200 SPA/REST routes, and about 350 classic PHP/Blade pages.
So we enter the Era of Ancient PHP + Laravel + Blade + main.js + bootstrap.css + hipster.sass + REST + React + SPA 😑
Now the Backend grizzlies wake from their hibernation, growling: We have nearly 25 million lines of PHP! Monoliths are evil! Did you know Netflix uses microservices? If we break everything into tiny chunks of code, all our problems will be solved! Let's use DDD! Let's use messaging pipelines! Let's use caching! Let's use big data! Let's use search indexes!... Good right? Sure. Whatever.
OK, so we enter the Era of Ancient PHP + Laravel + Blade + main.js + bootstrap.css + hipster.sass + REST + React + SPA + Redis + RabbitMQ + Cassandra + Elastic 😫
Our monolith starts pooping out little microservices. Some polished pieces turn into pretty little gems... but the obese monolith keeps swelling as well, while simultaneously pooping out more and more little ugly turds at an ever faster rate.
Management rushes in: "Forget about frontend and microservices! We need a desktop app! We need mobile apps! I read in a magazine that the era of the web is over!"
OK, so we enter the Era of Ancient PHP + Laravel + Blade + main.js + bootstrap.css + hipster.sass + REST + GraphQL + React + SPA + Redis + RabbitMQ + Google pub/sub + Neo4J + Cassandra + Elastic + UWP + Android + iOS 😠
"Do you have a monolith or microservices" -- "Yes"
"Which database do you use" -- "Yes"
"Which API standard do you follow" -- "Yes"
"Do you use a CI/building service?" -- "Yes, 3"
"Which Laravel version do you use?" -- "Nine" -- "What, Laravel 9, that isn't even out yet?" -- "No, nine different versions, depends on the services"
"Besides PHP, do you use any Python, Ruby, NodeJS, C#, Golang, or Java?" -- "Not OR, AND. So that's a yes. And bash. Oh and Perl. Oh... and a bit of LUA I think?"
2% of pages are still served by raw, framework-less PHP.32 -
So my school got invited to this coding competition for high-schoolers and among them, I was a part member and part mentor along side our CS professor since I was the most proficient coding stuff (although most of I do were JS and Python stuff although i can read other code)
Then this guy showed up.
He was picked by the faculty to take the WebDev competition. He knows how to use Photoshop for Photo retouchings and stuff but here's a problem.
He can't code nor make a proper website design.
So being the kind person I am, I volunteered to teach him what I know about frontend and HTML. This goes on for 4 weeks of nonstop practices, coding sessions and finally, Code In The Dark-style practice (which involves the person to code a full website for only 15 minutes).
When he was able to finish and mastered some of what I taught. I gave him the go signal and we were on to the road to victory.
Unfortunately our first try, we won nothing.
He said after the competition "I give up man, I can't take this!" but I said, "Just because you lost a f*cking competition once, doesn't mean you're a motherf*cking loser in life. There's still one more chance."
So I pressured our WebDev guy to be more better, taught him about mockups, JavaScript and etc.
Then the second attempt a year later, me and the WebDev guy won and moved on the finals. However, he didn't win the finals and I was the lone champion reprsenting our school.
Although he didn't win, he was happy I carried the torch and win the prize.
Prior to that, he asked me "Hey, how to be like you?"
I only answered, "Achievements are just gold with cloth and paper. Wear it lightly".
Fast forward to today, he's now the school's head design coordinator and layout designer for their newspaper column. He also practices his coding skills by frequenting on our coding sessions even when the competition was over.
But whenever someone asks "who taught you this?" he would only look to me, smile and say "that person right there".7 -
The last two frontend devs I interviewed.
First:
He had 15 some years of experience, but couldn't answer our most basic of technical questions, we stopped asking after the first couple.
Based on a technical test I got the impression that he couldn't distinguish between backend and frontend.
So, I posed a simple question "Have you interfaced with REST API'S using Javascript before?"
Which lead him to talk about arrays. I shit you not he droned on about arrays for five minutes.
"I have experience using big array, small arrays, breaking big arrays into littler arrays and putting arrays inside other arrays."
Never been in an interview situation where I've had to hold back laughter before. We refer to him as the array expert.
His technical knowledge was lacking, and he was nervous, so he just waffled. I managed to ease his nerves and the interview wasn't terrible after that, but he wasn't what we were looking for.
Second:
This was a phone interview.
It started off OK he was clearly walking somewhere and was half preoccupied. Turns out he was on his way back from the shop after buying rolling papers (we'd heard him in the shop asking for Rizla), and he was preoccupied with rolling a joint.
We started asking some basic technical questions at which point he faked that he'd seen a fight in the street.
We then called him back five minutes later you could hear him smoking "ah, that's better". After that the interview was OK, not what we were looking for, but not bad.
Top tip: If you require a joint to get through a phone interview, roll and smoke it before hand.17 -
Interviewer: "Hi, we are searching for a junior frontend dev with 1 year of experience and strong skills with Angular".
Me: "I have never used Angular before but I have 4 years of experience, It's not a problem for me to study it and use it quickly".
Interviewer: "Eh no, we are searching for someone with very strong Angular skills".
Me: "That's fine, but sorry how can a junior dev with just 1 year of experience have already strong skills with Angular? He must have also strong skills with JavaScript in general and It's quite impossible".
Interviewer: "Ehh... ehm.... ehmm..."11 -
I’m surrounded by idiots.
I’m continually reminded of that fact, but today I found something that really drives that point home.
Gather ‘round, everybody, it’s story time!
While working on a slow query ticket, I perused the code, finding several causes, and decided to run git blame on the files to see what dummy authored the mental diarrhea currently befouling my screen. As it turns out, the entire feature was written by mister legendary Apple golden boy “Finder’s Keeper” dev himself.
To give you the full scope of this mess, let me start at the frontend and work my way backward.
He wrote a javascript method that tracks whatever row was/is under the mouse in a table and dynamically removes/adds a “.row_selected” class on it. At least the js uses events (jQuery…) instead of a `setTimeout()` so it could be worse. But still, has he never heard of :hover? The function literally does nothing else, and the `selectedRow` var he stores the element reference in isn’t used elsewhere.
This function allows the user to better see the rows in the API Calls table, for which there is a also search feature — the very thing I’m tasked with fixing.
It’s worth noting that above the search feature are two inputs for a date range, with some helpful links like “last week” and “last month” … and “All”. It’s also worth noting that this table is for displaying search results of all the API requests and their responses for a given merchant… this table is enormous.
This search field for this table queries the backend on every character the user types. There’s no debouncing, no submit event, etc., so it triggers on every keystroke. The actual request runs through a layer of abstraction to parse out and log the user-entered date range, figure out where the request came from, and to map out some column names or add additional ones. It also does some hard to follow (and amazingly not injectable) orm condition building. It’s a mess of functional ugly.
The important columns in the table this query ultimately searches are not indexed, despite it only looking for “create_order” records — the largest of twenty-some types in the table. It also uses partial text matching (again: on. every. single. keystroke.) across two varchar(255)s that only ever hold <16 chars — and of which users only ever care about one at a time. After all of this, it filters the results based on some uncommented regexes, and worst of all: instead of fetching only one page’s worth of results like you’d expect, it fetches all of them at once and then discards what isn’t included by the paginator. So not only is this a guaranteed full table scan with partial text matching for every query (over millions to hundreds of millions of records), it’s that same full table scan for every single keystroke while the user types, and all but 25 records (user-selectable) get discarded — and then requeried when the user looks at the next page of results.
What the bloody fucking hell? I’d swear this idiot is an intern, but his code does (amazingly) actually work.
No wonder this search field nearly crashed one of the servers when someone actually tried using it.
Asdfajsdfk.21 -
Working with a "senior frontend developer"
HIM: committed this code, and took him 2 weeks before his first commit on our project
var str = ''
if (string == 'String Here') {
str = 'stringhere'
} else if ( string == 'Another String Here') {
str = 'anotherstringhere'
} and so on ...
ME: WTF?
ME: can we do it like this?
ME: str = string.replace(/\s/g, '').toLowerCase()
Maybe he is senior by age :D10 -
Recently i had to interview a guy with 10 years of frontend experience for a react developer role
Me : Do you know what ecmascript is ?
Him : Yes
Me : Which version would you prefer to use and why ?
Him : I dont use it. I am more comfortable with JavaScript.
Me : (totally confused) 😶
Him : (trying to be oversmart) I know you young guys prefer to use these fancy frameworks because you dont know how powerful raw javascript is.
Me : (Trying hard to not "react") Ok.
How would you "react" to this ?31 -
Hey @Root! I know you won't have time to finish Ticket A before holiday vacation, so work on Ticket B instead.
I finished Ticket A in time. except for converting/fixing some horrible spaghetti monstrosity. More or less: "we overwrote this gem's middleware and now it calls back into our codebase under specific circumstances, and then calls the gem again, which calls the middleware again." Wtf? It's an atrocity against rationality.
The second day after vacation:
Hey @Root, drop Ticket B and work on Ticket C instead. Can you knock this out quick, like before friday? ... Uh, sure. It looks easy.
Ticket C was not easy. Ticket C was a frontend CSS job to add a print button, and for unknown reasons, none of the styles apply during printing. The only code involved is adding a button with a single line of javascript: `window.print()`, so why give it to the chick who hasn't been given a frontend ticket in over a year? Why not give it to the frontend guy who does this all day every day? Because "do it anyway," that's why.
And in somewhere between 13 (now 5) minutes and two hours from now, I'm going to have a 1:1 with my boss to discuss the week. Having finished almost all of Ticket A won't matter because it's not a "recent priority" -- despite it being a priority before, and a lot of work. I've made no progress on Ticket B due to interruptions (and a total and complete lack of caring because I'm burned out and quite literally can no longer care), and no progress on ticket C because... it's all horribly broken and therefore not quick. I assigned it to Mr. Frontend, which I'll probably get chewed out for.
So, my 1:1 with bossmang today is going to be awful. And the worst part of all: I'm out of rum! Which means sobriety in the face of adversity! :<
but like, wtf. Just give me a ticket and let me work on it until it's done. Stop changing the damn priorities every other freaking day!16 -
Man, I think we've all gotten way too many of these.
Normally most interactions that I have are through email. Eventually some would try to contact me via phone. These are some:
"Hey! We are calling you from <whatever company name> solutions! (most of them always seem to end on solutions or some shit like that) concerning the Ruby on Rails senior dev opportunity we were talking about via email"
<niceties, how are you doing, similar shit goes here...eventually>
So tell us! how good/comfortable would you say you are with C++?"
Me: I have never done anything serious with c++ and did just use it at school, but because I am not a professional in it I did not list it in my CV, what does it have to do with Rails?
Them: "Oh the applications of this position must be ready to take in additional duties which sometimes happen to be C or C++"
Me: Well that was not anywhere in the offer you sent, it specifically requested a full stack Rails developer that could work with 3 different frontend stacks already and like 4 different databases plus bla bla bla, I did not see c++ anywhere in it. Matter of fact I find it funny, one of the things that I was curious about was the salary, for what you are asking and specifically in the city in which you are asking it for 75k is way too low, you are seriously expecting a senior level rails dev to do all that AND take additional duties with c++? cpp could mean a billion different things"
Them: "well this is a big opportunity that will increase your level to senior position"
Me: the add ALREADY asks for a senior position, why are you making it sound that I will get build towards that level if you are already off the bat asking for seniors only to begin with?
Them: You are not getting it, it is an opportunity to grow into a senior, applicants right now are junior to mid-level
ME: You are all not making any sense, please don't contact me again.
=======
Them: We are looking for someone with 15 years experience with Swift development for mobile and web
Me: What is up with your people not making these requirements in paper? if I knew from the beginning that you people think that Swift is 15 years old I would have never agreed to this "interview"
Them: If you are not interested in that then might we offer this one for someone with 10 years experience as a full stack TypeScript developer.
Me: No, again, check your dates, this is insulting.
===
* For another Rails position
Them: How good are you with Ruby on Rails in terms of Python?
Me: excuse me? Python has nothing to do with Ruby on Rails.
Her (recruiter was a woman) * with a tone of superiority: I have it here that Python is the primary technology that accompanies Rails development.
Me (thinking this was a joke) : What do you think the RUBY part of Ruby on Rails is for? and what does "accompanies Rails development" even means?
Her: Well if you are not interested in using Rails with Python then maybe you can tell us about your experience in using Javascript as the main scripting platform for Rails.
Me: This is a joke, goodbye.
====
To be fair this was years ago when I still didn't know better and test the recruiters during the email part of being contacted. Now a days I feel sorry for everyone since I just say no without even bothering. This is a meme all on itself which no one has ever bothered to review and correct in years for now. I don't know why recruiters don't google themselves to see what people think of their "profession" in order to become better.
I've even had the Java/Javascript stupidity thrown at me by a local company. For that one it was someone from their very same HR department doing the rectuiter, their shop foreman was a friend of the family, did him the service of calling him to let him know that his HR was never going to land the kind of developer they were looking for with the retarded questions they had and sent him a detailed email concerning the correct information they needed for their JAVAscript job which they kept confusing with Java (for some reason in the context of Spring, they literally wanted nothing with Spring, they wanted some junior to do animations and shit like that on their company's website, which was in php, Java was nowhere in this equation)
I think people in web development get the short end of the stick when it comes to retarded recruiters more than anywhere else.3 -
When you start a new job as a Senior Developer, and start asking questions about the code, and you have these collections of conversations with other front-end people:
Exhibit 1:
Me: Ahh so I see the filtering and pagination is all done with Javascript in the front end...
Random dev: No, it's done with Angular.
Exhibit 2:
Me: I think we should add frontend pagination to this page. There will be too many elements on it if you're a customer with 2000 servers.
Random dev: Don't bother, there's no pagination in the API call... So that will not gain any performance.
Me: But it wouldn't take long to implement and it would improve the user experience, why would you want to show ALL the elements, when you have an option not to... Also, it WILL be a major performance hit, especially on mobile.
Random dev: People will use search anyway.
😥🔪
Also, there are no coding standards, every file looks different, and my opinion is being disregarded in everything, and I thought my last job was bad...
Seriously how are some people hired as front-enders?
Since I just took this job, I feel obligated to stay a couple of months... But hey, don't cry for me, I might have more rants for you. 😂
Sorry for the long rant, here's cake: 🍰5 -
Just learned that my previous workplace hired someone to take over the frontend which was my first big javascript project, and now I have an odd fear for my life.3
-
I was a midweight dev acting as a lead dev on the frontend development of a project. I had already built most of it, it was all vanilla JavaScript, had no jQuery, the code was simple, fast, and small. Then I went on holiday and the company put a senior lead on the project to carry out remaining work while I was away.
When I came back, there was a bug in the age gate page and I started to investigate. I then noticed that the asshole added jQuery to the code just to select the country and date of birth input fields. That idiot, a senior lead dev earning more than twice what I earned, didn’t know how to select some elements on a page! I nearly lost my temper when I saw the added bloat.7 -
My Typical Project
1. Identify common problem
2. Investigate options
3. Come up with clever solution
4. Implement backend solution
5. Get fed up with current frontend
6. Investigate other frontend
7. Realize perpetual chaos in Javascript landscape
8. Lie down in a corner
9. Cry myself to sleep4 -
Colleague: You know something about Java, right?
I: Yes..
(colleague shows some FRONTEND JAVASCRIPT and asks a question about it, FYI i am a BACKEND JAVA dev)
🙄😒2 -
I'm so sick of all these fat frontend websites.
Transferring dozens of megabytes of mostly unused libraries is not acceptable.
A browser tab crunching up CPU time because everything must be "beautifully animated" (🤢) and processed without involving page reloads/backend is not acceptable.
A response time of over a second is not acceptable.
Cryptic error messages and random popups asking you to reload your page, not acceptable.
Sticky elements/popups breaking access on small screens is not acceptable.
Running hundreds of ajax calls per minute as heartbeats/probes
and crashing the page when the internet has a hiccup, not acceptable.
Fuck Asana, Fuck Twitch, Fuck LinkedIn, Fuck Youtube, Fuck the dozens of other SPAs which unload their truckload of diarrhea into a tab, yet fail to load crucial functionality about half of the time.
Fuck any page that breaks when you block Facebook, Doubleclick, Twitter or Google Analytics. To hell with websites depending on cookies or javascript loaders to display anything.
I want webpages to be interactive informational documents again.
Fuck off with your apps.
If you want to make an app, learn to use a real language, and get the fuck out of my browser.5 -
I know a guy who writes everything in Haskell.
He started learning it because his parents got him into a math school (and math schools in Russia use either Python or Haskell), he liked it, but later he dropped out. Today, apart from Haskell, he only really knows HTML and CSS, and maybe some JavaScript.
He writes backend AND frontend in Haskell and uses some kind of JRPC stuff to manage all that. He told me that his life is a pure heaven. He IS RELEVANT (!!!!!!), his apps always run without bugs (because in Haskell you can mathematically prove that there are no bugs), they are performant, faster than C (because you can't write a complex enough app in C that will be as efficient as compiled Haskell, because it's you vs compiler). He doesn't have any problems in life whatsoever. He never got burned out, he never got anxiety or depression. He doesn't act pretentiously and stuff, he's just a normal person who rarely even mentions that he can program.
Science says it can't be done! You can't only know Haskell and be a relevant software engineer! You know what, he didn't _know_ it was impossible. He's like that grandpa from a meme, he got Alzheimers, but because of it he forgot that he had Alzheimers, and now remembers everything.
The fun thing is that he looks like a typical gopnik, with adidas suits and stuff.
What a gem of a person.26 -
Would the web be better off, if there was zero frontend scripting? There would be HTML5 video/audio, but zero client side JS.
Browsers wouldn't understand script tags, they wouldn't have javascript engines, and they wouldn't have to worry about new standards and deprecations.
Browsers would be MUCH more secure, and use way less memory and CPU resources.
What would we really be missing?
If you build less bloated pages, you would not really need ajax calls, page reloads would be cheap. Animated menus do not add anything functionally, and could be done using css as well. Complicated webapps... well maybe those should just be desktop/mobile apps.
Pages would contain less annoying elements, no tracking or crypto mining scripts, no mouse tracking, no exploitative spam alerts.
Why don't we just deprecate JS in the browser, completely?
I think it would be worth it.22 -
So this backend developer boasted.
"All the controls are in my hands.. you frontend developers are just the puppets of our API's".
Next day i did this:
If (email === '****') {
profilePicture = 'dick.jpg';
}5 -
What's the point of using a framework if you don't use any of its features!? What the heck, I have to fix this damn web frontend that is so broken in many ways.
Instead of using an authentication middleware, every single view has the same block of code to check if a user is authenticated. Instead of templates, they used static HTML/JavaScript files and they passed data to pages through cookies.
The "REST" API is so messed up, nothing is resource-oriented, HTTP methods are chosen randomly as well as status codes. They are returning "412 Precondition Failed" instead of a plain simple "401 Unauthorized" when you're not authenticated! What the hell, did they even bother to check what 412 is about when they copied and pasted it from a crappy website!? I would never come up with 412, not even in my scariest nightmare.
What kind of drugs were they using when they wrote such code? Oh dear, I need a vacation...2 -
Today a colleague of mine asked me to help with some javascript. So I said sure, it will be done in 5 minutes. Im a fullstack developer with a focus on backend in this project.
So I opened the frontend part and was amazed how shit the javascript file was. Yes you read it right FILE...
One big file with a lot of variables in the window scope.
Because she was in “charge” of the frontenders because she works there a bit longer then me I never checked the frontend code.
I said I wont/cant help unless I see better code. I explained to a trainee what could be done to change it and Im impressed that the trainee did a better job then the employee and quick as well.
Got the whole code in seperate files with each part of the code in seperate scopes within 2 hours.
What Im saying here is that even as student, intern or trainee you can know things better thsn someone with experience, dont be afraid to speak up. Because everyone can learn from eachother.7 -
For my very first job interview, I joined a rather well known company (somewhere in the mid-ranges) as an intern-frontend developer. Everything was going okay-ish. I was asked some technical questions and I answered them to the best of my knowledge, and it was all good until he came to the javascript questions.
Interviewer: So, have you worked with any frontend frameworks?
Me: Yeah, I usually work with vanilla JS, but I've gotten into frameworks like Backbone and Ember.
Interviewer: I've never heard of those. Do you know AngularJS?
Me: I've dabbled aroudn with it, although I haven't gotten into it much. If you want me to use AngularJS, I can pick it up and get the ropes of it pretty quick.
Interviewer: So tell me.. what is AngularJS?
Me: It's a Javascript framework released by Google (explains what it is and how it differs from most popular JS frameworks, explains the components of Angular.. etc)
Interviewer: Well, you're wrong. It's an enhanced html for web-apps. ( or some bullshit he quoted off the front-page of the then angularjs.org homepage )4 -
First time my laptop acted as a CV.
I've been in a personal project with my pal for like a three months. We meet sometimes at a cafe which is a very nice workplace, we often see more people with laptops, so we are not the only ones that thinks so.
My pal was waiting for me, he got a table early and then I arrived. there was a guy nearby us.
Me: (this guy has a newest new macbook pro, fucking riche)
-- I sit, put my laptop and start to work with my pal --
The guy starts looking at my stickers without hiding his doing at all. I noticed that instantly
Me: (Crap, he's gonna ask something :( )
-- I kept discussing stuff with my pal for like 5 minutes and then it happened. the guy stands up and... --
Guy: hey! how are you? sorry for bother, are you perhaps developers? I'm asking because I saw your stickers
Me: mmm yes
Guy: Do you have a job currently?
Me: We are in a project (No need to mention this is personal project and I got my full time job)
Guy: Oh, ok, no problem, you see I got a company, and currently we are looking for people to work with us, we want frontend developers with javascript skills preferable, but anything is welcome. Interviews starts next week, so if you are interested or know someone that could be, I'll give you my card and please write me at my mail if anything.
Me: got it, no problem.
-- I tried my best to hide my displeasure face(but I think I showed it a little), for him to being a riche with a new macbook pro, and you know, the interruption, I wanted to be focused while working in da project --
-- I got the card, I read it a bit, didn't dig into too much, there was stuff to do at the moment. the guy already returned to his chair and my friend --
Pal: Excuse me Mr Guy, what's the job tittle?
Me: (FUCK! dude!, we're working in our shit, don't give him more reason to try to scout us. we are behind the schedule and I need to explain this shit to you FFS)
Guy: Oh yes, will be frontend developer(again), but if you are a full stack that will be a plus too, we got some stuff with angular 1.x(ugh), and sencha touch(ugh) and ...(don't remember what else was it)
Pal: Ok and the job is full time in site? or are you open to work remotely
Me: (ok man, you sound interested, that makes me look interested too >:( )
Guy: preferable in site, but we would consider remotely depending on the person.
Pal: Good! thank you very much Mr. X
Guy: cool
-- Later on, like two hours, my friend goes to the counter for more coffee --
-- I text him: dude, I feel the guy will kidnap me or something --
-- then the guy start looking again at my laptop and... ---
Guy: hey! Jhon was your name right? Do you have experience with devops? I see your aws stickers
Me: yes
Guy: do you have experience with microservices?
Me: yes, a bit with lambda, also I've done some stuff with kubernetes, opsworks, rds and whatnot. no biggie
Guy: oh cool! we have a devops job too, there is a migration we need to do for an app to micro services. again if you are interested or know someone that it does. please mail me :)
Me: gotcha
There were no further interactions with Mr. Guy the rest of the day.
I'll be thrilled if someone ask me about my bee and puppycat sticker
12 -
I lost my job 😅 tbh did me a favour. I was backend, this guy was frontend and was a typical opinionated JavaScript, magpie dev and I just did not give 2 fucks about what he thought was “amazballs” and we had a small tiff, we’ll he was arguing, I was trying to do my job and I just didn’t care enough about his feelings on the subject, forget what it was about but I think it was trivial. But anyway, I was let go soon after 😅16
-
Modern web frontend is giving me a huge headache...
Gazillion frameworks, css preprocessors, transpilers, task runners, webpack, state management, templating, Rxjs, vector graphics,async,promises, es6,es7,babel,uglifying,minifying,beautifying,modules,dependecy injection....
All this for programming apps that happen to run inside browsers on a protocol which was designed to display simple text pages...
This is insanity. It cannot go on like this for long. I pray for webasm and elm to rescue me from this chaos.
I work now as a fullstack dev as my first job but my next job is definitely going to be backend/native stuff for desktop or mobile. It seems those areas are much less crazy.10 -
It was when I ditched React. I replaced it with raw JavaScript, with frontend being built with Gulp and Twig (just because HTML has no includes). Here are the results:
1. Previously, a production frontend build took 1.5 minutes. Build time became so fast that after I push the code, the build was done before me going to Netlify to check build status. I go there, and it’s almost always already done.
2. In a gallery with a lot of cards, with every card opening a modal, the number of listeners was reduced from N to one. With React, I needed 1000 listeners for 1000 cards. With raw JavaScript, I needed just one click listener with checking event target to handle all of the cards.
3. Page load time and time-to-interactive was reduced from seconds to milliseconds.
4. Lighthouse rating became 100 for desktop and 93 for mobile.
But there is one more thing that is way better than all of the above: cognitive complexity.
Tasks that took days now take hours. Tasks that took hours now take minutes.
Tasks that took thousands of lines now take hundreds. Tasks that took hundreds of lines now take tens.
In real business apps, it is common to build features and then realize it’s not needed and should be discarded. Business is volatile, just because the real world is volatile too. With this kind of cost reduction per feature, it became way less painful to discard them. Throwing out something you spent time and emotional resource on doesn’t feel good. But with features taking minutes to build, it became easier.25 -
Me: I want to try Angular2 as a frontend framework.
Boss: Just use jQuery.
Me: That's not a framework but syntactic sugar for JavaScript. I rather not use it at all and rely more on ES6 shims. Let's maybe try vuejs.org?
Boss: Other devs know jQuery, just write it in jQuery. We'll need to build it fast and you have used jQuery before, haven't you?
Me: Yes, but ...
Boss: And you haven't used these recommendations.
Me: Yes, but ...
Boss: I won't take the risk. I want something that is known to work.
Me <dying on the inside>: If you insist.
Image source: https://hakanforss.wordpress.com/20...
PS: I don't work there anymore ;)
11 -
Today I learned that someone wrote a Python interpreter in JavaScript called Brython. So now you can include a framework to write shitty code in a buggy framework and tell your users to throw more hardware at it.
The guy I heard this from also believed that his code would somehow be "compiled" rather than what's essentially a framework be loaded and then execute code in a language not native to the browser...
So now you can write JavaScript where it doesn't belong in Node and write Python where it doesn't belong through a framework. Frontend and backend are so passé, we might as well start calling it fluid instead.
FULLSCHTAK!!!
🙂🔫21 -
Stupid javascript.
Stupid hoisting-oblivious "frontend devs."
Stupid browser-specific javascript behavior.
Stupid thrown-together javascript minifier that literally only strips out whitespace and comments.
Stupid poorly-written javascript spamming my api.
Time to rewrite it. Grumble grumble. Soo not how I wanted to spend my morning-turn-afternoon.
Leading to the last but not least:
Stupid me forgetting javascript's quirks.12 -
Marketing pushed deadline for release one week earlier. That sucks.
What sucks even more is that frontend was not ready, but our frontend guy promised to take a look over the weekend and finish it. Thats cool we might make.
What sucks is that he fixed one small issue on Sunday 9PM and left the whole thing unusable.
So guess who was googling till 4am how to do stuff in bloody javascript?
In the end, I beleive I did a decent job and we ca release some kind of alpha and get rid of my dirty hacks later. That's how you get technical debt.
Now lets see what my boss thinks about it and if we are really going to release it or if I'm going to kill somebody.6 -
In the Ruhr area (Germany) we have some very old, very strange words with strange meanings. One of those words is ‚Prutscher‘.
A Prutscher refers to a person who does things but never gets a good result, due to lack of knowledge or simple carelessness. Most of the time, Prutschers are people who are interested in certain subjects and often work in the related jobs, but who lack the motivation to properly train themselves, learn what there is to learn and to always keep up with their technologies .
Here are a few examples I've stumbled upon so far in my career:
- Developers in their 60's who read a book about PHP 25 years ago and decided to become a software developer. Since then haven't read anything about it. Who then now build huge spaghetti monoliths for large companies, in which they prefix every function, every variable and constant with their initials and, of course, use Hungarian notation.
- People who read half a fucking tutorial about <insert any fancy js framework here> and start blogging/tweeting about it
- Senior web developers who need to be told what the fuck CORS is and who can't even recognize CORS related errors in their browser console.
- People who have done nothing else for 18 years than building websites for companies on Wordpress 1.x and writing few lines of PHP and Javascript from time to time. Those who are now applying as a frontend dev due to the difficult economic situation and are surprised that they are not accepted due to a lack of experience.
- Developers who are the only ones working on Windows in the team and ask their Linux colleagues for help when Windows starts bitchin.
- People who have been coding for 30 years, have worked with ~42 languages and don't know the difference between compiled and interpreted languages in the job interview.
- Chief developers at a large newsletter-publisher who think it's a good idea to build your own CMS (due to a lack of good existing ones, of course).
- Developers who have been writing PHP applications for multinational corporations for 25 years and cannot explain how PHP is executed. They don't even know what the fucking OPcache is, let alone fpm. FML
- People who call themselves professional developers but never ever heard of DRY, KISS, boy-scout rule, 12-Factor App, SOLID, Clean Code, Design Patterns, ...
- Senior developers wondering why the bash script won't run on their fucking Windows machine.
- Developers who consider Typescript to be a hindrance and see no value in it.
- Developers using ftp for deployments in 2022
- Senior Javascript Developer applying for a job and for whom Integer is a primitive data type in JS.
- Developers who prefer to code without frameworks and libraries because they are only an unnecessary burden/overhead and you can quickly code everything up yourself.
- Developers who think configuring their server(s) manually is a good idea.
You fucking Prutscher. What you have already cost me in terms of work and nerves. I can't even put it into words how deeply I despise you. I have more respect for the chewing gum that has been stuck in my damn trash can for the past 3 years than I do for you guys. You are the disgrace of our profession. I will haunt you in your dreams and prefix every fucking synapse of your brain with MY initials.
As a well-known german band once sang in a very fitting song: I wouldn't even piss on you if you were on fire.
If you recognized yourself in one of the examples here: FUCK YOU!29 -
Shitty-Clent-side: Onclick of submit button, send request to server
Server: Responds with a 500 error.
Shitty-Client-Side: change "Submit" to "Submitted" and backgroumd color to green(because UX is important and error handling can go to hell)1 -
- Team_leader_1: I know you're a frontend developer, but trust me NodeJS has threads :) sync operations don't block the main thread :)
- Team_leader_2: You need to study the theory :) NodeJs can handle further operations during the sync function :) it spawns a new thread, you haven't studied Javascript well enough :)
- Me, very ready to dab on 2 condescending little fucks:
16 -
Why the fuck does people who teach in professional colleges doesn't have the mindset to update their godamnn fucking dinosaur knowledge to the least basics of modern technology.
Had to do this mini-project for uni, and the languages allowed included java, python, php or any similar frontend tools for creating desktop app or web app. I planned on taking React + Express cz apparently that'll fall in the category.
Now she starts yelling at my project saying its not allowed and when I fucking asked her "can I use node.js which is basically javascript" she said yes.
And for gods sake she has a Masters degree and phd but doesn't even know what's the difference between get and post request!! Fed up with this college shit!!7 -
I cant fucking wait for the day when i dont have to do fucking frontend just give me a backend, even fucking php is fine just get me away from javascript this is hell this is torture help9
-
Why the hell does every single frontend job on Earth require expert knowledge of React, a fad JS library that will be forgotten in 5 years?
For extra credit: when was the sage advice of "keep content, appearance, and behavior separate" overruled in favor of "use JavaScript for literally everything"? Have I been in a coma for the past 3 years?
Look, I understand the appeal of separating code into repeatable components. I just don't understand why essentially the same thing can't be accomplished with vanilla JS, which is ten times easier to understand and doesn't require an entire website to be written in some make-believe offshoot of Ecmascript that will look like hieroglyphics a decade from now.
There are also seemingly no positions that offer people a platform to start applying React to real world scenarios. I've seen the "understand React in 5 minutes" articles. Wow, super cool, you used 30 lines of JavaScript to render a "Hello world" div. The possibilities are truly endless.
But seriously, how does this shit work? Where do I go to learn the mystical art of offloading every single one of a website's responsibilities to JavaScript? How do I use React to build an actual functioning website, and at what point will it save me time or increase my productivity instead of just pissing me off?17 -
I feel like the web frontend landscape has gone to hell...
It used to be a priority to develop lean front end applications that load fast and work the same on most devices. If resources are required you try to share them. I have always liked the way this was solved using CDN.
Proper workflow: include some small libs you might need, script your interactions, test site, deliver.
And now our friends of the Javascript community have discovered the nuclear science called npm... It started off as this great benefit allowing frontenders to complete entire projects in the language they know and love but I feel like it has grown into an abomination that produces bulky applications with more boilerplate configuration than actual active code...
Surely I can't be the only one who is completely fed up with the direction this is going? Is anyone else looking for a lean way of developing javascript again using only a couple of small libs instead of those monstrous frameworks.
I have even considered to develop a library that makes it easy to develop with CDN (and dependencies) in mind but I don't even know if it will be worth it as more and more people tend to move away from it.
I'm sad10 -
Frontend Developer wanted. Required skills: C#, PHP, MySQL, HTML, CSS, Jquery, Java, JavaScript, React, Angular, Vue, Laravel, Wordpress, Shopify, Docker, Git, SVN, Ruby.
Must have at least 3 years of working experience in a high level company. Only worked for A+ clients and ultra high traffic websites.
Also nice would be UX/UI, Design Systems, Wireframing.
Experienced in sales and cleaning floors. Getting coffee putting music on etc
Salary indication: €18009 -
I work in a contract position and reviewed the code of a senior engineer recently. Regretfully I can't provide context to preserve anonymity.
He wrote awful JavaScript;
- handled a single DOM element with 2 different frontend libraries
- used the logical operator && to 'chain' two methods (it didn't work) instead of returning a boolean value,
- broke everything down into minute detail (a comment box had 7 components!),
- API calls were made for every component update instead of maintaining local component state where it made sense, which meant UI updates were slow,
- animated EVERYTHING, which made my Firefox on Xubuntu i7 64bit with 16GB RAM beg for mercy.
I had a rough couple of months with interviews, with 2nd stage technical interviewers throwing impossible tasks at me.
Example:
1. Create an online Python code editor with Javascript which can compile Python bytecode,
2. Use Mesos and Kafka to create real time architecture for Tensorflow with a Javascript frontend in 1 day. (I asked, and wasn't allowed to use Kubernetes or serverless architecture),
3. Hack a website from the browser's address bar using parameters ( what?!! ),
Obviously, the next time I meet a 'senior', I'm going to tell him talk is cheap;
'SHOW ME YOUR CODE.'3 -
I fucking hate my boss so much
He looks down on me like I’m some idiot who doesn’t know his shit.
The other day he was trying to explain OAuth2.0 to me in the most dumbed down way ever, even after telling him I do already know how OAuth 2.0 works. He just said “oh well just making sure” and continued explaining it to me the exact same way. Felt shitty having something explained to you which you already know in such a way in front of all of your coworkers
Whenever I give my thoughts on something he answers with an argument that’s essentially true but pretty stupid:
B: “We don’t need to bundle our JS files” (see my other rant)
M: “Our load time is around 15 seconds though and it takes forever to update our script tags”
B: “Yes but it’s only 15 seconds once and the tags are already there so it’s fine”
How do you reply to something like that??
On top of that, his code is absolutely awful, always looks hacked together, lacks documentation and i don’t think he has written a unit test in his life
I don’t even like frontend, was told I would mostly do backend and it seems like all I’m doing recently is write fucking javascript because even if I wanted to write backend code, it’s nearly impossible to write clean code in this pile of horseshit codebase7 -
First post.
So, I've been teaching myself front-end for about 7 months now, and I'm really enjoying it, especially the actual programming aspect of JS. I also just started a new job, nothing to do with development, that I expected to be extremely boring and unfulfilling, as it doesn't fulfill any of my interests, but it'll pay my rent and it has decent benefits. I'll be mostly working with excel.
Now, like I mentioned, I'm really new to the dev world, just a little infant really. I know enough to know that I don't know shit. So, I was surprised to learn today that you can program in excel with VBA. I know the language gets a good bit of hate on here, I did a search before posting, and while I haven't started to learn it just yet (I'm starting tonight) I'm excited about. Firstly, because I'll get to do coding for my job, something I'm interested in, and secondly, because if I can figure out how to automate part of what I do well enough that it's implemented with the rest of the team, then maybe I'll be rewarded, and I'd be able to put professional coding experience on a resume for when I try to find a better job.
I've really enjoyed reading all the rants. They've been entertaining and also educational sometimes.
tl;dr Discovered VBA and was actually excited about it6 -
Not sure if you'd call this an insecurity but regardless; frontend.
Much of the stuff I develop is meant to be user/privacy friendly.
Like, at the moment I'm developing an end-to-end encrypted notes web application. The backend is a fucking breeze, the frontend is hell for me. I'm managing mostly but for example, I need to implement a specific thing/feature right now and while the backend would take me about 15-30 minutes, I've been only just thinking about how I'm going to do this frontend wise for the past few fucking hours.
My JavaScript skills are quite alright, html is manageable, css only the basics.
And before people tell me to just learn it; I. Fucking. Hate. Frontend. Development. My motivation for this is below zero.
But, most of the shit I write depends on frontend regardless!3 -
Everyone is on their vacation and I am in good mood so time to refactor some 3 year old frontend, angular, javascript code. After 5 minutes of looking, some great quality of code snippet on the image below.
10 -
Found an answer on Quora discouraging to learn Javascript because "it's not as important as php". It was a question about frontend development. Soooo 20002
-
I friend of mine was looking for an internship. I asked him what he wanted to do, he said frontend. I said do you know JavaScript. He said that's a long name I like to just call it Java.1
-
How Bad I'm at frontend Development: about 3 year ago i accidentally wrote </from> instead of </form> while working on the frontend of a website, everything just went bonkers. Took me 10+ hours to realize my mistake.
In my opinion frontend devs are real hero they have to learn multiple frameworks, and make website respinsive and work on IE at the same time. Idk Why the fuck clients still want their website to work on IE (fuck you Carl, your users are of age group 15-22 they don't even know wtf IE is)
P. S. At that time i didn't knew HTML validators are a thing.6 -
True story
> Got offer for nodejs via LinkedIn
> When I appeared, the interview was for Javascript and frontend
> "Based on your skills we are calling in you another interview for Sr. PHP developer"8 -
"I dont like the way that you splitted your code into multiple small files. Simply put every logic into one controller." - so called "frontend architect" after reviewing a team's Angular code. I dont know what to think.2
-
8 days and i'm never gonna touch Javascript, CSS, Angular and anything frontend-related for the rest of my life.
I cannot be happier.10 -
To all frontend webdevs here:
Explain to me how do you cope with all this insane clusterfuckness of frameworks, tools and js libraries.
Why is it so hard for a beginner like me to learn webdev? Android and backend are much more logical and sane. Even Node.js is pretty dope.11 -
Fuck JavaScript, seriously I have spent the last 8 hours trying to build a fucking basic search application that would take me < 1 hour in any other fucking programming language on the planet. I AM FUCKING DONE WITH THIS SHIT. I'd rather pay some dude with a long ass fucking beard who calls himself a "Frontend Engineer" WHATEVER THE FUCK THAT MEANS. Because my backend oriented brain cannot fucking handle all of the frameworks, and modules, and different versions of the same fucking language. Plus its like JavaScript was designed so that you can't not write spaghetti code. FUCK THIS. I'm going back to writing static fucking template code that is used by a fucking backend language that only changes every few fucking years, not every month.
Have a great day. :)4 -
Oh boy, this is gonna be good:
TL;DR: Digital bailiffs are vulnerable as fuck
So, apparently some debt has come back haunting me, it's a somewhat hefty clai and for the average employee this means a lot, it means a lot to me as well but currently things are looking better so i can pay it jsut like that. However, and this is where it's gonna get good:
The Bailiff sent their first contact by mail, on my company address instead of my personal one (its's important since the debt is on a personal record, not company's) but okay, whatever. So they send me a copy of their court appeal, claiming that "according to our data, you are debtor of this debt". with a URL to their portal with a USERNAME and a PASSWORD in cleartext to the message.
Okay, i thought we were passed sending creds in plaintext to people and use tokenized URL's for initiating a login (siilar to email verification links) but okay! Let's pretend we're a dumbfuck average joe sweating already from the bailiff claims and sweating already by attempting to use the computer for something useful instead of just social media junk, vidya and porn.
So i click on the link (of course with noscript and network graph enabled and general security precautions) and UHOH, already a first red flag: The link redirects to a plain http site with NOT username and password: But other fields called OGM and dossiernumer AND it requires you to fill in your age???
Filling in the received username and password obviously does not work and when inspecting the page... oh boy!
This is a clusterfuck of javascript files that do horrible things, i'm no expert in frontend but nothing from the homebrewn stuff i inspect seems to be proper coding... Okay... Anyways, we keep pretending we're dumbasses and let's move on.
I ask for the seemingly "new" credentials and i receive new credentials again, no tokenized URL. okay.
Now Once i log in i get a horrible looking screen still made in the 90's or early 2000's which just contains: the claimaint, a pie chart in big red for amount unpaid, a box which allows you to write an - i suspect unsanitized - text block input field and... NO DATA! The bailiff STILL cannot show what the documents are as evidence for the claim!
Now we stop being the pretending dumbassery and inspect what's going on: A 'customer portal' that does not redirect to a secure webpage, credentials in plaintext and not even working, and the portal seems to have various calls to various domains i hardly seem to think they can be associated with bailiff operations, but more marketing and such... The portal does not show any of the - required by law - data supporting the claim, and it contains nothing in the user interface showing as such.
The portal is being developed by some company claiming to be "specialized in bailiff software" and oh boy oh boy..they're fucked because...
The GDPR requirements.. .they comply to none of them. And there is no way to request support nor to file a complaint nor to request access to the actual data. No DPO, no dedicated email addresses, nothing.
But this is really the ham: The amount on their portal as claimed debt is completely different from the one they came for today, for the sae benefactor! In Belgium, this is considered illegal and is reason enough to completely make the claim void. the siple reason is that it's unjust for the debtor to assess which amount he has to pay, and obviously bailiffs want to make the people pay the highest amount.
So, i sent the bailiff a business proposal to hire me as an expert to tackle these issues and even sent him a commercial bonus of a reduction of my consultancy fees with the amount of the bailiff claim! Not being sneery or angry, but a polite constructive proposal (which will be entirely to my benefit)
So, basically what i want to say is, when life gives you lemons, use your brain and start making lemonade, and with the rest create fertilizer and whatnot and sent it to the lemonthrower, and make him drink it and tell to you it was "yummy yummy i got my own lemons in my tummy"
So, instead of ranting and being angry and such... i simply sent an email to the bailiff, pointing out various issues (the ones6 -
When someone asks you what programming language they should learn, don't tell them the one you prefer.
Instead, ask them what area they plan to focus on, like,
Web frontend: javascript
Web backend: javascript
Mobile apps: javascript
Games: javascript
AI: javascript6 -
Just had an interview with our new potential product manager. I companioned our CEO, if technical questions arise...
First, he came to our office, to the interview, and never..never looked at our application. Neither he saw some screenshots, review's or anything related to the product. As a potential product manager...gasp
And he really tried to impress me, by mentioning what a great full stack developer he also is (LOL), with years of experience in frontend and backend.
But, since I am an android software developer, he mentioned he don't like java. But he loves java script...
Me: ehhh what? So you compare apples to oranges. Why do you don't like java? (And I could image a lot things ...)
Him: because unlike JavaScript, java is a mess when writing code.
Me: ok Iam done.9 -
!rant, but kinda
My new director wants to buy a solution for a portal environment that my institution currently has. I have no qualms over it. My only issue was the company that sells it to be known to provide close to 0 fucking support when shit arises.
During a presentation we were told that they were using state of the art JAVA technology to render items on the page and that their ApI was easy for devs to grasp. This caught my attention since I know of very few and obscure Java frameworks that work with frontend tech (as in, your frontend logic is legit in Java)
The sales people proceed to show us React. Obviously thinking that no one knows what REact was. The dude continues with "This is new Java tech" all proud and shit prompting me to interject that it is "Javascript" the dude brushes it away saying "same thing" to which I reply with "Negative, please make sure that you properly discern Java from Javascript since Java is to Javascript as car is to carpet, completely different environments" the dude sarcastically says that "oh well, didn't know one of the people here was more aware of our own technology than we are" to which I say "and not only that, but the final say in us adopting your tech is mine, so I would rather you keep the sarcasm and the attitude to yourself, bring in a tech person if need be and learn these distinctions since we don't work with Java"
My new director later on went to talk to me since he apparently thought that Java and JS were related in some way. I can't really fault it, last time the dude touched programming was in the early 2000s, previous boss was a C and COBOL developer, but the previous dude would ALWAYS take my word no questions ask, this dude was there asking me if I was sure that Javascript and Java were really completely different environments asking me to show him.
I do not like to be questioned. I shoot the shit here and don't really involve myself with more technical aspects under this platform unless it involves concrete architecture discussions and even there I really don't care with engaging on a forum concerning that. But concerning my job I really.......really do not like to be questioned by people that know way the fuck less than me. I started coding when I was 17, I am 30 now, with a degree and years of experience. I really hate to be questioned by this dude.2 -
I have been keeping this inside for long time and I need to rant it somewhere and hear your opinion.
So I'm working as a Team Lead Developer at a small company remotely based in Netherlands, I've been working there for about 8 years now and I am the only developer left, so the company basically consists of me and the owner of the company which is also the project manager.
As my role title says I am responsible for many things, I maintain multiple environments:
- Maintain Web Version of the App
- Maintain A Cordova app for Android, iOS and Windows
- Working with pure JavaScript (ES5..) and CSS
- Development and maintenance of Cordova Plugins for the project in Java/Swift
- Trying to keep things stable while trying very hard to transit ancient code to new standards
- Testing, Testing, Testing
- Keeping App Stable without a single Testing Unit (sadly yes..)
- Just pure JavaScript no framework apart from JQuery and Bootstrap for which I strongly insist to be removed and its being slowly done.
On the backend side I maintain:
- A Symfony project
- MySQL
- RabbitMQ
- AWS
- FCM
- Stripe/In-App Purchases
- Other things I can't disclose
I can't disclose the nature of the app but the app is quite rich in features and complex its limited to certain regions only but so far we have around 100K monthly users on all platforms, it involves too much work especially because I am the only developer there so when I am implementing some feature on one side I also have to think about the other side so I need to constantly switch between different languages and environments when working, not to mention I have to maintain a very old code and the Project Owner doesn't want to transit to some more modern technologies as that would be expensive.
The last raise I had was 3 years ago, and so far he hasn't invested in anything to improve my development process, as an example we have an iOS version of the app in Cordova which of course involves building , testing, working on both frontend and native side and etc., and I am working in a somewhat slow virtual machine of Monterey with just 16 GB of RAM which consumed days of my free time just to get it working and when I'm running it I need to close other apps, keep in mind I am working there for about 8 years.
The last time I needed to reconfigure my work computer and setup the virtual machine it costed me 4 days of small unpaid holiday I had taken for Christmas, just because he doesn't have the enough money to provide me with a decent MacBook laptop. I do get that its not a large company, but still I am the only developer there its not like he needs to keep paying 10 Developers.
Also:
- I don't get paid vacation
- I don't have paid holiday
- I don't have paid sick days
- My Monthly salary is 2000 euro GROSS (before taxes) which hourly translates to 12 Euro per hour
- I have to pay taxes by myself
- Working remotely has its own expenses: food, heating, electricity, internet and etc.
- There are few other technical stuff I am responsible of which I can't disclose in this post.
I don't know if I'm overacting and asking a lot, but summarizing everything the only expense he has regarding me is the 2000 euro he sends me on which of course he doesn't need to pay taxes as I'm doing that in my country.
Apart from that just in case I spend my free time in keeping myself updated with other tech which I would say I fairly experienced with like: Flutter/Dart, ES6, NodeJS, Express, GraphQL, MongoDB, WebSockets, ReactJS, React Native just to name few, some I know better than the other and still I feel like I don't get what I deserve.
What do you think, do I ask a lot or should I start searching for other job?23 -
So, the GUI is built by writing YANG files that are then transformed into protobufs and jsons. Protobufs are then digested by GWT to compile java into javascript and HTML. What part of the process you don't understand?
Wait, I actually don't exactly know where the jsons end up being used, but apparently they are being sent by C++ backend to GWT frontend. Somehow.12 -
recruiter used some blog post, a baseline for frontend developers (pretty neat post btw), to asses my skills. she read the subheadings of the post and asked me to rank myself 1-5. i find this way of assesments as idiotic as having percentage representation of skills on idiotic portfolio sites. i mean wtf does it mean that you know 80% of html??? but that s another rant. so she goes:
rec: javascript?
me: 5
rec: git?
me: 5
*continues with other subs*
rec: the fine manual?
me: excuse me?
rec: how would you rate yourself in the fine manual?
me: *blank stare*
"the fine manual" was the subheading of the conclusion paragraph of the fucking blog post....3 -
Inspired by @shahriyer 's rant about floating point math:
I had a bug related to this in JavaScript recently. I have an infinite scrolling table that I load data into once the user has scrolled to the bottom. For this I use scrollHeight, scrollTop, and clientHeight. I subtract scrollTop from scrollHeight and check to see if the result is equal to clientHeight. If it is, the user has hit the bottom of the scrolling area and I can load new data. Simple, right?
Well, one day about a week and a half ago, it stopped working for one of our product managers. He'd scroll and nothing would happen. It was so strange. I noticed everything looked a bit small on his screen in Chrome, so I had him hit Ctrl+0 to reset his zoom level and try again.
It. Fucking. Worked.
So we log what I dubbed The Dumbest Bug Ever™ and put it in the next sprint.
Middle of this week, I started looking into the code that handled the scrolling check. I logged to the console every variable associated with it every time a scroll event was fired. Then I zoomed out and did it.
Turns out, when you zoom, you're no longer 100% guaranteed to be working with integers. scrollTop was now a float, but clientHeight was still an integer, so the comparison was always false and no loading of new data ever occurred. I tried round, floor, and ceil on the result of scrollHeight - scrollTop, but it was still inconsistent.
The solution I used was to round the difference of scrollHeight - scrollTop _and_ clientHeight to the lowest 10 before comparing them, to ensure an accurate comparison.
Inspired by this rant: https://devrant.com/rants/1356488/...2 -
*Debugs a thread synchronization issue in a C program*
*Gives up after few attempts to debug a bootstrap table that’s not showing a column* -
Decided to dive a bit into frontend and discovered vue-js.
Why didn't I know you, back when I contributed to my highschools website?!2 -
I applied for software engineer in a software development firm. It clearly states in my resume that I am mainly a PHP developer in my current job. The company I applied for focuses on javascript frontend frameworks with Java Spring or node.js as backend.
The screening consisted of three parts; written exams, panel interview and the final interview. It lasted for a whole day, and when It's time for the final interview, the interviewer said that there are no slots left for trainee/junior level which is my level with 5 yrs experience in the industry.
I understand that this means that I will be trained with the technology that they are using so it will be an entry-level job but I submitted my resume several days ago and they didn't reviewed it first before making me attend the screening. I just wasted my time with this! They could've said from the start that they are not looking for people that do not have any experience with this technology/framework.
Fuck6 -
Fuck the JavaScript ecosystem; Fuck React, Redux, and a big special fuck you to React-Router. And fuck interviews that give week long assignments.
The whole fucking JavaScript community makes the simplest things so complicated just so that they can tell Backend and Mobile Devs “Hey our job is difficult too”; fuck you, it isn’t! You made it difficult. and so that they can write corny emoji-laden medium articles about it to supplement their meagre income. What’s more the articles are outdated in less than a week.
Fuck JavaScript; APIs changes everyday a week and it’s documentation is updated every decade.4 -
PouchDB.
It promised full-blown CRDT functionality. So I decided to adopt it.
Disappointment number one: you have to use CouchDB, so your data model is under strict regulations now. Okay.
Disappointment number two: absolutely messed up hack required to restrict users from accessing other users’ data, otherwise you have to store all the user data in single collection. Not the most performant solution.
Disappointment number three: pagination is utter mess. Server-side timestamps are utter mess. ANY server-side logic is utter mess.
Just to set it to work, you need PouchDB itself, websocket adapter (otherwise only three simultaneous syncs), auth adapter (doesn’t work via sockets), which came out fucking large pile of bullshit at the frontend.
Disappointment number four, the final one: auth somehow works but it doesn’t set cookie. I don’t know how to get access.
GitHub user named Wohali, number one CouchDB specialist over there, doesn’t know that either.
It also doesn’t work at Incognito mode, doesn’t work at Firefox at all.
So, if you want to use PouchDB, bear that in mind:
1. CouchDB only
2. No server-side logic
3. Authorization is a mess
4. Error logs are mess too: “ERROR 83929629 broken pipe” means “out of disk space” in Erlang, the CouchDB language.
5. No hosting solutions. No backup solutions, no infrastructure around that at all. You are tied to bare metal VPS and Ansible.
6. Huge pile of bullshit at frontend. Doesn’t work at Incognito mode, doesn’t work at Firefox.8 -
I was talking to a friend about the current state of machine learning through tensorflow and commented about the use of Javascript as a language.
He discarded the idea as he views Javascript as something that should only be used as a frontend technology rather than something to build backends or deep learning models.
I am thorn. I have always liked Javascript but will admit that I have used it mostly in the area of front end with very few backend instances(i did create a full stack intranet app in Express once, major success for the application it was hosting, it was a very basic api which had its own nosql db with no need to interact with the company's relational data, it was perfect for the occasion and still help maintaining it from time to time)
My boi states that node's biggest issue has always been npm and the quality of packages. I always contradict those statements by saying that if one uses community standards and the best packages then one does not need to worry about the quality(i.e mongoose over some unmaintained mongo wrapper etc)
I sometimes catch myself finding that my way of thinking adapts better to JS than it even does Python (which is his preference for deep learning) and whilst there are some beastly packages for python in terms of quality and usefulness such as matplotlib etc that one can do great things with the equivalent JS.
I mean, tensorflow.js came from the same wizards that did tensorflow (obviously) and i find the functional approach of JS to be more on par with how we develop solutions.
I am no deep learning expert, and sadly I have no professional experience with machine learning. But I venture to say that we should not cast aside the great strides that the JS community has done to the language in terms of evolution and tooling. Today's Js is not your grandaddy's Js and thinking that the language is crippled because of early iterations of the language would be severely biased.
What do you guys(maybe someone with professional experience) think of Js as a language for machine learning?
Do you think the language poses something worth considering in terms of tooling and power for ml?2 -
As a junior dev from a sysadmin and security background, this is a list of software development concepts I never seemed to truly understand but hope to(rated from most intimidating to least):
1) Frontend web development and all the huge world of javascript frameworks and tools. - It's more overwhelming than the political geography of the Holy Roman Empire in the Middle Ages.
2) Machine Learning, Deep Learning and A.I- too much math that fucks with my brain.
3) low-level programming(kernel,drivers) - sounds extremely interesting but the code in assembly/C/C++ looks like Linear A Minoan hieroglyphics.
4) Rx(insert language here) - I never get why it is useful or why someone invented this. Seems interesting though.
5) Code Reflection - sounds like Thelemic magick.
6) Packaging, automation, build tools, devops, CI, Testing -seems too complicated. I just want to run an executable at the client or make a web app that does something. Why all this process?6 -
New toy for frontend devs:
OpenType 1.8 Variable Fonts.
1 font file to rule them all. Manipulate on the fly fluidly the font weight via css and javascript.
http://blog.typekit.com/2016/09/...
1 -
Recruiter wrote me to see if i was interested in a java frontend dev role - my answer:
Just as a fyi - java and javascript is like car and carpet - not the same thing :)2 -
Most of the rants I see here are related to CSS or JavaScript, so I am very grateful I did not end up in the frontend, which I would have given up long ago.7
-
some guy asked me to look at his react project,
I'm yet to find out the problem with his routing but look at this dependency list.
for a simple frontend project, I really dont know how many lazy developers are being introduced into the javascript ecosystem,
might seem normal to others but it feels wrong to me, as a beginner developer who isnt even dealing with a deadline
or......... maybe they are just plain clueless that they dont realize this level of redundancy
9 -
Have a question about my career:
So far my career out of uni has been like this:
8 months in first place working as C# .NET dev, creating native desktop apps for windows. job was shitty, was not getting any best practices skills so I left.
12 months in 2nd place working as android dev in a startup. was working all alone and had to rebuilt my app up to 5-6 times to learn best practices. startup didnt care about android app at all so I left and now doing just some small freelance work for them.
3 months in new startup as android dev.Today I was told that its decided to focus on iOS and do all marketing (also uplift of new design) only on iOS. basically for next 3-4 months they don't plan to do much on android side. they saw that I showed some interest in backend and now they are asking me to talk with two other senior guys about starting with some small tasks for me on backend.
Our backend is mainly using python. Also backend guys will be pretty busy for next few months because they will have to deliver many new features in next few upcoming months. I've talked with one of them and he said that this is a bad idea to force frontend to start working on backend. However I feel that he's sort of gateekeping and probably just doesn't want to help me with getting up to speed.
In my defense, my knowledge doesn't end with C# .NET desktop apps and native mobile apps for android.
I have hobbie projects (gameservers) where I worked on websites (php,html,css,javascript,mysql) and also was taking care of a java based gameserver which is hosted in a linux vps.
Also I've had a small hosting "company" where with available tools I've managed to automate VPS(virtual private server) ordering, web hosting ordering and domain ordering. Basically I owned a dedicated server and did everything using whmcs, cpanel and proxmox virtualization.
I trust myself in learning this backend stuff and doing whats required, however I learned everything by myself and I won't follow all of these best practices.
Should I accept more responsibility on backend or should I continue focusing on android?7 -
Question for those that switched from Web, Mobile Apps development, Full-stack development to Game development after a year or more:
- Do you regret the change?
- What Game engine do you use?
- What Programming language do you use?4 -
!rant. Story from my college abt 6 months old.
We had to make projects for our course.
One team made a very nice project. One part of that was mobile no. verification using OTP.
And the student who was supposed to to that, did it by sending the required otp to the frontend page, and when user enters it, validate it using javascript.
The prof got mad about it and the rest of the class couldn't stop laughing.
Just remembered. Thought it would be worth sharing. -
Repeat after me:
process.env is not standardized. Keep it out of the browser.
process.env is not standardized. Keep it out of the browser.
process.env is not standardized. Keep it out of the browser.
process.env is not standardized. Keep it out of the browser.
Fucking hate the web community. It's just a large trash barge at this point.19 -
I decided i wanna, so i learned C, then i realized OOP was a thing so i had some fun with Java and Android, then i realized Web was useful, and easier to make actual products so i had an affair with RoR, but it was confusing AF, then i got a job where i have to work mainly with Python and Django, but frontend was PITA and i hated it.
In the end, since im only dev at the company and had to do it i started to like it (stockholm syndrom much) and now Im Javascript dev trying to move our stack to Node...
No regrets! -
So when are all of you going to admit that React.js is useless? It's awful and miserable and doesn't do anything it promises to.
It's not faster to write code, it's not cleaner, it's not easier, it's just a ton of boilerplate and it can't even handle simple animations.
If Facebook didn't create it, everyone would think it's ridiculous and stupid.. Because it is.
Stop trying to be cool and just fucking deliver fucking business value.56 -
I have plenty of those but one that shines out from the croud is one frontend guy.
He had to modify some javascript slider but couldn't figure out how.
So he comes to me and tells me he found the code where the slider is initialized but changes are not applied.
I walk up to his desk and he shows me some CSS code with #slider selector in it.6 -
ChatGPT, Copilot, React, how to make a link in a frontend website?
To create a link in a frontend website, create a span, a div, or a paragraph that contains the link text. In your JavaScript web app, add an event listener to that element that opens the link on click. If you want to claim you're accessible, add an aria-role to the clickable element. To make debugging harder and only possible for the real arcane experts, let your framework generate generic ids and class name hashes for styling and event handling, like "item_09fcfck" or "elementor_element_foo_bar". Avoid, at all price, to use an a href element!2 -
I should wait a bit longer before sharing this but looks like I am going to get a fulltime contracting position in a company that develops Netflix-like on-premises solutions for global brands, TV channels and telcos. I would with the team write hybrid app targeting phones, tablets, IP Tvs & consoles. I am waiting for them to call my two references and then voilà. Byebye e-commerce and WordPress, Welcome JS, React and Haxe. So excited this morning.3
-
Hello, everybody! Recently, I've decided to switch from Android development to web-development, mainly JavaScript. Ok, it is clear what to do and what to learn in frontend part. But what about backend? I have a some kind of a dream to learn Go. It is clear language it is a great pleasure to write on it, and I've started to learn it. In parallel I'm trying to study JS + Angular... Well, now I have some douts: is it effective to learn two different languages, which are quite new to me? Maybe, I should learn Node.js instead of Go? Right now it is clear, that this technology (node) is much more demanded. What path should I choose? To follow heart and learn Go? To follow mainstream trend and learn Node.js?1
-
manually writing multiselector widget with jquery and javascript, because you need to be able hackily pass in metadata for some stupid fucking edge case that the previous generation didn't want to deal with
please euthanize me, i fucking hate frontend and im sure it hates me back3 -
Ok, so I need some clarity from you good folk, please.
My lead developer is also my main mentor, as I am still very much a junior. He carved out most of his career in PHP, but due to his curious/hands-on personality, he has become proficient with Golang, Docker, Javascript, HTML/CSS.
We have had a number of chats about what I am best focusing on, both personally and related to work, and he makes quite a compelling case for the "learn as many things as possible; this is what makes you truly valuable" school of thought. Trouble is, this is in direct contrast to what I was taught by my previously esteemed mentor, Gordon Zhu from watchandcode.com. "Watch and Code is about the core skills that all great developers possess. These skills are incredibly important but sound boring and forgettable. They’re things like reading code, consistency and style, debugging, refactoring, and test-driven development. If I could distill Watch and Code to one skill, it would be the ability to take any codebase and rip it apart. And the most important component of that ability is being able to read code."
As you can see, Gordon always emphasised language neutrality, mastering the fundamentals, and going deep rather than wide. He has a ruthlessly high barrier of entry for learning new skills, which is basically "learn something when you have no other option but to learn it".
His approach served me well for my deep dive into Javascript, my first language. It is still the one I know the best and enjoy using the most, despite having written programs in PHP, Ruby, Golang and C# since then. I have picked up quite a lot about different build pipelines, development environments and general web development as a result of exposure to these other things, so it isn't a waste of time.
But I am starting to go a bit mad. I focus almost exclusively on quite data intensive UI development with Vue.js in my day job, although there is an expectation I will help with porting an app to .NET Core 3 in a few months. .NET is rather huge from what I have seen so far, and I am seriously craving a sense of focus. My intuition says I am happiest on the front end, and that focusing on becoming a skilled Javascript engineer is where I will get the biggest returns in mastery, pay and also LIFE BALANCE/WELLBEING...
Any thoughts, people? I would be interested to hear peoples experiences regarding depth vs breadth when it comes to the real world.8 -
Started to rewrite a part of the frontend of a web app I'm building and holy shit, I've never though JavaScript can be so much fun 😁😁3
-
Need some advice again. I'm a junior backend developer or that's at least what I try to call myself.
For the first year at this company I did a lot of backend which I love and really enjoy, eventually they let me do devops and migrations. Okay, but not really what I wanted.
Two months ago, I started my internship at the same company. Now they wanted me to do Shopify, I hate to do frontend, only thing I enjoy is the JavaScript. Fucking sucks but okay, eventually it will be done.
And fucking today I heard they wanted me on support mostly, isolated from the rest into another room with the (dumb) zero experience trainee.
I honestly don't know what to say? Should I refuse? I do have some power because they accepted 3 other projects which require my expertise with migrations. Like why don't they use me were I'm good at, backend?2 -
In reply to:
https://devrant.com/rants/3957914/...
Okay, we must first establish common ground here. What do we understand about "showing"? I understand you probably mean displaying/rendering, more abstractly: "obtaining". Good, now we move on.
What's the point of a front-end? Well, in the 90's that used to be an easy answer: to share information (not even in a user-friendly way, per se). Web 2.0 comes, interaction with the website. Uh-oh, suddenly we have to start minding the user. Web 3.0 comes, ouch, now the front-end is a mini-backend. Even tougher, more leaks etc. The ARPAnet was a solution, a front-end that they had built in order to facilitate research document-sharing between universities. Later, it became the inter(national) net(work).
First there was SGML to structure the data (it's a way of making it 'pretty' in a lexicographical way) and turn it into information (which is what information is: data with added semantics) and later there was HTML to structure it even further, yet we all know that its function was not prettification, but rather structure. Later came CSS, to make it pretty. With its growing popularity, the web started to be used as a publishing device.
source:
https://w3.org/Style/CSS20/...
If we are to solely display JSON data in a pretty way, we may be limiting ourselves to the scenario of rendering pretty web pages using aesthetic languages such as CSS. We must also understand that if we are only focusing on making a website pretty with little to moderate functionality, we aren't really winning. A good website has to be a winner in all aspects, which is why frameworks came into existence, but.. lmao, let's leave that to another discussion.
Now let me recall back my college days.. front-end.. front-end.. heck, even a headset can be a front-end to a pick-order backend. We must think back to the essence, to the abstract. All other things are just implementations of it (yes, the horrendous thousands of Javascript libraries, lol).
So, my college notes say:
"Presentation layer: this is the UI.
In this layer you ask the middle tier for information, which gets that information from a database, which then goes back to middle tier, back to presentation. In the case of the headset, the operators can confirm an order is ready. This is essentially the presentation tier again: you're getting information from the middle tier and 'presenting it' as it were.
The presentation layer is in essence the question: how do I bring my application data to my end users in a platform-and solution-independent way?"
What's JSON? A way to transport data between the middle tier and the presentation tier. Is that what frontend development is? Displaying it in a pretty way? I don't think it is, because 'pretty' is an extra feature of obtaining and displaying data. Do we always have to display data in a pretty way? Not necessarily. We could write a front-end script (in NodeJS perhaps) that periodically fetches certain information from a middle-tier is serves a more functional role rather than a rendering one.
The prettification of data was a historical consequence of the popularity of the web (which is a front-end) (see second paragraph with link). Since the essence of a front-end is to obtain information from the back-end (with stress on obtaining), its presentation is not necessarily a defining characteristic of it, but rather an optional and solution-dependent aspect, a facet.4 -
Is it just me or is it just really hard to set up and test frontend JavaScript? 🤔
Karma + Mocha + Chai + whatever
is a pain
And it doesn't look very pretty..3 -
How to fail my interview 101:
1. Change your GitHub status to "I love learning new things every day"
2. Start by showing off your code katas
3. "React is the best way to do frontend"
4. "Unit tests are necessary"
5. "TypeScript is better than JavaScript"
6. "I don't have to learn CSS, I use Tailwind"19 -
Question to the frontend devs: I'm currently trying to optimize part of our JS. How do sourcemaps influence loading/rendering Speed in the Browser?
In the `webpack.config.js` we use uglify as minimizer for js. It has the option `sourceMap` Set to `true`. Now as I understand it, this caused it to Inline a sourcemap inside the JS file (which leads to a slightly bigger file size and thus longer load time for the generated file...).
My Question: should sorcemaps be enabled for prod (minified) files? Why yes, why no? Do they help the browser parse the JS faster?12 -
Question to all JS Frontend Devs: What light and performant library can you recommend me today?
I'm a C++ dev who is a bit anxious about performance, load times etc. and before I stuck my nose into vanilla js, maybe there is something better/faster. I'm a total frontend noob, e.g. I heard that html tables aren't a thing anymore and that I should use divs?
My task is quite simple, I want to give the users the ability to press some buttons and drag and drop stuff around instead of modifying the URL per hand :/
So if someone could point me in the right direction, that would be awesome!16 -
So i was considering to start learning laravel but after all the hate php gets, i'd like to ask for your opinions guys.
I recently started working on django for a college project and that made want to learn new stuff, so i'm hesitating between JS (plain Javascript, jquery, node, angular...), laravel, ruby on rails or anything that could help me both on frontend or backend.
Any opinion is welcome and most appreciated11 -
I am tired of a glorified code monkeys cosplaying software engineers.
Disclaimer: in general, I have immense respect to engineers and technological advances that came from FAANG/MANGA. Bbbuuuuttttt...
Especially people that has a few relatively short (less than a year) stints in a few of them and thinking that their salary expectation for their skills is reasonable.
What I've saw so far, based on a few hires for past few years in a company of ~50 engineers, Python/JavaScript stack, monolith to microservice transition (all people had senior and above titles):
* Have no idea how to setup own development environment on MacBook.
* Have no idea how to run code and tests for Python (from discussion, the two only development experience was "code - commit - push - done" and "clicking button in remote coding environment".
* Have no idea how to use bash/zsh (the person had "Linux skill up to 11").
* Grinding leetcode and interviewing during work hours (were let go immediately).
* Introducing a new microservice for each task (we're transitioning from Django monolith, but not to that extent).
* Ignoring all the onboarding, documentation and ignoring every request for writing documentation "I am not a technical writer".
* Knowing nothing about Kubernetes (this was in the job posting/requirements).
* Person actively hostile to any frontend task (the position is not full stack, but JavaScript is a required skill).
I am pretty open and I understand the eternal "generalist vs specialist" thing, but if the person do not posses certain skills and actively lie about it, just because "I worked at FAANG companies, obviously I have that skills" - it's dishonesty at best and fraud at worst. And if with the end of ZIRP you suddenly became unhireable in FAANG/MANGA - you need to think why.
There are tons of small software companies that nevertheless have a good salary and benefits, and most of the time hiring was a breath, because for the most of the people they were flying under the radar.
Unfortunately, since this year the hiring is exhausting, the amount of incapable candidates is incredible (a lot of them with credentials), and instead of 10-15 candidates per position (before and during pandemic), now there are more than 300 candidates per position with "impressive" working experience and only 10 people who really spend time on interviewing.
In short, if you think you're worth gold only from 3-4 companies in the world and all of them stopped hiring you - you should rethink your worth.3 -
Muahahaha!
Stupid canvas! I killed you!
No more anti-aliasing for you! Now it's time for pixel perfect drawings and a finally functioning floodfill algorithm!
I only had to make my own full custom drawing routine. It is not that I had other things to do, right?!
Seriously: Who the heck decided to implement anti-aliasing for a canvas that cannot be deactivated? Who!?
Oh, I hate frontend so much. That's not my world... -
Fuck you javascript. You're the worst. Fuck you fuck you. Why I became a fucking frontend developer. Fuck me and my stupid idea to get hired as a...
Oh nvm found the bug. JS is za best.1 -
Old colleague reached out to me. He needed to reinstall one of my web apps (combination of python, php and Javascript (frontend)).
It was harder to do than expected and the code was not the most clever I ever saw.
Not sure what I was thinking during that time of my life 🤔 -
Situation a few months ago: Talking to beginners in a WhatsApp group and helping them with their problems and questions. Thought it would be nice and easy.
After a few weeks, we are "talking" about programming languages used to build a simple website (we were main talking about frontend) so I did my thing, helped them etc.
--- btw. you need to know that the link to the group was available on on a learning platform("sololearn")---
Later in a personal chat with someone:
He:Can you teach me a bit
Me: what do u want to know
He: hmm like what is the exact difference between backend and frontend
Me(in short): [...]languages you mostly use for the frontend thing are for example JavaScript[...]
He:what is JavaScript
*Contact blocked*
Dude. Still have got a painful headache.
Oh btw here are some learning-platforms:
udemy.com
udacity.com
SoloLearn.com
Treehouse.com
Post some in the comments!3 -
Im new to devRant and i’m just looking if i could get any tips, example projects i could do to fill my portfolio? Im trying to sharpen my skills in web dev (both back & front + React)4
-
Webpack? More like Fudgepack 😡
OK sure, I know it's cool to rip on Webpack without taking 5 minutes to understand it, but I really have tried. Every time I want to do anything which used to be trivial with grunt, gulp or brunch, it requires a whole bunch of sorcery and every post I see online around the same topic inevitably ends with something like "that's not modular", "WebPack doesn't work like that", "you're holding your phone wrong" etc. And it's not like I'm someone who is afraid of new or uncomfortable things. I try new languages almost as often as there are new JavaScript fads (OK maybe not THAT often). I use "weird" keywords and experiment with different key maps all the time. I swap my daily window manager on an almost quarterly basis (and xmonad is no picnic as an introduction to Haskell). But what the fuck is it with so many people in positions of influence in the frontend world always taking one step forward, two steps back and an occasional hop sideways when it comes to tooling (and dragging everyone else along with them)?
How did such a turd of a tool become defacto for so many frontend frameworks? Do hard core JavaScripters just really really hate outsiders and want to deter others from their precious as much as possible? Fuck Webpack and fuck everyone responsible for helping it permeate so thoroughly through the software development industry.2 -
1. Reading eBook “Beginners in vb6”
2. Made a calculator with vb6 to help me in Math homework
3. Made few other desktop apps on vb6 for fun
4. Got interested in Websites so started with WYSIWYG Microsoft FrontPage
5. Started learning frontend and backend coding from WYSIWYG Dreamweaver (HTML, CSS, jQuery, MySQL and PHP)
6. Then custom coding on Sublime. Made around 6 side projects (HTML, CSS, jQuery, MySQL and PHP)
7. Started learning core JavaScript and followed by other programming languages
8. Interest came in making Android and iOS apps. I learnt Java and Swift for it
9. Now I span between Web and Mobile Apps -
The frontend developers in my company are the reason why I have anxiety. Here are few things that grinds my knees:
1) for a long time in projects, they deleted the auth token from their storage without integrating the logout api. They thought why use an API for that. :)
2) most of them had no clue that form fields could accept javascript as inputs and work as XSS vulnerabilities. This actually happened with a client, he got so fucking pissed.
3) One of them asked me to convert a PATCH request to DELETE cos fuck REST and HTTP methods.
For fuck’s sake. I need to get out of this place.4 -
I have a question, but first some background. When I got my first job, it wasn't clear cut what I would do, but I ended up doing frontend. I really liked doing frontend, so I continued doing so and I still do to this day. I even work alongside designers in a design studio, so I feel very much like a frontend developer.
Obviously, the term "frontend" these days implies someone, in some ways, writing a web, mobile or desktop app using javascript. For me, frontend is also about stuff like accessibility, design, code delivery, and understanding the end-users and the designers that may have prototyped something for you.
I have not been active in any other dev communities than this place, but it seems to me like a frontend developer is pretty much the lowest common denominator ( I guess in terms of skills). If I am right, I do not know why, which is why I'm hoping someone could explain.9 -
Everybody's talking about the 50/50 for some reason, so here's my 2 cents. I've been trying to hire another senior front-end engineer for my team for over two months, and not one half-competent candidate passed our tests yet*. The first one to pass, and I don't care whether it's a male candidate, a female one, or a type of asexual sentient mushroom spore, will get the job.
We do prefer a female candidate because our team is all male at the moment. But that's not going to stop us from hiring a male one if we find anyone.
Also, out of 40ish candidates I've interviewed so far, I believe only 3 were female. Might be a fourth one I can't recall at the moment.5 -
Fuck all those special snowflake npm packages who each implement their own incomprehensible documents format and even make an ugly ass website full of lies for it.
Next to JavaScript, this is the biggest reason why I hate frontend development with a passion.2 -
I got contacted by an other company and I am so unsure whether to accept their offer or stay at my current job.
For now I spend 2 years at my current company. The culture is great and everyone gets treated very well.
The bad part is, that it is located in a part of Germany I really can't stand and to this day fully remote is not an option.
Additionally lots of stuff is really frustrating in my daily work, e.g. colleagues that experiment with critical parts if our infrastructure, resulting in every developer who made the mistake to update the local development stack being unable to work for half a day or so.
This and the fact, that our techstack sucks hard. (mostly bad php for backend and server-rendered HTML and a weird mix of Typescript, Javascript, Vue and some old bits of deprecated angular for frontend). This company has it's own product (a web platform) and no real deadlines in the sense of "something bad happens, when your team won't achieve the project in the originally proposed time"
Company number two seems to work with a wide variety of technologies for very different projects (it's a consulting compan), would pay me ~28% more than my currently raised pay and allows for full remote.
When I try to look objectively on the facts everything points to accepting their offer, but on the other hand there is this weird feeling of this being a joice that would come to soon...
How do you make such decisions? I already talked to a great colleague of mine, who thinks it might not be a bad idea to stay at the company for an additional year or 2, because I haven't yet reached the point where there is not enough to learn here anymore, which I agree on, but this company seems to offer everything I want.
I feel overwhelmed with this situation :D that's why I would like to know how you people try to tackle such a situation8 -
I took the effort to apply for a frontend/angular position. I don’t have much experience in Angular (although its just javascript) but i’d like to learn further... i got a mail back that i didn’t send them a motivation. No true i applied at 50+ companies in the last months and writing a custom motivation is just too much of a hassle.
I sended them the standard; i have this and this experience and looking for such and such.
I got a call. Yay, almost a week after the application but i cannot complain can i?
During the call the person of this company was very hesitant. He wasnt looking for someone right now. Wanted to take his time and wanted more of a medior developer. (Tnx buddy for underestimating me already)
Yeah if i can send over some code before we talk further. Sure i’ll send over my GitHub but if you are this hesitant already i know enough and i don’t want to work at your company because you clearly don’t want to hire me. -
Finding it hard to focus. I'm into UI, backend, frontend, iOS... Exploring FP. We've just had our first child and I need to put my time and energy into what will a) provide healthy financial remuneration b) be more enjoyable than frustrating c) be relatively futureproof (if that's even possible). For some reason I have a huge distaste for JavaScript (as an ecosystem) which has led me to look into Elm. I've enjoyed Ruby but something in my mind tells me Functional programming is more logical for me. It's a whole new approach and skill to level-up on. I love programming my own back-ends, but for me, design is so important and I want to be part of the visual, tangible part that people interact with. I'm a one-man operation which means I do design, full stack Development, client liaison, financials, client acquisition. Freelancing is a double edged sword - I don't know when the next project will come, but I also need to focus on the projects I have without taking too much on. At times I think employment would be good, despite having it's on drawbacks which I read about repeatedly on here. Any advice?1
-
If VS code plugins were Pokemon cards, which ones would you choose and what level would they be? ... Ready .... Set ... Go2
-
The adventurous world of javascript and typescript never ceases to amaze me.
I'm investigating some paths to take for migrating this legacy project which has incurred some technical debt. Because of... reasons... even the frontend Vue project needs to be built on a Windows system. No, you can take your hands down, even wsl or docker aren't alternatives here. It's a long story and ties in with said debt.
I'm keen on rebooting the entire frontend using a newer Vue cli and scaffold up all the essentials like eslint and typescript which is currently not used. This is gonna be sweet.
Except, typescript (BY Microsoft) doesn't play well on a Windows (BY Microsoft) filesystem because of a recent change to support - get this - wsl. I can't decide if it's hilariously ironic or genius.
This response about sums up my current mood. https://github.com/Microsoft/...
Of course, further digging in other repos like node only turns up issues closed due to it being on Windows' end.
So now my readme has a troubleshooting section describing how to make changes to your filesystem if you run into issues in Windows and I want to go home.6 -
Frontend developer mainly, getting all excited by C#, net core, apis, http, databases. A new world of trinkets and hard-edged engineering. Makes me eyes glitter.
But my day job needs me to become as proficient as possible on the frontend of the stack. As we warm up to a huge application rewrite, with me as the sole frontender, it becomes clearer and clearer that, if I am not only to survive, but leave a codebase behind me that is clean, thoughtful, well modularised and built with maintenance and performance in mind, that I must let go. I have to focus.
I feel a little sad today. Somehow, right now, the frontend world does not feel as exciting. Javascript feels loose, unpredictable...my work open as well to everyone with every flavour of opinion. Because it is observable.
But I am mortal. Time is precious, and limited. I feel I need a dose of curiosity discipline and that, if I can do so, I can devote myself not to my coming and going whims of interest, but the real hard work of learning craftsmanship once that feeling of glitter has faded.
My brothers and sisters, steady my hand. -
In my company we are constricted to have 100% of f̶a̶k̶e̶ coverage with unit test.
Obviously the test suites are not performing and it takes more than 8 minutes to run 3335 tests.
I know that what I'm going to say is super mainstream but there is nothing comparable to the relief that comes from seeing all tests in green after you did a lot of small changes around the code on Friday.4 -
Every time I have to touch a webpack config I remember Geocities much more fondly. Hell, even Frontpage wasn't so bad really.
-
Even though I'm learning Node.js, I'm still a little confused about the distinction between Node and frontend JavaScript.
Where does frontend JavaScript end, and Node begin? What are the practical distinctions between the two?5 -
Do you guys think that the frontend or a javascript developer is an easy job? is less than a backend developer?
let's discuss5 -
Frontend shananigans continue:
Spent all morning un-ejecting my CRA react app and migrating sass to less... Seriously how is this productive?? -
Has anyone experience with Frontend Testing and can suggest something good?
Note: JavaScript / Node JS3 -
!rant => question?
I'm hired as a freelancer for a start-up that wants to create a social-network-like platform. I've always been a "basic" PHP and javascript developer like using AngularJS, MySQL and my own kinda like PHP MVC framework etc.. But I'm worried that 'this' will come short when the platform expands on the user-base and stuff. That MySQL won't be able to keep up with the expectations and the amountof data, that AngularJS will not be enough for the Frontend,.. I've taken a look at ReactJS, RethinkDB, NodeJS and such, but this is not really within my "comfort zone" and I'm not willing to invest time in something new if it's not able to handle the platform (I don't know if it will..) and I'm afraid that I'll have to start from scratch if it all fails.. (and this is something I can't afford)
So.. What are you guys's opinions? We're not looking at millions of users, but it will have feeds, comments, connections, messages, post scopes,.. Etc. RethinkDB looks promising with the 'watchers' to get live data instantly, but it's a whole new way of query'ing and such.. It just feels like I'm wasting my time because I'm afraid that I'll reach a point in development where I'll have a situation for example like "damn.. This is impossible with angular or php.." [I've shouldn't have agreed to this project..] :D1 -
So I'm in my last year of university. The GPA is high. Did one internship the summer after second year in one of the best companies in my country. Third year in my department we do a semester long internship for 5 months, I joined a company and worked on back-end using Go. This was the spring semester and I wanted to continue working in the summer. The internsip company didn't tell me anything so I looked for a job. Found one that paid great, I was getting the salary a new graduate was getting. I worked as a full-stack there. Mostly prototyping, the company was new and I was in the R&D side. After 2 months the company had some budgetary problems and we parted ways. I was in the market again for part-time job in my senior year and because of my prior experience with Go, a friend mentioned me to a company executive he met and I had an interview and got in as a full-stack part-time dev. This was for some background information.
My story is;
The work is actually great in terms of what I do. I'm learning a lot here. The problem is that I'm having imposter syndrome for the first time ever. The projects are demanding and because that I'm part-time they take time to finish. There are no due dates or anything but sometimes the CEO is coming to me and saying "Aren't you finished with it?" or "Are you going to finish it soon?". Because that I'm more qualified in Javascript and React when they gave me my current frontend project I told them that its better if they give javascript/frontend projects from now on so that I can do a better job finishing them. What the CEO told me after that was, "Then hopefully you'll finish them sooner.". The people are nice and stuff like this only happened 2-3 times and the lead that I'm working with acknowledges my pros and cons and we have a good relationship, when I do something wrong he tells me why and how I can improve my code. But I just can't get over the syndrome and for some time I actually thought they would fire me when they get a full time dev.
Everything is great for some time. It's my fourth month and I think I felt this way because this is the most demanding job I have with senior year and also I didn't know people that well because I was the new guy. Although I still have concerns, have you ever felt this way? If you share tips or any recommendations I would feel great.
Thank you for reading.2 -
Practicing some random code interview questions while not busy.
Find top N values with MaxHeap in JS
Didn’t get it right in 1st try. Something wrong with the replace function. Then started getting busy...
At the end of the day, still didnt have a chance to fix it.
God damn it! It’s me. A frontend developer can’t write MaxHeap in JavaScript 🤦♂️ -
I need some advice to avoid stressing myself out. I'm in a situation where I feel stuck between a rock and a hard place at work, and it feels like there's no one to turn to. This is a long one, because context is needed.
I've been working on a fairly big CMS based website for a few years that's turned into multiple solutions that I'm more or less responsible for. During that time I've been optimizing the code base with proper design patterns, setting up continuous delivery, updating packaging etc. because I care that the next developer can quickly grasp what's going on, should they take over the project in the future. During that time I've been accused of over-engineering, which to an extent is true. It's something I've gotten a lot better at over the years, but I'm only human and error prone, so sometimes that's just how it is.
Anyways, after a few years of working on the project I get a new colleague that's going to help me on my CMS projects. It doesn't take long for me to realize that their code style is a mess. Inconsistent line breaks and naming conventions, really god awful anti-pattern code. There's no attempt to mimic the code style I've been using throughout the project, it's just complete chaos. The code "works", although it's not something I'd call production code. But they're new and learning, so I just sort of deal with it and remain patient, pointing out where they could optimize their code, teaching them basic object oriented design patterns like... just using freaking objects once in a while.
Fast forward a few years until now. They've learned nothing. Every time I read their code it's the same mess it's always been.
Concrete example: a part of the project uses Vue to render some common components in the frontend. Looking through the code, there is currently *no* attempt to include any air between functions, or any part of the code for that matter. Everything gets transpiled and minified so there's absolutely NO REASON to "compress" the code like this. Furthermore, they have often directly manipulated the DOM from the JavaScript code rather than rendering the component based on the model state. Completely rendering the use of Vue pointless.
And this is just the frontend part of the code. The backend is often orders of magnitude worse. They will - COMPLETELY RANDOMLY - sometimes leave in 5-10 lines of whitespace for no discernable reason. It frustrates me to no end. I keep asking them to verify their staged changes before every commit, but nothing changes. They also blatantly copy/paste bits of my code to other components without thinking about what they do. So I'll have this random bit of backend code that injects 3-5 dependencies there's simply no reason for and aren't being used. When I ask why they put them there I simply get a “I don't know, I just did it like you did it”.
I simply cannot trust this person to write production code, and the more I let them take over things, the more the technical debt we accumulate. I have talked to my boss about this, and things have improved, but nowhere near where I need it to be.
On the other side of this are my project manager and my boss. They, of course, both want me to implement solutions with low estimates, and as fast and simply as possible. Which would be fine if I wasn't the only person fighting against this technical debt on my team. Add in the fact that specs are oftentimes VERY implicit, so I'm stuck guessing what we actually need and having to constantly ask if this or that feature should exist.
And then, out of nowhere, I get assigned a another project after some colleague quits, during a time I’m already overbooked. The project is very complex and I'm expected to give estimates on tasks that would take me several hours just to research.
I'm super stressed and have no one I can turn to for help, hence this post. I haven't put the people in this post in the best light, but they're honestly good people that I genuinely like. I just want to write good code, but it's like I have to fight for my right to do it.1 -
As a frontend developer, I started learn unreal engine 4 in my spare time instead of build next js framework. I found C++ is very difficult in unreal project, even with the experience of building deep neural network for robot soccer back in university🤔
11 -
Hey! Just curious, is it normal that a technical test/challenge takes me more than a day to do?
I have been interviewed for a front-end role, and was given a react challenge. They said that it shouldn't take more than 2 hours ('hopefully' is what they added at the end). But i've been doing this challenge for a day now and it's only 60-70% done.
It's not complicated, and I do know how to do it, and, even, do it properly, it just takes a lot of time for me to code, i.e. develop components, change webpack when needed, read react materialize-ui (css framework) docs, then destructure json response from the api they provided and put this information on a page, then try to compile to the right format (they want single .html element with inline js and css as a deliverable).
So my question is, am I shit or is it unreasonable for a company to ask do so much coding or a little bit of both?
What's your experience usually when looking for a job in 'hip' and 'cool' startups?4 -
Did an interesting experiment a few days ago, I counted the lines of code in my dissertation project. My project consists of a cloud hosted web service which allows video streaming, search and upload, as well as an iOS frontend which allows users to record their own video and upload it. The entire project spans about 2,400 lines of code. Then I looked in my work iOS project and saw a JavaScript file for manipulating form elements which spans about 2,100 lines of code. The whole project is about 100,000 lines of code and doesnt do anything special, it just calls a web API and saves/displays results mainly.
The effect of “Enterprise Architecture”1 -
This is how it looks like when you are a programmer and you was born in Iran :)
Nobody will be your sponsor for your job applications 😏
6 -
[ WEBDEV frontend QUESTION ]
I will need to build a new admin dashboard for representing a lot of data from the api. the API is written in PHP and this won't change. We are currently using jquery to make the data interactive (choose date ranges, different filters and so on). Were currently using morris.js for charts. I'm thinking this would be a good opportunity to learn and use a new js framework to make the data more easily bindable on buttons and selects (not so many listeners on buttons and shit like that).I will be developing the front end on my own, alone, so i mostly have freedom here. I need something that has implementations of chart rendering, and which I could learn in a week or two in the evenings after work (starting to work on this in the next week probably). What are your guys recommendation? Whats the best option for dashboards js wise? I was thinking vue, won't I shoot myself in the foot for using a new technology(for me anyway) right from the bat?2 -
stateofjs survey reminds me of all that's wrong with JavaScript: too many frameworks each of which has to reinvent the wheel and depend on too many node_modules child dependencies, most don't support TypeScript properly (ever tried to convert a node-express-mongoose tutorial to TS?), there is still no proper type support in JS core language, and browser features get added in form of overly complex APIs instead of handy DOM methods.
Instead the community gets excited about micro-improvements like optional chaining which has been possible in other languages for decades.
At least there is something like TypeScript, but I don't like its syntax either, it's overly verbose and adds too much "Java feeling" to JavaScript in my opinion.
Also there is too much JS in web development, as CSS and HTML seem to have missed adding enough native functionality that works reliable cross browser to build websites in a descriptive way without misunderstanding web dev for application engineering.
After all, I'd rather have frontend PHP than more JavaScript everywhere.
Anyway, at least the survey has the option to choose how satisfied or unsatisfied people are about certain aspects of JS. But I already suspect that most respondents will seem to be very happy and eager to learn the latest hype train frameworks or stick to their beloved React in the future.5 -
Why useImperativeHandle in React is bad?
I have component A. I have component B which is a child of A.
I have button in component A that should change how component B is displayed.
Usual approach is to set state in A, change it upon click and pass that state as flag via props to B.
But there is another approach via exposing ref to component B using forwardRef() + useImperativeHandle().
And then calling method that belongs to B from A. Like this: bRef.current.changeDisplay()
https://stackoverflow.com/questions...
https://reactjs.org/docs/...
https://github.com/reactjs/...
People on SoF and Docs say that the first way is preferrable. But no one explain why.
Does anyone know why calling child method from parent is considered bad?4 -
What's the general Software Engineering rule of thumb again for frontend templating code?
If I look at certain websites, I notice some code smells in PHP such as:
$.modal = <?php echo $(base)["username"] != 'me' ?' ': echo 'style="display=none"' ?>
or just in general places in the code where PHP gets used as a templating engine for gluing together pieces of HTML code based on conditionals spread out over the codebase and the database itself too. To make things worse, this carries over to JavaScript ajax functions. As a developer, this to me just seems like spaghetticode.
On the other hand, many popular frameworks properly do templating, such as EJS, containing templating in one place and not mixing it with logic too much but just having simple output like <%= %>.
I know I've seen frameworks like Angular 1 contain pieces of HTML into directives, but maybe that's something different, more 'OO'-simulating or cleaner.3 -
Okay, I may regret this...but I am desperate.
Anybody know any recruiters looking for a remote JavaScript developer? Frontend, backend, fullstack, doesn't matter (see line 1, column 27)
I'm tired of being denied by companies 😭😭😭4 -
I've to say that javascript is no language I like because I'm more fastinated of building a nice and scalable backend then building a gui (in the browser).
The funny thing is that right now javascript helps me at my current project because many websites implement wide-opened apis for their js frontend and it just works like a charm to use them instead of parsing the whole html and do some XPath stuff to fetch information. -
"Hello world"
Which mechanical keyboard do you recommend me to use for coding?
And what about mechanical switch ?13 -
Hummm(flash back)... I was studying art and design when I've decided to become a web designer, but by the time it came to take my degree also took some frontend languages and them(big explosion and fireworks) it was like magic, I could design and give life to my creations!!! 6 years later still is magic(not the rainbow and unicorns type) ...you know dam well i am talking to you javascript(and your dam post apocalypse bugs)... 😁😁😁 still wouldn't imagine my self doing anything else!
-
what's up with backend devs getting on rants about frontend frameworks? Don't they use frameworks for developing their precious servers? or do they just write the whole thing from scratch?
Shit tards, frontend development is evolving and for the better, we've got awesome frameworks that help us reduce the amount of code we need to write to attain a functionality and in a way that reduces headaches when building a large application and gives superb consistent performance because the code has been production tested a million times! yeah you can use js to build a frontend because its JS it's what it was designed to do, but tell me how reinventing the wheel everytime you make a frontend is useful, and how that is maintainable in the long run when building a large production frontend?
The modern frameworks, help us write modular and reusable components that can be shared and used by anyone for any of their application. They are arming the web with capabilities that are close to what native apps offer and still you keep bitching about it.1 -
Many memes mock frontend development, showing a beautiful and simply frontside of something in contrast to an exceptionally chaotic backside or inside of a product.
Single page applications by fullstack developers combine both sides, bringing the unpolished industrial aesthetic of backend logic to JavaScript while making sure that also the frontend isn't that shiny at least at second glance.4 -
I genuinely want to know about the thoughts of more exp devs in this community to tell me about the JavaScript and latest frameworks. But only in job and good pay perspective. I know js hardly qualifies as a proper programming language. But right now and am working as a frontend developer with angular 5 and was looking for some advice in building a career in js related technologies.1
-
Is it wrong of me to want to learn technologies like GraphQL, databases, Nest.js, and other backend related technologies without having solid HTML, CSS, and JavaScript knowledge? I've been working with Node.js and Express.js for a couple years now but really want to dive into more of whats possible on the backend but I never felt interested to learn the frontend. I do have some very basic knowledge of HTML, CSS, and JavaScript, but I feel I couldn't pass a technical interview related to them. I just find the backend so much more interesting and fun to work with over the frontend.3
-
Php framework which provides nothing more than user management and separate admin and user login? Without shitload amount of external dependencies and packages? I want to give the mysql location and done, I don't want to learn some shitty js frontend you're forcing on me because you think it's fancy... Is there something with a kind of a pull-> works way? I develop javascript stuff, and I'm really tired of installing bunch of garbage what I don't even use. They're all pushing some extra js frameworks too, I need user management and that's it. Even Laravel started to be discusting..
-
Last night on uyouthe’s weird dreams:
- I gave an interview about my ex and why she died
- my other ex got involved in huge marketing campaign of a new laser surgery by receiving said surgery but they somehow completely evaporate her pelvic and hip bones with laser. I saw her body after that happened
- I somehow live in 2003 Netherlands and work for some scientific lab as a frontend developer. All that ie and ancient JavaScript shit but I like that, processes and culture are flawless
- many other weird shit regarding self-driving vehicles being a mainstream and me owning one, my grandma turning evil and send swat to take me down, also I met a lot of hipsters at defcon and I don’t know why are they there
All that in one dream. Amazing. -
Hi guys. I could use a bit of help. I am receiving the lastLogout data from the DB, and if it's NULL, it means that I will start the tutorial because it's the first login. I am rendering with serverside, and I'm using handlebars. So the data is rendered nicely with
<div>
{{needTut}}
</div>
What is the best practice to watch for this piece of information from frontend javascript? Shall I simply create an event listener? It feels a bit dirty...3 -
!rant
That moment when you choose a JavaScript frontend framework based on the color of its logo (really love green color)2
Top Tags
Weekly Rant
View