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
-
We will no longer be accepting contracts which have an internet explorer or edge support requirement.
All of the front end devs are going hysterical and celebrating 😂 🎉🎉17 -
So because of the sheer number of interviews I’ve been doing I’m starting to get a bit brazen with them since I’ve started to really not give a fuck about most of them and I’ve started to notice patterns in common lines of questioning resulting in this unexpected gem today:
Interviewer: So we always start our devs off on the bottom end of our salary band.
Dev: Either give me the top or I’m not interested.
Interviewer: 😡. But if we start you at the top of the salary band we’ll have nothing to give you later. 🥺.
Dev: No need, I’ll take the money up front. Companies don’t give raises these days anyway, it’s just a carrot to dangle in front of the naive.
Interviewer: 😡. Well if all you care about is money so focussed on money you’ll just leave if a better offer comes around!
Dev: All the more reason to give me the highest number possible to defend against that possibility.
Interviewer: 😡. But there are other devs on the team with similar experience that will be making less than you.
Dev: Sounds like they fell for the negging and guilt tripping you are currently attempting on me in order to save a buck. Salary is not based on your skills or experience anymore, it’s based on your ability to negotiate. Here’s mine.
Interviewer: ………………. I’ll pass you along to the hiring manager.
Dev: ???? wtf
HOW THE FUCK DID THAT ACTUALLY WORK ARE YOU FUCKING KIDDING ME I WAS TRYING TO GET THEM TO HANG UP FOR SHITS AND GIGGLES AND NOW I’M LOOKING AT A 20K RAISE ALL BECAUSE I CONTINUALLY TOLD THEM TO GO FUCK THEMSELVES??? THIS IS ACTUALLY WHAT IT TAKES TO BE TREATED PROPERLY BY A COMPANY???13 -
I'm a new developer. Here is the top advice I've received:
0. Think like a programmer, outside of work too.
1. Programming is tough. It takes a certain kind of mindset to sit in front of a monitor and think it through a problem till the end. Develop that mindset.
2. Handwork pays.
3. Do it for fun. Be exceptional. Money will follow.
4. Care about the craft you build. Write such a beautiful code that your fellow devs would think about your code and have a nerdgasm.
5. Simple is beautiful. Anybody can make things complex. It takes a stroke of genius to make things simple.
6. Write modular code. It makes your code reusable and easy to maintain. Future developers who will work on your piece of code will appreciate it.
7. Share your knowledge. Unlike materialistic things, knowledge grows when you share it.
8. Add comments. You think you'll remember why you wrote that piece of code that way or a clever hack you created but trust me, you won't.
9. Be humble. You'll never know everything. Don't hesitate to ask for help.
10. Writing code is exciting! Of course there will be some frustrating moments. But don't give up! You'll miss a lot of fun.5 -
The world will remain fucked up until the moment when backend devs will get as much credit as front end. Backend devs unite! All servers down so they can see who has real power!10
-
Tip for devs (esp front end):
Sublime text (and few other inferior editors) has a plugin called "transparency" that allows your editor to be transparent.
Windows 10 powershell consoles can be made transparent.
1) Open browser
2) Open command prompt over it with 75% transparency
3) Open editor over both with 50% transparency.
4) Set editor to fullscreen, no-distraction mode to center the text (Shift+F11 in sublime)
Enjoy coding while constantly viewing the code, the browser and monitoring the cmd prompt at the same time, without having to click Alt+Tab a zillion times.
17 -
Recruiter: are you interested in a client side java role?
Me: yes, here is my client side resume please submit me
Recruiter: sorry the hiring manager said they are looking for more of a back-end engineer
Me: you told me it was a client side role, please resubmit me with my back-end geared resume
Recruiter: yes that's correct, it's client side, we'll keep you in mind for the future but you should know there is a difference between mobile devs and web devs
Me: what you just said is not relevant to this conversation. I would be happy to discuss the diff between front-end and back-end, client vs server, etc.
Recruiter: I'm just relaying what the hiring manager is saying to me
Me: your [lack of] ability to relay technical information is quite apparent :/
*lesson learned*: interview recruiters before they start interviewing me
Unbelievable waste of time, how do these people even make a living? FML!16 -
So today was shite. I get done with classes for today after going to work in the morning( college student) and I get a phone call. SURPRISE! We have a client meeting in twenty minutes.
My class runs from 5-9 and the meeting was scheduled at 7:30. I was let out early thank god. Then made sure that we had deliverables for the project running and ready to go.
Meeting with the client went well and he was pleased with my progress.
Now I have been the only one developing any sort of deliverable for this website. It originally started out with three people. The main developer will call him Cunt and a front-end dev that isn't on the project anymore.
FUCKING CUNT DECIDED TO COME AT ME FOR SAYING THAT THERE WAS A MISCOMMUNICATION ERROR AND ONE OF THE TASKS WASNT FINISHED. THEN CUNT ASKED IF I HAD ALL OF THE FRONT DEVS PAGES TO WHICH I SIGHED YES. CUNT FUCKFACE PROCEEDED TO EDUCATE ME ON HOW TO TALK TO OTHER DEVS AND NOT MAKE CRITICIZE HER CODE. UM CUNT YOU HAVENT COMMUNICATED WITH HER FOR THE THREE MONTHS IVE BEEN ON THIS PROJECT. AND YOUVE CONSTANTLY AVOIDED BEING IN THE OFFICE WHEN ANYONE IS PRESENT AND EVEN SHOOED HER AWAY. THE FACT THAT CUNT ISNT FIRED IS BECAUSE I TOOK LEAD ON HIS PROJECT AND HAVE MAKING EVERY DEADLINE FOR THIS AND OTHER PROJECTS.
*breaths*
Moral of this. Don't be a CUNT!2 -
I fucking hate websites that refuse to show their content unless you enable their JS clusterfuck. Yes I am blocking JavaScript because I'm sick of all those goddamn frameworks from God knows what domain. IS THAT FUCKING WRONG?!! I don't hate front-end devs, in fact I respect them for keeping up with design needs of shitty clients. But that fucking Web 2.0 with 50 frameworks per tab and no HTML or even PHP whatsoever for those who block your JS crap.. shove it right up your fucking ass!!!19
-
*Opens some Computerphile video on YouTube in Chrome Canary*
CPU > hey ho dude, wait a minute..! I can't process all of this in realtime!!! >_<
Alright.. I think I've still got a copy of all their videos sitting somewhere in the file server.. perhaps I could use that instead.
*Opens said video from the file server in SMPlayer*
CPU > aah, thanks man. Now I can allocate 15-ish % of my resources to that and give you a good watching experience.
Web browsers are really great for being the most general-purpose document viewers, application execution environments (remote code execution engines as someone here called it), and overall be one of the most versatile programs on any PC's standard software suite.
But that comes at a price.. performance. And definitely when it comes to featureful fucking WordPress shitsites (shites?), bloated YouTube, Google, Facebook, and all that fucking garbage.. I fucking hate web browsers and this "Web 2.0" that people keep on talking about. Your boatload of JavaScript frameworks just to ease your own fucking development has a real impact when it happens on dozens of tabs, you know.
Besides, can't those framework creators just make it into a "compiler" * of sorts? So that front-end devs can flail their dicks in an shit-infested environment full of libraries and frameworks all they want, but the framework can convert it into plain JS code that the web server can then serve. Or better yet, the JavaScript standard could be improved to actually be usable on its own!
Look, I'm not a front-end dev. Heck, I'm not even a dev to begin with. But what I do know is that efficiency matters, especially at large scale. Web browsers being so overgeneralized and web devs adding a boatload of fucking libraries or frameworks or whatever, it adds up, both to the CPU's and my own temper.
(*) Quote marks because source code to source code isn't really compiling, but then uglified JS looks worse than machine code anyway so meh :/6 -
How I discovered I was a developer:
The company had hired a pair of computer science graduates and we had been commissioned to build a magento store. Weeks went buy with limited progress, and missing functionality was met with protestations from the devs about unreasonable demands.
At this time I had been taken on as a designer / casual front end developer (though the focus was on design). I knew HTML, CSS and some very limited php and js.
We were severely over deadline, and seeing the desperation on people's faces I suggested looking into it.
I read the magento docs, got an install up an running, configured an installed plugins, integrated the theme using the complex multilevelled XML/phtml architecture magento uses and even got some of the more complex js functionality working using JavaScript.
In two weeks.
I'm now the lead developer4 -
So today, I managed to make one of my colleagues feel like an idiot. In this contract, I work mostly for ui integration, while he build the pages with angular before I add all the html structure and fancy css.
We are building the front-end/ui for an industrial device with a touch screen. For that last 2 days he was blocked on a bug that when you click the confirm button on a delete popup, it would somehow select an input in the page before it was deleted and would lock the ui when showing the virtual keyboard (the poor thing didn't know what to do and wouldn't close).
During those two days, he asked all the other devs for help, trying to find a pattern or anything that could help, while I was focused on writing my css and stuff since it was my priority and I was hired specifically for that (I was aware of the bug and gave my input but I never saw it being reproduced)
So today, he start his new routine of raging at his desk and he decides to show me on my device for some reason. I immediately notice a pattern. It would always select one of the two fields behind the popup, in the click area of the button (it's a big button). Then, I noticed that I could press a random spot on the screen, drag my finger on the button and let go and nothing would happen.
It's at this moment I knew I had found the bug. The button was set to emit an event on mousedown while the inputs behind it were set to emit an event on mouseup (like it should be everywhere). So the popup closed when you placed your finger on the screen and the input was selected immediately after when you removed your finger (which was usually faster than the page code which was not yet optimized)
After that, it was just an easy fix to change the listener and I had a free beer.1 -
Post Anger Rant (Beware, Long rant ahead)
So there is this project we have been working for months, most of the devs involved are jr students so I was leading them in the architecture and what to do and they were doing it, the progress was slow but safe and fun.
On the team there was this guy, someone I trusted and in who I had special interest for his skills, so I let him own the github repo.
So the day of the first demo I pull the backend changes ( I had been working on front end ) and I realize that the code was different, so I started using my super awesome forensic skills to find what happened,and when I say different I mean a totally different architecture different database connections, different service pirts, basically other project, so during my criminal investigation I found out this guy I trusted had never really worked with us, from the beginning he went solo working on his own project and changing everything because of some tutorial he found on the internet, so I decided to reset to the previous version just to find out that he had already deployed the code and that a lot of fixes that we should have were only on his version.
So I went and confront him telling him that he did wrong and he had to learn team work and that I was trying to teach them good practices and he waits and asks me "so, my code was wrong?" Seriously what da hell dude? I'm talking about team work and all you can think about is your code.
Finally he admitted his mistake and repented (I think), but seriously how arrogant must you be to ignore a whole team, specially when on your first real project.8 -
Alright, I've already ranted about this but I feel like that was rather incomplete.. there's some other things that make me want to kill myself every time I enter <!DOCT- WHERE IS THAT FUCKING KNIFE?!!!
First one I've mentioned earlier is its <repetitiveness></repetitiveness>. What was wrong with {brackets}? If only HTML was more like CSS.
But there's some other ones as well.
- Frameworks! Ain't there nothing like a good dozen resources that every single one of your web pages wants to get JS from.
- Quantity over quality. Let's just publish early with tonnes of bugs, move fast and break things, amirite 🤪
- General noobness of apprentice web devs. Now I'm not talking about the real front-end devs here - AlexDeLarge was one of them.. forever holding a special place in my heart - that know how to properly use their tools. But there's a metric shitton of people who think that being able to write <html><body>Hello world!</body></html> makes them a dev.
- The general thought of "it's slow? Slap in more hardware." Now this is a general issue with software development, optimization costs valuable resources while leaving it in a shitty state but released quickly costs pretty much nothing. A friend of mine whose post I'll attach in the image section illustrates this pretty well. You can find it at https://facebook.com/10000171480431....
I'm not sure if this is an exhaustive list, but those are the most important things that irritate me about web development in general.
On a side note, apparently 113 people visited my hiddenbio.html page.. I'm genuinely impressed! I had no idea that so many people on devRant would click through. On Facebook pages this has been an ongoing significant issue of getting people to leave the platform - it's huge but engagement on off-Facebook links is terrible. I guess that I'm dealing with an entirely different community here. And I'm pleasantly surprised actually!
11 -
Just got my beta access for Framer X. They describe themselves as "Unity for design" bridging the gap between Sketch and React using code-based components. I think it has a lot of potential. Would love some non-designer perspectives. What do the front-end devs here think of it?10
-
You utter &@£#s. You give rediclious promises to clients without consulting Devs how long items will take, when issues with project are clarified with client months in advance you turn around week before last and do a massive U turn. Expect junior developers to be masters of Photoshop, flash, server side technologies and to get around and code the front end. Then developers who are putting in the over time already you demand a massive load of overtime extra and threaten us if we don't meet the deadline?! Sat here blood boiling. last guy here litrually rage quit because of issues like this and #&## I think I'm going to too, so hard to try stay professional! ##&##&# I have had it!2
-
After I spent 4 years in a startup company (it was literally just me and a guy who started it).
Being web dev in this company meant you did everything from A-Z. Mostly though it was shitty hacky "websites/webapps" on one of the 3 shitty CMSs.
At some point we had 2 other devs and 2 designers (thank god he hired some cause previously he tried designing them on his own and every site looked like a dead puppy soaked in ass juice).
My title changed from a peasant web dev to technical lead which meant shit. I was doing normal dev work + managing all projects. This basically meant that I had to show all junior devs (mostly interns) how to do their jobs. Client meetings, first point of contact for them, caring an "out of hours" support phone 24/7, new staff interviews, hiring, training and much more.
Unrealistic deadlines, stress and pulling hair were a norm as was taking the blame anytime something went wrong (which happened very often).
All of that would be fine with me if I was paid accordingly, treated with respect as a loyal part of the team but that of course wasn't the case.
But that wasn't the worst part about this job. The worst thing was the constant feeling that I'm falling behind, so far behind that I'll never be able to catch up. Being passionate about web development since I was a kid this was scaring the shit out of me. Said company of course didn't provide any training, time to learn or opportunities to progress.
After these 4 years I felt burnt out. Programming, once exciting became boring and stale. At this point I have started looking for a new job but looking at the requirements I was sure I ain't going anywhere. You see when I was busy hacking PHP CMSs, OOPHP became a thing and javascript exploded. In the little spare time I had I tried online courses but everyone knows it's not the same, doing a course and actually using certain technology in practice. Not going to mention that recruiters usually expect a number of years of experience using the technology/framework/language.
That was the moment I lost faith in my web dev future.
Happy to say though about a month later I did get a job in a great agency as a front end developer (it felt amazing to focus on one thing after all these years of "full-stack bullshit), got a decent salary (way more than I expected) and work with really amazing and creative people. I get almost too much time to learn new stuff and I got up to speed with the latest tech in a few weeks. I'm happy.
Advice? I don't really have any, but I guess never lose faith in yourself.3 -
One of the dumbest things I've done as a dev... I was a front-end/php guy that got hired into a asp.net company. My boss told me to take down a section of the website. I hopped on the server and started looking at files and saved a config file. 2 minutes later I had 3 devs in my office asking what I'd done that took down our entire network.
Thankfully my boss laughed it after they republished the site, but that was my intro into asp.net development.1 -
getting into dev work is such a shit show. thinking back 2 years ago I decided to switch career so went on bootcamp and starting looking for junior role.
as you know full well all jobs requires 5+ years when the tech has only been around 3. Anyhow, got a junior full stack role at a start up, all good , great pace (cos of startup) and wide range of tech to learn. one minute i am doing great , next day I am not good enough and got let go (WTF?) ,also whats up with some backend devs Jesus why wouldnt you let me put a " on aws because you are the backend dev what the fuck is wrong with your ego man?
fun story number 2: after being let go of my first role due to being good dev for one day and bad the next. I went for an intern role for really low paid. well fair enough I am here to learn right guys? nope, i have experience with the main tech from my last job and I managed the take home test and despite I told them i have more experience front end they criticise my backend code , despite i was able to tell them what I have done not so well and I have found a better solution AT THE INTERVIEW. still not good enough. I was really doubting myself If I am that shit at being an fucking intern with a stack I have experience in.
fast forward another job interview I landed my current role with fantastic culture, good line manager & tech lead. nice colleague and I am being treated like a prince with the work i put in. Why is this industry so fucked?
so, folks out there trying to get into this game. dont lose hope, you can do it , you just need to get fucked a bit to know whats good out there!5 -
I AM TIRED
warning: this rant is going to be full of negativity , CAPS, and cursing.
People always think and they always write that programming is an analytical profession. IF YOU CANNOT THINK IN AN ANALYTICAL WAY THIS JOB IS NOT FOR YOU! But the reality could not be farther from the truth.
A LOT of people in this field whether they're technical people or otherwise, just lack any kind of reasoning or "ANALYTICAL" thinking skills. If anything, a lot of of them are delusional and/or they just care about looking COOL. "Because programming is like getting paid to solve puzzles" *insert stupid retarded laugh here*.
A lot of devs out there just read a book or two and read a Medium article by another wannabe, now think they're hot shit. They know what they're doing. They're the gods of "clean" and "modular" design and all companies should be in AWE of their skills paralleled only by those of deities!
Everyone out there and their Neanderthal ancestor from start-up founders to developers think they're the next Google/Amazon/Facebook/*insert fancy shitty tech company*.
Founder? THEY WANT TO MOVE FAST AND GET TO MARKET FAST WITH STUPID DEADLINES! even if it's not necessary. Why? BECAUSE YOU INFERIOR DEVELOPER HAVE NOT READ THE STUPID HOT PILE OF GARBAGE I READ ONLINE BY THE POEPLE I BLINDLY COPY! "IF YOU'RE NOT EMBARRASSED BY THE FIRST VERSION OF YOU APP, YOU DID SOMETHING WRONG" - someone at Amazon.
Well you delusional brainless piece of stupidity, YOU ARE NOT AMAZON. THE FIRST VERSION THAT THIS AMAZON FOUNDER IS EMBARRASSED ABOUT IS WHAT YOU JERK OFF TO AT NIGHT! IT IS WHAT YOU DREAM ABOUT HAVING!
And oh let's not forget the tech stacks that make absolutely no fucking sense and are just a pile of glue and abstraction levels on top of abstraction levels that are being used everywhere. Why? BECAUSE GOOGLE DOES IT THAT WAY DUH!! And when Google (or any other fancy shit company) changes it, the old shitty tech stack that by some miracle you got to work and everyone is writing in, is now all of a sudden OBSOLETE! IT IS OLD. NO ONE IS WRITING SHIT IN THAT ANYMORE!
And oh my god do I get a PTSD every time I hear a stupid fucker saying shit like "clean architecture" "clean shit" "best practice". Because I have yet to see someone whose sentences HAVE TO HAVE one of these words in them, that actually writes anything decent. They say this shit because of some garbage article they read online and in reality when you look at their code it is hot heap of horseshit after eating something rancid. NOTHING IS CLEAN ABOUT IT. NOTHING IS DONE RIGHT. AND OH GOD IF THAT PERSON WAS YOUR TECH MANAGER AND YOU HAVE TO LISTEN TO THEM RUNNING THEIR SHITHOLE ABOUT HOW YOUR SIMPLE CODE IS "NOT CLEAN". And when you think that there might be a valid reason to why they're doing things that way, you get an answer of someone in an interview who's been asked about something they don't know, but they're trying to BS their way to sounding smart and knowledgable. 0 logic 0 reason 0 brain.
Let me give you a couple of examples from my unfortunate encounters in the land of the delusional.
I was working at this start up which is fairly successful and there was this guy responsible for developing the front-end of their website using ReactJS and they're using Redux (WHOSE SOLE PURPOSE IS TO ELIMINATE PASSING ATTRIBUTES FOR THE PURPOSE OF PASSING THEM DOWN THE COMPONENT HIERARCHY AGIAN). This guy kept ranting about their quality and their shit every single time we had a conversation about the code while I was getting to know everything. Also keep in mind he was the one who decided to use Redux. Low and behold there was this component which has THIRTY MOTHERFUCKING SEVEN PROPERTIES WHOSE SOLE PURPOSE IS BE PASSED DOWN AGAIN LIKE 3 TO 4 TIMES!.
This stupid shit kept telling me to write code in a "functional" style. AND ALL HE KNOWS ABOUT FUNCTIONAL PROGRAMMING IS USING MAP, FILTER, REDUCE! And says shit like "WE DONT NEED UNIT TESTS BECAUSE FUNCTIONAL PROGRAMMING HAS NO ERRORS!" Later on I found that he read a book about functional programming in JS and now he fucking thinks he knows what functional programming is! Oh I forgot to mention that the body of his "maps" is like 70 fucking lines of code!
Another fin-tech company I worked at had a quote from Machiavelli's The Prince on EACH FUCKING DESK:
"There is nothing more difficult to take in hand, more perilous to conduct, or more uncertain in its success, than to take the lead in the introduction of a new order of things."
MOTHERFUCKER! NEW ORDER OF THINGS? THERE 10 OTHER COMPANIES DOING THE SAME SHIT ALREADY!
And the one that got on my nerves as a space lover. Is a quote from Kennedy's speech about going to the moon in the 60s "We choose to go to the moon and do the hard things ..."
YOU FUCKING DELUSIONAL CUNT! YOU THINK BUILDING YOUR SHITTY COPY PASTED START UP IS COMPARABLE TO GOING TO THE MOON IN THE 60S?
I am just tired of all those fuckers.13 -
After being live multiple years supporting only Safari, Firefox, and Chrome, one customer wanted IE support. After taking a close look at the usage numbers, and discussing with us front-end devs, our product guy shot it down. Pop the champagne!2
-
Hi all, first rant.
I work on an app on the Shopify platform, which requires me to look at the front end of people’s Shopify stores about half the day.
Can we PLEASE get the Shopify devs together and convince them to put a hard limit on the number of pop ups and slide ins and modal apps a single store can have running??? When a user (or app developer) can’t click on a product to buy it (or test installation) because ‘spin the wheel’ and ‘join the mailing list’ and ‘Karen in Ohio just bought a toaster’ won’t stop popping into the view, your UX is shit.
I realize people could still actually go in and build these things into their store code - but I’m willing to bet VERY few would.
Thanks - rant over.2 -
The tale of the asinine Typescript framework guy continues:
>guy makes a framework
>promotes it
>people don't wanna use it because it's mediocre
>doesn't care, he still promotes it
>people started criticizing his framework
>won't listen
>calls his critics haters
>thinks PH tech guys are way behind the world
>says a lot of bad takes in tech himself
>such as NodeJS used as a front-end
>people tryna correct his bad takes
>calls them haters too
>people start complaining
>gets banned in many PH tech communities
>except one
>total windbag in there
>somebody calls him out, explains why they hate him
>he says his framework will be famous and we will all be eating dust
>heckler tells him he is not only the person in the open source community and tells him a famous Filipino open source contributor
>says he doesn't know this famous contributor and he doesn't care
>challenges heckler to confront him face to face
>heckler calls his bluff and gives a place and time to meet
>big guy agrees to meet
>people are clamoring for him to shut up
>admin tells him and the heckler to shut up
>big guy pushes it
>calls the admin (female) a puta (whore)
>gets banned
>goes on Facebook saying that his heckler will not show up in that place despite it being the favorite hangout place of the heckler since 2017
>that he is being banned because of haters
>people call him out on his Facebook posts and he takes them down
>people in the tech community started thrashing his Github with prank forks and PRs
>guy tries to shame them on Facebook
>gets rekt by tech people
>goes on Twitter saying that backward PH devs are oppressing him
>even tagging the famous devs
@marcusignacius I have lost total sympathy for this guy and his framework. Arrogant, petulant, childish, and uncharitable. honestly he brought this on himself.
Somebody honestly slap him this rant on Twitter pretty please.
22 -
I'm a front end developer who knows Ruby on rails and Node Js, I still call myself a freaking FRONT END DEVELOPER because I don't have enough knowledge of the required concepts to trust my skill in a complex backend project.
How the fuck there are so many full stack developers who lack shit tons of knowledge in both specialties! And worst of those are asp.net "FULLSTACK DEVS" that can't write JavaScript without copying and pasting from SO and don't know that display flex is a thing!14 -
Copying a javascript anonymous function (Yes, the whole function) 11 times with only one parameter changing
I'm currently cleaning it up...
O H B O Y F U N D A Y S I N C O M M I N G...3 -
Sorry to keep whining about my stupid fucking job, but y'all, I think I'm nearing my limit.
There's some good...I am pretty much free to resolve issues any way I want to, as the only other person in the company who "codes" only knows one old ass language that doesn't apply to 90% of the rest of the tech stack at all, and some SQL - all of that to say, we may disagree, but ultimately, these matters are always deferred to me at the end of the day, insofar as the actual implementation goes (which is to say I am not micromanaged). At least as far as non-visuals are concerned, because those of course, are the most important things. Button colors and shit, woo hoo**. That's what we should focus on as we're bringing in potentially millions of dollars per month - the god damn button color and collapsible accordions based on data type over the shit ass DB performance bottleneck, the lack of redundancy or backups (aside from the one I made soon after I started -- literally saved everyone today because of that. My thanks? None, and more bullshit tasks) or the 300GB+ spaghetti code nightmare that is the literal circulatory system of the FUCKING COMPANY. Hundreds of people depend on it for their livelihoods, and those of their families, but fuck me in the face, right? I'm just a god damn nerd who has worked for the federal government, a handful of fortune 500's, a couple of fortune 100's, some startups, etc. But the fuck do I know about the lifecycle of companies?
I could continue ranting, but what's the point? I've got a nice little adage that I've started to live by, and y'all might appreciate it: "If everything is a priority/is important, nothing is". These folks just don't fucking get it. I'm torn because, on the one hand, they waste my time and kinda underpay me, in addition to forcing me to be onsite for 50 hours a week. They don't listen to me, couldn't give a flying shit about my experientially based opinions. I'm just a fucking chimp with a typewriter, there to take commands like a fucking waiter. But there's a lot of job security, assuming I don't fucking snap one day, and the job market for devs (I'm sure I don't need to tell you) is hostile atm. I'm also drinking far more than usual, and I really need to do something about that. It's only wednesday - I think...not 100% on that truth be told, and I logged my fourth trip to the liquor store this week already.
**Dear backenders - don't ever learn front end, or if you do, just lie about it to avoid being designated full stack. It's not worth it.5 -
I honestly don't get the idea behind JavaScript frameworks. Like, if JavaScript on its own is really so bad that it's only usable for front-end devs with a framework.. why has nobody considered committing back their changes into JavaScript itself? Makes life easier for everyone.
Also, regarding the framework.. as far as I understand it's a bunch of functions that you load in, right? But do you really need all of those, to the point where the unused ones are justifiable? And wouldn't it make more sense to write them yourself as you need them? I mean that's at least the idea of functions in languages like Bash or C or whatever.
What's the point of frameworks?37 -
My first project it’s an emotional roller coaster. I was a little trainee/ junior dev at my job with a little more than a month learning RoR and one day my tech lead receives an email from the big boss saying: “We got a big client who wants a total redesign of his web and we said yes we can do it in a month, so please check if anything it’s reusable”, after reading my tech lead said to me “Do you want to help me with this ?” And well, we spend like 2-3 hours checking all the controllers, views, assets, etc. We conclude that the project was mostly front end changes and the back end will stay the same, so yeah it can be done in a month. The next day in a meeting with all the team I was nominee to be the person in charge of that project, because it was an easy project and all my teammates hate to do front end stuff, so I take the challenge. After that I met the Project Manager, another guy who recently start as PM about a month, so yeah we were two new guys who need to handle the project of a big client, nothing can go wrong. We did the planing, I give an estimation ( first one in my life ) for the tasks and added like 4 hours in case anything goes wrong. Then the first sprint came by, and I couldn’t finish it because the time given to some features was to low and the “design” was a mockup made by the PM, ok, no problems, we add more time to the tasks and we ask for a real design. At the half of the sprint the client start adding more and more stuff, the PM doesn’t talk back, just say yes yes yes. Then in a blink of an eye the easy project became a three months projects with no design at all, two devs ( a new guy who recently begin as dev enter the project ), just mockups and good hopes. But somehow we did it, we finish it! Nope. The early Monday of the next week I received an email of the PM saying we would have a second version and the estimation of the tech lead was a minimum of six months ( that became 8 months). This time was hell, because the client doesn’t decide what the hell he wants so a task would take a couple of days more or so, the PM became the personal bitch of the client, but it wasn’t his fault, because we later knew that the company became partner with this client and because of that the PM didn’t have too much choice :/, the designs were cool, but they weren’t on time ever, our only design guy had to do designs to our project and another 5 projects of the company, so yeah, we weren’t the only ones suffering. At the end we survive, the project was done and the client somehow was happy. Of course the project didn’t end and it was terminated half a year later, but I’ll always remember it because thanks to this project I was given the opportunity to work as a Front end dev and I’m happy still working as one.
-
So about 3 weeks ago I was laid off from my dream job due to corporate bullshit. From the feedback received since then it is clear that the company made a mistake hiring a brand new React dev while they really needed an experienced one. Because the consultants who were supposed to be weren't. And the other in-house front end dev was an elitist asshole. And I never received proper feedback until it was too late. Actually I still don't have proper feedback save for some vague stuff which really sounds like the kind of feedback you'd give someone in the middle of their learning process. They even said eventually given more time I could have made it. But alas they felt they had to make a call in the best interest of the company.
Things moved fast since then, I took a week to recover and then I spent time updating my resume before getting back in touch with the recruiter who got me my last job. Great guy and he was happy to help me again. Applied to some positions, got some replies, first in person interview I go to they are immediately willing to take me on.
So now I'm supposed to start tomorrow but somehow I'm having my doubts. The company isn't an IT company but rather a fashion company. They believe in developing in house tools because past attempts with external companies resulted in them trying to push their vision through. Knowing who they worked with I agree, they tried to oversell all the time. But after talking with their developers I noticed they are behind on their knowledge. But so am I. So there was no tech interview which means I am getting an easy way in. And if they honour their word I'll be signing tomorrow for around my old wages.
So you'd think that sounds good right? And yet I'm worried it's going to be another shit show working on software without proper analysis or best practices. I mean the devs aren't total idiots, they are mediors like me and I think their heart is in the right place. They want to develop a good project but it will be just us 3 making a modern .net wpf application with the same functionality of the old Access based system currently in use. I was urged by the boss to draw on my experience and I think he wants me to help teach them too. But I'm painfully aware for my decade since graduating I'm a less than average .net dev who struggles with theory and never worked a job where I had someone more experienced to teach me. I coasted most of the time in underpaid jobs due to various reasons. But I'd always get mad over shitty code and practices. Which I realize is hypocritical for someone who couldn't explain what a singleton class is or who still fails at separation of concerns.
So yeah my question for the hivemind is what advice would you give a dev like me? I honestly dislike how poor I perform but it often feels like an insurmountable climb, and being over 30 makes it even more depressing. On the other hand I know I should feel blessed to find a workplace who seems to genuinely believe that people grow and develop and wishes to support me in this. Part of me thinks I should just go in, relax, but also learn till I'm there where I want to be and see if these people are open to improving with me. But part of me also feels I'm rushing into this, picking the first best offer, and it sure feels like a step backwards somehow. And that then makes me feel like an ugly ungrateful person who deserves her bad luck because she expects of others what she can't even do herself :(4 -
Alright devs let's see those faces #devfacefriday what's your specialties? (Me === red flannel,front-end. Bff === cream flannel, back-end.)
5 -
Well today is my last day at my current job. I have enjoyed the last 4 and a half years here and learned a lot.
This last week of my notice period has been surreal though and quiet a stark contrast to how things have been.
Before I was the "go to" person for pretty much the entire dev team even though I am hired as a front end dev (so my remit was the companies website). This included the backend devs who worked on the internal business software.
The last few days have felt like I was a "persona non-grata". Conversations that would end up being held at my desk are now held elsewhere and what few tickets I do have have been given over to others.
I knew on some level this would happen but living through it is a different story.
Anyhow, I am looking forward to the new role I am starting Monday but will certainly miss the old team very much!3 -
(long post is long)
This one is for the .net folks. After evaluating the technology top to bottom and even reimplementing several examples I commonly use for smoke testing new technology, I'm just going to call it:
Blazor is the next Silverlight.
It's just beyond the pale in terms of being architecturally flawed, and yet they're rushing it out as hard as possible to coincide with the .Net 5 rebranding silo extravaganza. We are officially entering round 3 of "sacrifice .Net on the altar of enterprise comfort." Get excited.
Since we've arrived here, I can only assume the Asp.net Ajax fiasco is far enough in the past that a new generation of devs doesn't recall its inherent catastrophic weaknesses. The architecture was this:
1. Create a component as a "WebUserControl"
2. Any time a bound DOM operation occurs from user interaction, send a payload back to the server
3. The server runs the code to process the event; it spits back more HTML
Some client-side js then dutifully updates the UI by unceremoniously stuffing the markup into an element's innerHTML property like so much sausage.
If you understand that, you've adequately understood how Blazor works. There's some optimization like signalR WebSockets for update streaming (the first and only time most blazor devs will ever use WebSockets, I even see developers claiming that they're "using SignalR, Idserver4, gRPC, etc." because the template seeds it for them. The hubris.), but that's the gist. The astute viewer will have noticed a few things here, including the disconnect between repaints, inability to blend update operations and transitions, and the potential for absolutely obliterative, connection-volatile, abusive transactional logic flying back and forth to the server. It's the bring out your dead approach to seeing how much of your IT budget is dedicated to paying for bandwidth and CPU time.
Blazor goes a step further in the server-side render scenario and sends every DOM event it binds to the server for processing. These include millisecond-scale events like scroll, which, at least according to GitHub issues, devs are quickly realizing requires debouncing, though they aren't quite sure how to accomplish that. Since this immediately becomes an issue with tickets saying things like, "scroll event crater server, Ugg need help! You said Blazorclub good. Ugg believe, Ugg wants reparations!" the team chooses a great answer to many problems for the wrong reasons:
gRPC
For those who aren't familiar, gRPC has a substantial amount of compression primarily courtesy of a rather excellent binary format developed by Google. Who needs the Quickie Mart, or indeed a sound markup delivery and view strategy when you can compress the shit out of the payload and ignore the problem. (Shhh, I hear you back there, no spoilers. What will happen when even that compression ceases to cut it, indeed). One might look at all this inductive-reasoning-as-development and ask themselves, "butwai?!" The reason is that the server-side story is just a way to buy time to flesh out the even more fundamentally broken browser-side story. To explain that, we need a little perspective.
The relationship between Microsoft and it's enterprise customers is your typical mutually abusive co-dependent relationship. Microsoft goes through phases of tacit disinterest, where it virtually ignores them. And rightly so, the enterprise customers tend to be weaksauce, mono-platform, mono-language types who come to work, collect a paycheck, and go home. They want to suckle on the teat of the vendor that enables them to get a plug and play experience for delivering their internal systems.
And that's fine. But it's also dull; it's the spouse that lets themselves go, it's the girlfriend in the distracted boyfriend meme. Those aren't the people who keep your platform relevant and competitive. For Microsoft, that crowd has always been the exploratory end of the developer community: alt.net, and more recently, the dotnet core community (StackOverflow 2020's most loved platform, for the haters). Alt.net seeded every competitive advantage the dotnet ecosystem has, and dotnet core capitalized on. Like DI? You're welcome. Are you enjoying MVC? Your gratitude is understood. Cool serializers, gRPC/protobuff, 1st class APIs, metadata-driven clients, code generation, micro ORMs, etc., etc., et al. Dear enterpriseur, you are fucking welcome.
Anyways, b2blazor. So, the front end (Blazor WebAssembly) story begins with the average enterprise FOMO. When enterprises get FOMO, they start to Karen/Kevin super hard, slinging around money, privilege, premiere support tickets, etc. until Microsoft, the distracted boyfriend, eventually turns back and says, "sorry babe, wut was that?" You know, shit like managers unironically looking at cloud reps and demanding to know if "you can handle our load!" Meanwhile, any actual engineer hides under the table facepalming and trying not to die from embarrassment.36 -
I am a junior web developer, currently working in my first job for a small company, I was hired because I have an interest in meteor and modern web dev.
When I say small I mean I am the only full time js dev.
So the project we are working (my first ever professional project from start to finish) is a travel booking web app (being a little vague, for the sake of privacy). I am the lead developer, as a new programmer of a project that is far from trivial. There are no other javascript devs in office, no sort of code review. We have an outsourced dev but as I got in a flow with one dev my boss supposedly told him to do it part time (without discussing with me), but haven't heard anything from him, so assuming he's just disappeared (probably annoyed at being treated like a commodity).
Boss has set up the stages, and forces me to move on to the next stage before that stage has been finished. I will have to go back over the whole thing to finish things off.
He will only hire cheap juniors, one front end guy with barely any experience is styling the site.
He is used to churning out WordPress and Magento sites.
Wish I had a senior I could learn off.
I want to stick at this project and see it through, but i can only see it ending in a train wreck.
At the same time I want out, I want to work under a better team with senior programmers and better code review.
I just have to do my best and see how it goes I guess6 -
Sometimes I feel like I am surrounded by idiots. My family are too stupid and lazy to have jobs or do anything involving a skill. They are too dumb to do anything properly so most of the house is fucked.
My co-workers are supposed to be Web devs but cba to learn the frameworks or languages we work on. Some of them have over 5 years experience and don't understand basics like backend verification vs front end.. Or even what json is. Needless to say everything I'm told to do is retarded such as implement roles and permissions where there are no roles, but ot allowed to add roles.
Anyone else surrounded by idiots 90% of the time? How do you not get worn down?2 -
!rant
Suggestion, devRant resources. A section for posting URLs of useful shit you find that may help others. Maybe categorised or just tags.
Heres one for Mac Front end devs..
Nucleo is a beautiful library of 20729 icons, and a powerful application to collect, customize and export all your icons.
https://nucleoapp.com/7 -
Story time.
We are all alike as devs, just surrounded by the people who has an idea of "new facebook", but i like how their mind works and how they long for a change, so it does not annoy me that much. I just simply explain how it is not likely to happen, without decent marketing and innovation.
However, yesterday i went to my dad's workplace, because i was bored. He has lots of friends there, and i happen to meet one. When he heard me that i am a software engineer, he told me that he has an idea.
I prepared my words to explain why it is not possible, but when i heard what it is, i was ashamed of myself.
He sells and manages car tires. He wants a simple showroom website to show what tires he has,( not stock-wise. Price, size, type, brand etc. ) and he wants to update them himself.
I swallowed my words and told him that i could do it. Normally i don't make websites, i provide utilities and APIS to make the front-end devs job easier at my work. But i will turn his idea into reality.
He said that he hired someone else for that years ago, but the one he hired made the website in ASP.NET 2.0, so making one from scratch would take much less time.
No way i would touch that mess came from the seventh layer of hell itself, to torment developers endlessly.
Just a simple front-end seasoned with bulma and pure JS, node to communicate with the DB ( maybe golang for fun ? ) and a simple admin panel for him would do the trick. I am excited !3 -
Talking about some plans today with back end devs... One person tells me the front end devs couldn't make it... I said: I wouldn't call them "devs"... Person says: Yeah, let's not mention that in front if them...1
-
The interview wasn't so bad, but it was deceiving, not to the fault of the company though. During the interview process, they were asking all sorts of questions about my Angular and front-end skills. I was to take over a project that used Angular heavily, and none of their devs knew angular. At the time, this was going to be my dream job! After I got the job, and met with the contractor who was handing over the project. He told me that he spent that weekend rewriting the whole thing on rails and ember. When I brought it up with my boss, he was not happy. I would have been fine working on it, but instead I got put onto Wordpress projects with the evergreen promise that I would transition to that project or another one like it. Never happened, built up my skills contributing to Open Source, then left.1
-
What browsers do front end devs here normally test on? I test on Firefox and Chrome because...that's all I use, but what about Edge/Safari or god forbid IE11?
I'm more familiar with backend dev ops so my testing consisted of checking Firefox a lot. :P
6 -
Worst day of my life.
Got a job at an awesome company in another country but joining is in November.
Bunch of us got screwed over by the current company because of "downsizing" (out of the blue, they wanna start over with 4-5 devs like 2 years back) and they don't want to keep front-end developer as anybody can do it... (yeah I remember how the site was before I came... using ! important everywhere is not the solution).
Started looking for jobs (because I need to pay rent) so that I can spend 3 months there and then quit. Facing moral dilemma, as I don't want to do that to the company who hires me now.7 -
So the story is true and this is what we have to deal with now..
My friend and I started to build a Web Application for a Roleplay Community. The project was for a client mainly and they don't mind if we try to sell this project to the public. All goes well except the shitty design, which is the one our client asked for. So after 6 months of work we planned to switch our backend to Nodejs, the switch look quite easy in our brains [PHP => NODEJS] because we already use Nodejs for instant functions without reloading the page.
So during the planning we earn a client which is one of the member of the clan, but he pay for another clan which is 6x bigger then the one we're in. So we continue to develop and think about the switch. We learn a news about a new competitor, this one sucks, we tried their App and it's not worth the money they ask. A few days after another competitor enter the market, this one is a big challenge for us. "Sit down tight, yea you reading this"..
The competitor use BUBBLE to create their shit, they earned 10 clients in one week and just punch us with "THE ROCK" hand, they release a lot of feature each week, they're 6 devs on that (if we can call them devs), we're 2 programmers (True Programmers). What we do in 1 week they do it in 5 hours with Bubble, the switching to Nodejs was a badluck, you couldn't add feature because of this switch during 2 weeks, this made us later and second in the race. My friend (at the same time my employee and back-end programmer) move into another appartment which obligate him to work full-time. At this time I'm f****, I'm only a Front-End Programmer vs 6 Wannabe Devs with a mother**** tool of *** (#Bubble).
This is where I am, in this beautiful opportunity to win this market but with this bad luck occuring = the opportunity is low, but our advantage is we don't have made our project public yet so they're the only good option for the communities to get that kind of web app, the others are not included and only a copy of this (Their Product) or just a big junk made with Wix.
At this time I'm working hard to make this opportunity happen, I have my math which I have to finish to have my High School diploma to do, a part-time job to get if I want to stay with an internet connection and finally I have to find a way to still be able to make my dream come true (Working on my Business at full time & Make money from it) and continue to be a Front-End Programmer/CEO of an enterprise.4 -
I'm starting to feel super frustrated with my job.
Sometimes I feel like people who work for large tech companies must have it easy. My company is trying to do this digital transformation thing. Modern development practices Scrum, agile, CI/CD etc. So I was put on a team to work on a project with this new methodology. The idea was we would build the front end and interface with the core systems via service calls. Of course it didn't work out that simple and we had to add our own server side stuff but whatever. It's really hard without a point of reference for any of this stuff. We don't have established coding standards, the data we are working with is a mess, incompetent vendors, the infrastructure team supporting the environments can be such arrogant fucks when we need their help to get shit done. The team also doesn't have any members who really know the core systems well. I am the only developer on the team who is an employee of the company the rest are contractors who are in and out. Last week it was literally just me. This is my first job out of school btw I've been here a year now. I guess I just feel frustrated that I have to figure out so much on my own I don't really have many senior devs at the company I can look to. And on the team I've sorta ended up in an unofficial leadership position. Feels like a lot on my shoulders. I feel like if i could have worked for a bigger company I could learn to do a lot of things better. I feel like there's too much on me for the amount of experience I have or am I wrong ?5 -
I'm really sick of elitist JS/front-end devs acting like these front-end heavy sites are any better than a traditional site using SSR (server-side rendering). Single page apps (SPAs) have 1 large benefit over an app with full page requests: the web dependencies (CSS,JS,etc) don't have to be looked up and downloaded on every page load. With optimized caching headers and HTTP2, this is not a problem. I agree with every point this guy makes: https://blog.usejournal.com/spa-or-...6
-
I am usually lurking in here since I never really worked as a Software Developer, but until I start going to the University, I thought I might also find myself a job in Software Development.
Well... I don't know where to start.
Someone in here heard of JBoss? Me neither... we're using it... It is a Framework to deploy fortified Java Web Applications. My first day was very chaotic and was dedicated to get this fucking shit to work. I got JBoss 7.5 from my colleagues and started deploying the hello world program...
So. Many. Things. Gone. Wrong...
After like 5 hours of troubleshooting, I had to install/setup a new wrapper with my own batch scripts, install SPECIFICALLY jdk 1.7_17 (anything else won't work) and downgrade JBoss to 7.2.
Yeah that's the first thing. Let's continue about JBoss. Version 7.2 uh? What's the newest one though? Oh it's now known as WildFly... huh... FUCKING HELL, THE NEWEST ONE IS VERSION 10.1??? AND EVEN 10.1 IS 1 YEAR OLD? WHAT THE FUCKING FUCKK AAAAAAHH...
So yeah, after that, without any expectation, I had a look at our codebase. Unit tests huh? I couldn't find a single self written one to test the applications functions... I asked my fellow devs and they told me that "it is too time consuming and we have to focus on new features, the QM Team will just manually test the application". Ever heard this bullshit? A big fat ass codebase with shittons of customers and not a single unit test...
So last but not least, since it is a web application, it also got a site. Y'know RichFaces? The deprecated front end library for Java Webpages? Where you got like 150 Tables per page everyone with a random id everytime you reload? Yeah I don't think I have to explain that to you guys...
So now YOU tell me? Is this a place to be 😂😂😂6 -
Did my first meaningful work in angular in many moons at work today - also apparently the first time I've touched it in 4 major version releases lol.
I typically find myself specializing in API and service architecture lately, so I was pleasantly surprised at how quickly I got back into the swing of things with the front end in general. Granted the app itself has been very neatly organised and written which goes a very long way to helping one find their way quickly.
That said, I really can't admit to having any desire to stay working in angular for very long. Yes, I think it speaks well to the framework itself that I can pick up immediately going from version 8 to 12 without any issue, but also, I think angular kinda sucks ass*.
* Opinion should be taken with a grain of salt coming from a .NET dev. This does not reflect the views of .NET or other devs in general. User results may vary.1 -
If some of you front-end devs haven't used CSS-Grid yet and are still annoyed by using nasty position and JS hacks to place stuff, I strongly recommend you to take 1-2 hours and read this incredibly useful guide for CSS-Grid:
https://css-tricks.com/snippets/...
and this one for Flex:
https://css-tricks.com/snippets/...
These two links have saved me PLENTY of hours struggling with all kinds of responsiveness and placement/sizing issues.1 -
A little background on project fubar:
Project fubar was started a couple of years ago, by an entirely different set of devs, against an entirely different set of requirements which were never made transparent to this day, on a new platform and framework.
That means it had APIs either outdated or deprecated, front-end logic that did things it wasn't supposed to be doing and lots of scope creep and technical debt.
I had to support and fix fubar for the last few months to prime it for UAT. It was the equivalent of plugging leaks which created more leaks.
Finally, I couldn't take it and asked for a week off. I timed it so it would be right after what would have been the final UAT deployment and I'd be back after they completed their test rounds, so I could fix any new or returning defects.
Today I just found out that fubar got put on hold, that UAT was a failure and all fubar-related work had to stop. I have some mixed feelings on this: I worked hard to get fubar working as business wanted, and I was proud of that. But I also didn't like that fubar was constantly changing in scope and function.
I wonder if anyone else has ever felt the same thing?2 -
My "dev specialty" when I first started was Flash and ActionScript. I just wanted to make funny games and shitpost animations on Newgrounds.
Eventually I got steered into building basic websites. Those were the Dreamweaver MX days. JavaScript + jQuery were all the rage.
Then I got a job building SharePoint modules, got exposed to legitimate programming languages like C# and learned more about enterprise software architecture, design patterns, yadda yadda. I started hanging out more with the front-end guys, who taught me SASS and SMACSS and all that jazz.
Eventual jobs kept leaning me towards front-end, so I guess that's the hole I find myself in lately. Sometimes I get a sprinkle of devops, some infrastructure stuff, maybe a little solution design here and there.
Now I maintain shitpost enterprise applications built by other devs who like spaghetti and meatballs. At least I put in funny ASCII art for strings in my unit tests. -
I find it hilarious that I am one of 2 people at my company of 60+ people that really knows front end development. Like, how have you guys made it this far without full stack devs?2
-
There has been a post today about the existence of too many js frameworks. Which reminds me of this awesome post https://hackernoon.com/how-it-feels...
At first I thought someone was corpseposting, as it is my understanding that the js ecosystem is calming down a bit. But then I noticed that post got almost 20 upvotes. So here's my thoughts:
(I'm not sure what I'm ranting about here, as it feels kinda broad after writing it. I think it's kinda valid anyhow.)
I'm ok with someone expressing frustration with js. But complaining about progress is definitely off to me.
How is too many frameworks a bad thing?
How does the variety and creation of more modern frameworks affect negatively developers?
Does it make it hard to understand each of these new frameworks?
Well, there's no need to. Just because it has a logo and some nice badges and says it will make you happy doesn't mean you should use it.
You just stick to the big boys in the ecosystem and you'll be fine for a while.
Does it make you feel compelled to migrate the stack of every project you did?
Well, don't. If you don't like being on the bleeding edge of js, then just stick to whatever you're using, as long as it's good code.
But if a lot of companies decided to migrate to react (among others frameworks), it's because they like the upsides: the code is faster to write, easier to test and more performant.
In general, I'm more understanding/empathic with beginner js programmers.
But I have for real heard experienced devs in real life complain about having to learn new frameworks, like they hate it.
"I just want to learn a single framework and just master it throughout my life" and I think they're lowering the bar.
There's people that for real expect occupying positions for life, make money, but never learn a new framework.
We hold other practitioners to high standards (like pilots or doctors), but for some reason, some programmers feel like they're ok with what they know for life.
As if they couldn't translate all they learned with one framework to another.
Meanwhile our lives are becoming more and more intertwined with technology and demand some pretty high standards. Standards that historically have not been met, according to thousands of people screaming to their devices screens.
Even though I think the "js can be frustrating" sentiment is valid, the statement 'too many js frameworks is bad' is not.
I think a statement like 'js frameworks can go obsolete very quickly' is more appropriate.
By saying too many js frameworks is a bad thing you're
1) Making a conspiracy theory as if js devs were working in tandem to make the ecosystem hard,
But people do whatever they want. Some create packages, others star/clone/use them.
2) Making a taboo out of a normal itch, creating.
"hey you're a libdev? just stop, ok? stop"
"Are you a creative person? Do you know a way to solve a problem in an easier way than some famous package? it doesn't matter, don't you dare creating a new package."
I'm not gonna say the js world is perfect. The js world is frantic, savage, evolves aggressively.
You could say that it (accidentally) gives the middle finger to end users, but you could also say that it just sets the bar higher.
I liked writing jquery code in the past, but at the same time I didn't like adding features/fixing bugs on it. It was painful.
So I'm fine with a better framework coming along after a few years and stealing their userbase, as it happens almost universally in the programming world, the difference with js is that the cycle is faster.
Even jquery's creator embraced React.
This post explains also
https://medium.com/@chrisdaviesgeek...13 -
So I work for an IT consulting firm (web development) and was hired by a customer 7 months ago for coaching Git, implementation of VueJS on the front-end and fostering teamwork with devs who'd been in their solo comfort zone for the last 15 years.
I asked for confirmation multiple times on whether they were sure they wanted to go through with a bigger investment in front-end. Confirm they did, multiple times.
After half the team's initial enthusiasm faded (after 1 month), the 'senior' of them who's worked there for 18 years on a single -in the end, failed- project got a burn-out after half a week of showing up (without doing actual work) from the stress, and started whining about it with management that has no technical clue whatsoever. This and other petty office politics lead to the dumbest organizational and technical decisions I've seen in my short 5-year career (splitting a Laravel app that uses the same database in two, replacing docker container deployment with manual ssh'ing and symlinking, duplicating all the models, controllers, splitting a team in two, decreasing productivity, replacing project management dashboards with ad-hoc mail instructions and direct requests).
Out of curiosity I did a git log --author --no-merges with the senior's name on the 2 projects he was supposed to help on, and that turned up... ZERO commits. Now the dept. hired 3 new developers with no prior experience, and it's sad to see the seniors teach them "copy paste" as the developer's main reflex.
Through these 7 months I had to endure increasingly vicious sneers from the IT architect -in name only- who gets offended and hysterical at every person who dares offer suggestions. Her not-so-implicit insinuation is that it's all my fault because I implemented Vue front-end (as they requested), she has been doing this for months, every meeting at least once (and she makes sure other attendees notice). Extra background: She's already had 2 official complaints for verbal abuse in the past, and she just stressed another good developer into smoking again.
Now I present her my timesheet for January, she abuses her power by refusing to sign it unless I remove a day of work.
Earlier this week I asked her politely to please stop her unjust guilt-tripping to which she shouted "You'll just have to cope with that!", and I walked out of the room calmly (in order to avoid losing my nerves). She does this purely as a statement, and I know she does it out of bad faith (she doesn't actually care, as she doesn't manage the budgets). She knows she wields more power over me than the internal devs (I am consultant, so negative reviews for me could delay further salary raises).
I just don't know how to handle this person: I can't get a word in with her, or she starts shouting, and it's impossible to change her (completely inaccurate technological) perception.3 -
Today one of the more junior back-end devs told us, that he doesn’t plan to do front-end, because he doesn’t want to make design.
He basically told us that in his view FE devs do design work and that’s it.
What the f**? We have designers for that. Front-end devs are not the ones who make design. Reaaad uupp, boy6 -
Fuuuuuuuuuuccccccckk you gulp, you have one fucking job. Front-end web Devs this is a warning for all of you out there. Go with webpack always.5
-
Seeing devs having only a hammer in their hand is making me sad. At least don't talk bullshit about things you don't understand or haven't tried... Most of the front end devs at my company are like that.2
-
Having a complete front end and back end application where the frontend is designed to look as simple as possible.
A new potential customer wants to have our app and listens to a designer bragging that its just replacing 2 fields.
After a while our manager comes by and mentioned that everything needs to be done within a few weeks....
All devs lose their mind since in the backend we need to have like 8 external sources to connect and hundreds of business rules to implement.
How a single designer ruined the year for 7 devs....1 -
Anyone know small-medium companies hiring front end devs around the eu?
Or any recruiters with a soul?
React btw. Thanks.
Why yes. This is a last resort. Thanks for noticing/criticizing6 -
Just got an internship a few days ago. The manager threw a project at me. I have to do it alone. It's a user-system (registration, login etc.) The front-end is ready. And I have to build its back-end in PHP. I started to draw the project on paper (pseudocode) and then asked a few questions about design patterns to jump into coding. They recommended me Laravel. I'm good at PHP (procedural) and have done some basic OOP. I've actually built a few projects in Python using OOP. But I've never used any framework (yeah, I know). So I started to learn Laravel and realized that it's very different than normal PHP (procedural or even normal OOP). I almost don't write any normal PHP code. This makes me confused. But I have to learn it fast and well, and finish the project to hit the deadline and get the full-time job. I'm desperately looking for any kind of help to learn Laravel more effectively! I've googled and got some recommendations. But I need more live help from devs directly.5
-
I don’t know why/how, but some guy in my team put the node_modules folder on GitHub.
This person ran *npx create-react-app* and for whatever reason probably DELETED the .gitignore.
I had to fix it of course, and in the meanwhile I forgot to switch branches before changing everything, making git crash because switching branches with +4 million lines of code deleted was too much.
Why don't they let experienced front-end devs initialize projects? I don’t understand.8 -
We were building a website using angular 1. We were collaborating with some devs from outside our firm. At some point one of the devs(which was supposed to be a front end expert) had the brilliant idea to migrate to a never version of angular. He made the changes and fucked up all the controllers and functionalities and then he just disappeared. My team worked for 2 weeks to fix his mess.
Dude do you even know the definition of refactoring? 😤4 -
So here's a question for all the front-end web devs. I'm mostly a back-end dev, but currently learning Angular 6 for a personal project I'm doing.
Didn't realize that styling isn't what Angular does (or maybe it does, and I just don't know), but that you should use some framework for styling too.
So the question is: What is most commonly used, is it bootstrap or something like that?4 -
Started a new role as a front end developer working with React, happy that i finaly won't have to work with wordpress anymore, having a great hope that I will learn from the best with my team, and then ... COVID-19 ... I have to work from home
first task, implement a feature on a react front end build with react boilerplate, first time seeing this repo and dispair quickly took over, there is no documentation except for clone and install, the code is a mess, the console is filled with errors and warnings ...
I did what I could, but it was not enought, my n+1 didn't complain but if I was him i'd fire my ass with no regret, now I understood why almost all my collegues are working as a backend devs.
I don't fear being fired, I fear the feeling of being not good, feeling useless, each morning I stare at the code and I become illiterate, I can't even touch a keyboard, now I don't know what to do, fixing this shitty app, trying to build something with react boilerplate and try to understand how the data flow, or continue my endless tutorial hell .1 -
Note to devs here. Please don't choose a framework for the hype at your work. Use it on your own time or company hackaton/learning time.
I'm looking at you angular.
Production ready doesn't mean sanity ready.
Now because some dev choose such technology for arbitrary reasons. (hype, latest acronym on CV). I spend more time debugging and understanding than I would if some simpler technology was chosen. Look at all the options then choose the simplest one that has and seems to have active maintenance. Zen of python is the best thing to happen in programming and I think everyone, even if you don't like Python should follow it. Save you and your colleagues brain time and ask for advice.
Also IMO react is probably third or second best option, higher if one requirement is to be react native. Angular is even lower because it's complexity is unforgivable when a dev has not enough front-end experience.8 -
Question - my field is information security (or cyber security if you want to think of me as a time lord), but I wanted to know;
Front end and back Devs, how much time do you spend on security issues and/or implementing security measures?10 -
Hi all my webdev friends! Question for you, tried google, got propaganda.
Why do front end devs use frameworks like angular or react? I was looking into it, and it looks like html/JavaScript can handle it all. Wouldn't removing them save load time and data overhead? Does it really boost productivity that much?
As a backend dev, it is completely possible I missed something haha.5 -
!rant
I'm a designer and just found out about a hackathon by Deutsche Bank hosted at the end of October in Berlin. Are some devs out there interested in forming a team (and brainstorming about an idea, obviously)? Preferably from around Germany, since one has to pay travel costs on his/her own, but I'm open, really.
More information: https://api-open.db.com
Just hit me up if you're interested!
P.S. I'm not bad at getting some front-end development done...8 -
#!/bin/rant
I have two jobs, one is developing a web site with a CMS and the other one is the back-end of a web platform. I like both, but the first one is on front-end phase, which I hate, and I closed all the pending tickets on the second one. So I don't want to work on the first one but I have to because of the due date, and tomorrow I leave on vacations which means side projects,
Please fellow devs and ranters what should I do? (Quitting is not an option)1 -
If html and css are not really considered as programming languages, then how do we call the job? I've 'coded' the design? I've front-end designed the design? I've 'sliced' the design? (last one is sure old fashioned enough to exist..)
p.s. and while front-end devs nowadays are required to have angular, react, etc as their skillset, I feel like html and css are also shifting to be required for designers..1 -
I have started a freelance full-stack project with some existing code-base and it was horrible. They only have API endpoints for fetching whole data. No limit, No sort, No filter. They are doing all this shit on the front end. They are even aggregating data on the front end. Seriously who the fuck does that? On top of that the guy who has coded it was a senior developer. I am wondering now, did he write that kind of code purposefully or this kind of shitty devs actually exists?2
-
Full stack and front end devs: how much CSS are you expected to know? I love front end development, but I hate fighting with CSS.3
-
- Document the current architecture & code for new hires as well as existing people to get a grip on the logic (not everyone understands it)
- Figure out what MLOps is
- Build at least one front-end application to understand the hardships of UI devs -
Why employers strongly believe Front-End and Back-End are synonyms of Full-Stack?
They are requiring Front devs to have knowledge and experience with relational databases and Back devs to be experts in HTML and CSS, sometimes graphic design stuff too.
For God's sake just hire a Full-stack Dev3 -
Job Interview Help!
Hi Devs! Applying for a junior front end developer job here and have been called by a recruiter. He's explained he will:
"be asking some technical questions, so it might be worth a quick bit of revision on your JavaScript knowledge and terms!"
Has anyone come across these before and what level of knowledge would I be expected to know for a junior role?
I'm going to do the test either way as it'll be great experience but a bit of prep is always good! -
I just found out that Front end developers believe Backend development is so easy anyone can do it.....that is why there are many frontend devs and so small backdevs 🤓🤓🤓🤓5
-
I'm working at a startup and one of the founders asked the accountant to prepare a presentation for the company's financial state. This was back for the first trimester of 2023. It said that we are losing money but not to worry because x,y,z (believable reasons).
I had yesterday a lunch conversation with the office (except the founders) and the accountant said that we are bleeding quite a lot of money each month and the company is not looking healthy.
My boss (previously CTO, has stepped down) also left the company for unrelated reasons (mainly the childish behaviour of the CEO, increased stress, devs being fired for no good (humane) reasons, stupid decisions, devs leaving and the projects going to shit due to unrealistic deadlines by new COO) .
So does anyone has any advice for job hopping for a junior front-end dev that wants to do more back-end development in the next company :)?2 -
Wondering why the heck isn't there a common Webpack config around for the front-end devs! Such a pain to configure that from scratch 😡2
-
Fellow Devs,
I don't know what I'm doing wrong. I am at a loss. I have applied to several Front-End jobs, both local, and remote. I have personal projects on my portfolio, and I offer to do "homework," that's been assigned while applying for a job. I am currently learning Python, but I don't have a project up with that.
Any suggestions?16 -
Is there such a thing as natural talent for specific categories of developers?
I've seen this occur a few times. I have more affinity for front-end development or separately, for UX, so I naturally see wireframes, I naturally know what looks good or not to a user, and I can relate to a user.
I've seen multiple backend devs who share the same complaint that they don't have a knack for front-end and that they hate front-end. They can create beautiful architectures and solve complex problems, but they tell me: "Don't ask me to tell you what looks like a good layout or not because I have no idea".
The same thing happens to me when it comes to back-end (even though I'm a Fullstack developer): Don't try to give me extremely complex problems because I will likely get very stuck, but ask me if a design would look good, ask me to design a website UX wise and I will do well without a great deal of effort.
I wonder why I have a hard time with back-end and others vice versa. Maybe we're trained more in certain areas or our brains function differently.
And so.. I wonder if more people see this happen in their workplace and if this observation holds true.3 -
I've been working on this personal project for awhile, I showed some screenshots, then I showed some updates (which I promptly deleted cause it was plain ugly). A website aimed at the "not-so-seasoned" devs, and I've been at a creative plateau for about 3 days now. I try to do some front-end, when I like what I see, I take care of the corresponding server-side logic, but for some reason, I'm having "Developer's block" (is that even a thing?).
Every second that goes by I try to do something else none code related, but I can't shake thinking about the project, but once I switch back to it, fuckin crickets.
I'm not asking a question this time (for once lol), just a mini dev's block rant. -
(!rant && question)
For the front-end devs out there, do you guys prefer using font-weight to change the weight of the font or do you guys prefer using separate names (Font Name Black, Font Name Bold, and so on)2 -
Question for the frontend devs:
When you build the front end of the website, do you keep PageSpeed Insights or Lighthouse analytics in mind,
or is it more of a "I'll deal with that later" kinda deal?
Little backstory to this - Our management wants these analytics to be close to 100% and one of the metrics is Largest Contentful Paint which is 3.2 secs, and I have no idea what that is.12 -
!Rant
Any tips for eye soreness? I don't feel it when I am working in front of the computer but it gets sore at the end of the day and few minutes in the morning the day after.I typically see the screen for around 9 hours.
Is this common? How do you devs overcome this? How do you devs protect your eyes? I'd like to get any tips from you people.
Thanks5 -
Finally have my DCOS cluster running! On paper this should be amazing. But I have now figured out that the front end Devs have about 400 uncommitted HTML templates, which means I cannot proceed with out severe chaos! I spend so much time creating an awesome data centre, only to be thwarted by other peoples laziness!
4 -
All you front end devs who work with dedicated design teams, what's you usual workflow? Do the designers pass on the UI kit with all the assets and dimensions and you clone the thing using whatever stack you're using or do you all decide the specs on the fly looking at the general visual structure of the design?5
-
Xamarin vs Flutter
I already know c# but I’m thinking it’s better to learn Dart + Flutter than carry on with Xamarin (only ever worked on the back end parts of Xamarin so not familiar with the layout syntax and the ui side of it).
Xamarin seems to be so clunky (to be fair more the dev environment than the end result), even on a powerful machine it’s a pig to work on.
Our project uses Xamarin forms, without any extra MVVM framework such as Prism and it just seems a bit shit from what front end code I’ve seen (could be the devs).
So given that I’m not sure that holding out for MAUI and expecting it to be a silver bullet is a good idea.
Is the UI code for Flutter any cleaner?
Is the dev environment more reliable?
Or is another option better, such as ReactNative or Ionic ?
(Particularly if one of those would let you develop an iOS version without access to a Mac)2 -
Check out this holiday rant/poem from a Front-end developer and colleague:
“Twas a Dev’s Christmas: A Holiday Ode to the Open Source Community” by @warlyware https://levelup.gitconnected.com/tw... -
Hello fellow devs. I wanna create a survey site, which will contain 3 surveys within. All 3 surveys, will contain around 50 questions, and will have a range of input options. The site will collect the data from a form, store it and probably live visualize them with a plot-like library .
I was thinking about using React for the front-end, Firebase for the back-end + Google-Sheets and one of the many react-libraries for plotting.
Do you think that this stack is appropriate for that kind of app ? I am a bit concerned about firebase's querying system or the scalability of the app. (Since it will hold a lot of questions and answers )
( It's survey for developers, so I hope in the future you will participate in it :D ). -
So, this backend dev, thinks because I am doing frontend work I have no knowledge on backend stuff.
I ask him for a backend feature to match my front end feature. He says that that will take about 4 weeks and therefore cannot be included in this scope. I ask why because its something really easy. He says he'd have explained but I cannot get it.
So I ask him why they have their tables structured that way (I went in and checked ). I then went ahead and schooled the guy on SQL, normalizing databases and other stuff.
Put some respect on frontend devs. some of us are fullstack
Top Tags
Weekly Rant
View