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???

I'm drunk and I'll probably regret this, but here's a drunken rank of things I've learned as an engineer for the past 10 years.

The best way I've advanced my career is by changing companies.

Technology stacks don't really matter because there are like 15 basic patterns of software engineering in my field that apply. I work in data so it's not going to be the same as webdev or embedded. But all fields have about 10-20 core principles and the tech stack is just trying to make those things easier, so don't fret overit.

There's a reason why people recommend job hunting. If I'm unsatisfied at a job, it's probably time to move on.

I've made some good, lifelong friends at companies I've worked with. I don't need to make that a requirement of every place I work. I've been perfectly happy working at places where I didn't form friendships with my coworkers and I've been unhappy at places where I made some great friends.

I've learned to be honest with my manager. Not too honest, but honest enough where I can be authentic at work. What's the worse that can happen? He fire me? I'll just pick up a new job in 2 weeks.

If I'm awaken at 2am from being on-call for more than once per quarter, then something is seriously wrong and I will either fix it or quit.

pour another glass

Qualities of a good manager share a lot of qualities of a good engineer.

When I first started, I was enamored with technology and programming and computer science. I'm over it.

Good code is code that can be understood by a junior engineer. Great code can be understood by a first year CS freshman. The best code is no code at all.

The most underrated skill to learn as an engineer is how to document. Fuck, someone please teach me how to write good documentation. Seriously, if there's any recommendations, I'd seriously pay for a course (like probably a lot of money, maybe 1k for a course if it guaranteed that I could write good docs.)

Related to above, writing good proposals for changes is a great skill.

Almost every holy war out there (vim vs emacs, mac vs linux, whatever) doesn't matter... except one. See below.

The older I get, the more I appreciate dynamic languages. Fuck, I said it. Fight me.

If I ever find myself thinking I'm the smartest person in the room, it's time to leave.

I don't know why full stack webdevs are paid so poorly. No really, they should be paid like half a mil a year just base salary. Fuck they have to understand both front end AND back end AND how different browsers work AND networking AND databases AND caching AND differences between web and mobile AND omg what the fuck there's another framework out there that companies want to use? Seriously, why are webdevs paid so little.

We should hire more interns, they're awesome. Those energetic little fucks with their ideas. Even better when they can question or criticize something. I love interns.

sip

Don't meet your heroes. I paid 5k to take a course by one of my heroes. He's a brilliant man, but at the end of it I realized that he's making it up as he goes along like the rest of us.

Tech stack matters. OK I just said tech stack doesn't matter, but hear me out. If you hear Python dev vs C++ dev, you think very different things, right? That's because certain tools are really good at certain jobs. If you're not sure what you want to do, just do Java. It's a shitty programming language that's good at almost everything.

The greatest programming language ever is lisp. I should learn lisp.

For beginners, the most lucrative programming language to learn is SQL. Fuck all other languages. If you know SQL and nothing else, you can make bank. Payroll specialtist? Maybe 50k. Payroll specialist who knows SQL? 90k. Average joe with organizational skills at big corp? $40k. Average joe with organization skills AND sql? Call yourself a PM and earn $150k.

Tests are important but TDD is a damn cult.

Cushy government jobs are not what they are cracked up to be, at least for early to mid-career engineers. Sure, $120k + bennies + pension sound great, but you'll be selling your soul to work on esoteric proprietary technology. Much respect to government workers but seriously there's a reason why the median age for engineers at those places is 50+. Advice does not apply to government contractors.

Third party recruiters are leeches. However, if you find a good one, seriously develop a good relationship with them. They can help bootstrap your career. How do you know if you have a good one? If they've been a third party recruiter for more than 3 years, they're probably bad. The good ones typically become recruiters are large companies.

Options are worthless or can make you a millionaire. They're probably worthless unless the headcount of engineering is more than 100. Then maybe they are worth something within this decade.

Work from home is the tits. But lack of whiteboarding sucks.

I told these people that this issue would happen. Did they listen? Nooo

It'll be fine, they say. We likely won't be having that much data returned to the front end, they say.

Day of the install. Web Application attempts to query 68,000 rows of data straight into the web page.

*Surprised Pikachu face* when they are consistently getting crashed browser tabs.

And now everything gets pushed back and we're behind by an entire month because they didn't heed my warnings.

Oh, and now I have to pick up after them, and do some stupid work arounds that will likely be defunct in a month or two. 🙄

Week 278: Most rage-inducing work experience — I’ve got a list saved! At least from the current circle of hell. I might post a few more under this tag later…

TicketA: Do this in locations a-e.
TicketB: Do this in locations e-h.
TicketC: Do this in locations i-k.
Root: There’s actually a-x, but okay. They’re all done.
Product: You didn’t address location e in ticket B! We can’t trust you to do your tickets right. Did you even test this?
Root: Did you check TicketA? It’s in TicketA.
Product guy: It was called out in TicketB! How did you miss it?!
Product guy: (Refuses to respond or speak to me, quite literally ever again.)
Product guy to everyone in private: Don’t trust Root. Don’t give her any tickets.
Product manager to boss: Root doesn’t complete her tickets! We can’t trust her. Don’t give her our tickets.
Product manager to TC: We can’t trust Root. Don’t give her our tickets.
TC: Nobody can trust you! Not even the execs! You need to rebuild your reputation.

Root: Asks coworker a simple question.
Root: Asks again.
Root: nudges them.
Root: Asks again.
Coworker: I’ll respond before tomorrow. (And doesn’t.)
Root: Asks again.
Root: Fine. I’ll figure it out in my own.
TC: Stop making it sound like you don’t have any support from the team!

Root: Asks four people about <feature> they all built.
Everyone: idk
Root: Okay, I’ll figure it out on my own.
TC: Stop making it sound like you don’t have any support from the team!

Root: Mentions multiple meetings to discuss ticket with <Person>.
TC: You called <Person> stupid and useless in front of the whole team! Go apologize!

Root: Tells TC something. Asks a simple question.
Root: Tells TC the same thing. Asks again.
TC: (No response for days.)
TC: Tells me the exact same thing publicly like it’s a revelation and I’m stupid for not knowing.
TC: You don’t communicate well!

Root: Asks who the end user of my ticket is.
Root: Asks Boss.
Root: Asks TC.
Root: Fine, I’ll build it for both.
Root: Asks again in PR.
TC: Derides; doesn’t answer.
Root: Asks again, clearly, with explanation.
TC: Copypastes the derision, still doesn’t answer.
Root: Asks boss.
Boss: Doesn’t answer.
Boss: You need to work on your communication skills.

Root: Mentions asking question about blocker to <Person> and not hearing back. Mentions following up later.
<Person>: Gets offended. Refuses to respond for weeks thereafter.

Root: Hey boss, there’s a ticket for a minor prod issue. Is that higher priority than my current ticket?
Root: Hey, should I switch tickets?
Root: Hey?
Root: … Okay, I’ll just keep on my current one.
Boss: You need to work on your priorities.

Everyone: (Endless circlejerking and drama and tattling)

Most of the tech YouTubers are really noob engineers.

Joma was a data scientist. He is an L3 engineer at Google and he hasn't done much during the last 1 year based on his internal stats.

I saw tech leads stats while he was at Google and that dude did nothing during his time. I'm sure he was an IC before he became a lead.

Clement talks about system design bull shit but he's a math major who worked on some angular front end while he was at Google. Basically his experience in tech is mostly involving using mat-button and mat-input. He also quit FB in a month.

Listening to tech lead gives me cancer. That guy was also some front end/ mobile engineer. I don't think any less of mobile engineers but tech leads acts as if he built some large scale systems at Google and FB. His opinion about react native shows how much of a noob he is. He also talked about docker in one of his video which showed he had some fundamental misunderstanding of what docker is. In his courses, he struggles to explain simple algorithms.

I don't know how these people have the courage to claim themselves as some sort of experts in the field when they are extreme noobs. They also sell some shady courses and are robbing innocent college kids.

One thing they all do well is talk. Which I give them 10/10.

It's crazy to me how much of a misguided superiority complex some CS college kids have.

"I'd never learn Python, that's just for kids"

"Front end is so easy, it's just HTML and making things look pretty"

The education system is a fucking joke. How do you get through all the required courses and get to the capstone course where your one goal is to build a simple prototype of a project(like a simple website) for a real world client and not know HTML or CSS when you spent a whole fuckboy semester on a class dedicated to HTML, css, JavaScript and the teacher gave you the PHP. Not only that but you can't even figure out how to use a simple google search to look up the documentation on any of these topics or even the easy to follow tutorials littering the internet on how to use Bootstrap which is what we're fucking using to make it faster to develop the core logic of our app but all you fucking want to do is take shortcuts and create a PowerPoint presentation in google slides and make an easy project look like shit and make me and yourselves look like shit. But don't fucking worry, I'll code the whole thing in a fucking night because you didn't do your part of taking care of just the front end and planned for your incompetence and lack of questions or help. I know you're busy looking for a job for after you graduate but you can't even answer a simple programming question. Let me give you the solution on how to reverse a string, cuz you don't remember c# but it literally takes 30 seconds to google the solution that is everywhere. My project team is why no one takes a degree from this university seriously.

I've seen several rants about dumb/useless teachers, college and the CS degree studies; today is a good day to vent out some "old" memories.

Around two semesters ago I enrolled in a Database seminar with this guy, a tall geek from the 80's with a squeaky voice, so squeaky mice could had an aneurysm if they listened to him.

Either way this guy was a mess, he said he was an awesome coder, that we were still "peasants" when it came to coding, that relational databases had nothing on him since he was an awesome freelancer and did databases every day, that we had to redo the programming course with him and with his shitty, pulled out of the ass own C++ style guide with over 64 different redacted rules.

He gave us sample code of "how it should be done" in Java...it ain't my favorite language but fuck me a fucking donkey could have written better code with his ass!! He even rewrote Java's standard input function and made it highly inefficient. He still wrote in a structural paradigm in OOP languages! And he dared to make this code reviews were he would proyect someone's code and mock it in front of the class as he took off points, sometimes going to the negative realm (3,2,1,0,-1...)

But you know what's shittier? That he actually didn't even attend, 90% of the time, it was literally this:
> Good morning class
> Checks attendance. . .
> I'll be back, I'm going to check in...
> 1 hour 45 minutes later (class was 2 hrs long) - comes back
> do you have any doubts?
> O.o no...? I'm ok.
> We're done

Not only that, he scheduled from 4 to 17 homeworks throughout the week, I did the math, that was around 354 files from everyone; of course he didn't check them, other students from higher semesters did and they gained each point taken from students making students from lower semesters get the short end of the stick.

How did I pass? He didn't understood my code or database schema and he knew he couldn't fail me as he had no ground to stand on.

Thanks for listening, if you got to the end of this long ass post and had a similar experience I'd love to read it.

Every day I feel like Dr. Leonard McCoy.

"I'm an automation expert, not a ..."

* DBA
* ElasticSearch administrator
* Kafka Architect
* Email marketing specialist
* SEO Analyst
* Front end developer
* Doctor
* Project manager
* Accountant

New HOE came. He “streamlined” the processes and “standardised” the policies. And in turn.. fucked up the whole startup feel of my company.

I saw it happening right in front of my eyes in a matter of only few months.

Earlier, things were flexible, work was fun, people were even ready to put in more hours because we were all having fun. Now, work feels like work, fun is gone, frustration has become normal, and the most frustrating part is that.. WFH is now a “privilege”.

Fuck this shit man! That fucker exhausted the whole company in just a few months. Given enough time, he will be the end of this company.

Frequently used answers :)

UI developer - I think API is not working
Backend developer - Front end is not sending the request correctly
Tester - Testing! Testing!
UI/UX - As per android/ios standards...
QA - Let me check one more time
PM - Let us have another meeting and get on the same page
Dev-Ops - It's very complicated you know
CTO - We're working on a next-gen solution
Founder - Let us build something that no one has built, something similar to what google...facebook...

Cridits: My EX-CPO

If nobody hates you, you're doing something wrong ~ House MD

Tl;Dr : I'm pissing the right people off and my God I like it

That's what I've known and have confirmed doing my current side project with my gf, we are working on a ratemyprofessors clone with extra spicy features, one in particular is so spicy some teachers will be put in a position in which they would rather grind hot peppers with their butt cheeks.

Don't get me wrong, there are good teachers (some of which actually showed support) but some are not good teachers and some aren't good people either; I've decided it's time to stop complaining and take action.

We recently released an alpha and I presented it to a teacher I had this semester (one of the "not so great" kind) as a DB proyect cuz fuck it I'm not doing 2 projects.

This teacher is your run of the mill "I'm lazy and I don't care" teacher and she ran the classroom like a shitty kindergarten, so much so, one of the teams was presenting a buggy admin site as their project and she started talking on the phone! Right up on their faces!!

My turn, I go up and handle her a 30 page printed thesis of my project and said that unlike my mates, I was going to start presenting the idea and then the actual software...why is it printed?, She said; Because I won't be projecting the PDF ma'am, I actually made a professional presentation and that way you can read more technical details while I give a broad overview...

I started talking about the huge issues students face and my research about it, undisciplined teachers, no class structure ~ abrupt interruption ~ "yeah I know like, you are giving so much statistics and numbahs but where is the database?"

I got pissed off because the whole purpose of printing and giving her the docs was for her to ask specific questions AT THE END! So I told her I was getting there and to ask questions at the end...I start showing off the system's sweetest features... everyone got quiet...a girl on the front row kept looking at the teacher and then back to the board with her eyes wide open, the teacher was visibly upset.

I asked someone to please help me by using the site being projected for everyone to see, he searched the teacher's name and it obviously popped up cuz I scrapped the whole teacher index site... some people gasp and others start murmuring.

She freaked and started arguing saying that frontend can't be just HTML and CSS, where did you mentioned x and y feature? admit it's just teacher evaluations! where did you get the teacher names? I want the scripts!....it went on even 10 minutes after class and the next class with a police like interrogation.

So yeah, something tells me I'm not getting an A, but I'm happy after all because that's the kind of reaction I want from those types of professors.

Worth it 😎

Client project manager calls me up one day

PM: hey can you make some precise estimates on some items for a project you’re not working on? It should be easy. It’s very similar to the project you ARE working on and it’s only a handful of user stories, mostly front end stuff. We´ll need this to be done by tomorrow night.

Me: um, I guess if it’s just a few simple items. ok

PM: great! I’ll let you know when you get access to the backlog.

Me: sounds good

Link to project is sent to me. Backlog contains over 20 user stories, most of which are backend related. And it doesn’t have much to do with my current project.

I contact PM: this isn’t exactly what you announced when I had you on the phone. If you want precise estimates with a minimum of design, this could take up to a week. I could however proceed to some ballpark estimates (poker planning) for starters if you need this quickly for your roadmap.

PM: no I need PRECISE estimates down to the hour for each item.

Me: ok then, it’ll take up to a week.

PM: 🤬🤬🤬. You told me it could be done in a day. I’m coming to realize your word can’t really be trusted.

Me: 🤦🏻‍♂️

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.

Me: “here’s a demo of the backend functionality you requested. We’ve got more work to do to make this production ready. Let me know your thoughts or if we need to make any changes, otherwise I’ll hand this off to the UX team, we’ll be ready to go live next month after other they deliver the front end”

PM: *telling stakeholders* “The new thing is done and ready for go live”

Me: *privately to PM* “who told you that the thing was ready for go live?”

PM: “You did”

Me: “I suggest you go read what I wrote a little more closely”

Static HTML pages are better than "web apps".

Static HTML pages are more lightweight and destroy "web apps" in performance, and also have superior compatibility. I see pretty much no benefit in a "web app" over a static HTML page. "Web apps" appear like an overhyped trend that is empty inside.

During my web browsing experience, static HTML pages have consistently loaded faster and more reliably, since the browser is immediately served with content useful for consumption, whereas on JavaScript-based web "apps", the useful content comes in **last**, after the browser has worked its way through a pile of script.

For example, an average-sized Wikipedia article (30 KB wikitext) appears on screen in roughly two seconds, since MediaWiki uses static HTML. Everipedia, in comparison, is a ReactJS app. Guess how long that one needs. Upwards of three times as long!

Making a page JavaScript-based also makes it fragile. If an exception occurs in the JavaScript, the user might end up with a blank page or an endless splash screen, whereas static HTML-based pages still show useful content.

The legacy (2014-2020) HTML-based Twitter.com loaded a user profile in under four seconds. The new react-based web app not only takes twice as long, but sometimes fails to load at all, showing the error "Oops something went wrong! But don't fret – it's not your fault." to be displayed. This could not happen on a static HTML page.

The new JavaScript-based "polymer" YouTube front end that is default since August 2017 also loads slower. While the earlier HTML-based one was already playing the video, the new one has just reached its oh-so-fancy skeleton screen.

It would once have been unthinkable to have a website that does not work at all without JavaScript, but now, pretty much all popular social media sites are JavaScript-dependent. The last time one could view Twitter without JavaScript and tweet from devices with non-sophisticated browsers like Nintendo 3DS was December 2020, when they got rid of the lightweight "M2" mobile website.

Sometimes, web developers break a site in older browser versions by using a JavaScript feature that they do not support, or using a dependency (like Plyr.js) that breaks the site. Static HTML is immune against this failure.

Static HTML pages also let users maximize speed and battery life by deactivating JavaScript. This obviously will disable more sophisticated site features, but the core part, the text, is ready for consumption.

Not to mention, single-page sites and fancy animations can be implemented with JavaScript on top of static HTML, as GitHub.com and the 2018 Reddit redesign do, and Twitter's 2014-2020 desktop front end did.

From the beginning, JavaScript was intended as a tool to complement, not to replace HTML and CSS. It appears to me that the sole "benefit" of having a "web app" is that it appears slightly more "modern" and distinguished from classic web sites due to use of splash screens and lack of the browser's loading animation when navigating, while having oh-so-fancy loading animations and skeleton screens inside the website. Sorry, I prefer seeing content quickly over the app-like appearance of fancy loading screens.

Arguably, another supposed benefit of "web apps" is that there is no blank page when navigating between pages, but in pretty much all major browsers of the last five years, the last page observably remains on screen until the next navigated page is rendered sufficiently for viewing. This is also known as "paint holding".

On any site, whenever I am greeted with content, I feel pleased. Whenever I am greeted with a loading animation, splash screen, or skeleton screen, be it ever so fancy (e.g. fading in an out, moving gradient waves), I think "do they really believe they make me like their site more due to their fancy loading screens?! I am not here for the loading screens!".

To make a page dependent on JavaScript and sacrifice lots of performance for a slight visual benefit does not seem worthed it.

Quote:

> "Yeah, but I'm building a webapp, not a website" - I hear this a lot and it isn't an excuse. I challenge you to define the difference between a webapp and a website that isn't just a vague list of best practices that "apps" are for some reason allowed to disregard. Jeremy Keith makes this point brilliantly.
>
> For example, is Wikipedia an app? What about when I edit an article? What about when I search for an article?
>
> Whether you label your web page as a "site", "app", "microsite", whatever, it doesn't make it exempt from accessibility, performance, browser support and so on.
>
> If you need to excuse yourself from progressive enhancement, you need a better excuse.

– Jake Archibald, 2013

It's official, the "front end dev" doesn't know how to code.
Why.
And it's not a "Well I don't know JS because I use React." scenario, no. He has almost no idea of coding.
What was he thinking trying to build the front end of a very complex app with just HTML, CSS and stupid copied and pasted snippets?

This would be my first official post.

Been a IT Technician for a managed service provider for the past 9 years up until last year August. Managing director pulls me in with a movement to App Development after coming across some personal hobby projects I have done in the past.

Started in the new position in November as Junior Developer and workloads get dumped on me and left to figure it out. 4 weeks of running through code without documentation and the solutions started to make sense.

Started a new solution for a Large remote customer with documentation and timelines in December and I get pulled in again for a second time in front of the MD.

Good News:With effect in January I have been promoted to Head of Application development.

Bad News: The existing department head is leaving end of the month and I am to go 900km from home to hand over all responsibilities for the next 3 weeks.

Better News: Department has started shifting to DevOps and it is up to me to set the policies and work flows to how I see fit.

Worse news: it starts by expanding the team asap as 10 projects accounting to 4000 man hours with deadlines in Q3.

Wish me luck. It's going to be twisted Rollercoaster ride...

I absolutely love being micro managed by my team mates and QA. I also love being blamed for the other developers shitty code that breaks other crap in the front-end for when my tickets get checked by QA it's my code that becomes the problem. The part I love the most, is when I get slack messages "quick call" and the same thing gets explained to me by 3 different people.

So we've got a gif that doesn't show up in our React Native application. Of course, the designers assume it's me: "are you sure the gif is in the codebase? how are you using it in your component"? yeah ok boomer. I'm like, look at this other gif, works fine. "oh" So I tell them, double check the export options on how you are building the gif, maybe there is something there. so now they are asking ME for those export options. I'M A DEV, NOT A DESIGNER, DO YOUR JOB AND FIGURE IT OUT. I DON'T EVEN KNOW WHAT PROGRAM YOU ARE USING

oh as an aside, I was putting up a website for a client and they are like "my logo is quite similar to many others, is this something to worry about legally?" OH, SO NOW I'M A LAWYER TOO??!!?!? WHAT IS WRONG WITH YOU PEOPLE GOOGLE IS LITERALLY IN FRONT OF YOU

why do people continually think just because we can code we are fucking designers / lawyers / astronauts
/ god?
man this pisses me off - i think of that draw red lines with blue ink expert video, in the end, just smile and nod: "i can do... absolutely anything... trust me, I'm an expert"

Why was the front-end developer always calm?

Because he had a jQuery.

So, I've had a personal project going for a couple of years now. It's one of those "I think this could be the billion-dollar idea" things. But I suffer from the typical "it's not PERFECT, so let's start again!" mentality, and the "hmm, I'm not sure I like that technology choice, so let's start again!" mentality.

Or, at least, I DID until 3-4 months ago.

I made the decision that I was going to charge ahead with it even if I started having second thoughts along the way. But, at the same time, I made the decision that I was going to rely on as little external technology as possible. Simplicity was going to be the key guiding light and if I couldn't truly justify bringing a given technology into the mix, it'd stay out.

That means that when I built the front end, I would go with plain HTML/CSS/JS... you know, just like I did 20+ years ago... and when I built the back end, I'd minimize the libraries I used as much as possible (though I allowed myself a bit more flexibility on the back end because that seems to be where there's less issues generally). Similarly, any choice I made I wanted to have little to no additional tooling required.

So, given this is a webapp with a Node back-end, I had some decisions to make.

On the back end, I decided to go with Express. Previously, I had written all the server code myself from "first principles", so I effectively built my own version of Express in other words. And you know what? It worked fine! It wasn't particularly hard, the code wasn't especially bad, and it worked. So, I considered re-using that code from the previous iteration, but I ultimately decided that Express brings enough value - more specifically all the middleware available for it - to justify going with it. I also stuck with NeDB for my data storage needs since that was aces all along (though I did switch to nedb-promises instead of writing my own async/await wrapper around it as I had previously done).

What I DIDN'T do though is go with TypeScript. In previous versions, I had. And, hey, it worked fine. TS of course brings some value, but having to have a compile step in it goes against my "as little additional tooling as possible" mantra, and the value it brings I find to be dubious when there's just one developer. As it stands, my "tooling" amounts to a few very simple JS scripts run with NPM. It's very simple, and that was my big goal: simplicity.

On the front end, I of course had to choose a framework first. React is fine, Angular is horrid, Vue, Svelte, others are okay. But I didn't want to bother with any of that because I dislike the level of abstraction they bring. But I also didn't want to be building my own widget library. I've done that before and it takes a lot of time and effort to do it well. So, after looking at many different options, I settled on Webix. I'm a fan of that library because it has a JS-centric approach. There's no JSX-like intermediate format, no build step involved, it's just straight, simple JS, and it's powerful and looks pretty good. Perfect for my needs. For one specific capability I did allow myself to bring in AnimeJS and ThreeJS. That's it though, no other dependencies (well, at first, I was using Axios because it was comfortable, but I've since migrated to plain old fetch). And no Webpack, no bundling at all, in fact. I dynamically load resources, which effectively is code-splitting, and I have some NPM scripts to do minification for a production build, but otherwise the code that runs in the browser is what I actually wrote, unlike using a framework.

So, what's the point of this whole rant?

The point is that I've made more progress in these last few months than I did the previous several years, and the experience has been SO much better!

All the tools and dependencies we tend to use these days, by and large, I think get in the way. Oh, to be sure, they have their own benefits, I'm not denying that... but I'm not at all convinced those benefits outweighs the time lost configuring this tool or that, fixing breakages caused by dependency updates, dealing with obtuse errors spit out by code I didn't write, going from the code in the browser to the actual source code to get anywhere when debugging, parsing crappy documentation, and just generally having the project be so much more complex and difficult to reason about. It's cognitive overload.

I've been doing this professionaly for a LONG time, I've seen so many fads come and go. The one thing I think we've lost along the way is the idea that simplicity leads to the best outcomes, and simplicity doesn't automatically mean you write less code, doesn't mean you cede responsibility for various things to third parties. Those things aren't automatically bad, but they CAN be, and I think more than we realize. We get wrapped up in "what everyone else is doing", we don't stop to question the "best practices", we just blindly follow.

I'm done with that, and my project is better for it!

The company I work for now has no PM, no UI/UE. It’s just me, because I’m a full-stack engineer. I originally thought that full-stack was just front-end and back-end. I kind of want to run away.

javascript is garbage

typescript despite best intentions, regardless of how well it's executed, is still garbage as it's some sort of band aid on top of javascript, and javascript is garbage

Before you ask, yes I'm garbage at front end development

Why do front end developers like to write their HTML/Component markup like this:

<div
id="test"
class="test"
>
Test
</div>

That lone > bracket absolutely irks me! Looks ugly! I prefer the Android style:

<div
id="test"
class="test">

<span>Test</span>
</div>

👌clean

Half of my dev team has decided to leave. Back-end decreases with 75% and front-end team decreases with 20%.

This is the fourth time that half or more of the dev team has to be replaced in my companies existing (which is less than 10y).

/me joining a new front-end project with enforced prettier rules to complete the build pipeline.

No double-quotes ! Single-quotes all the way !

- weird flex, but OK. I'll comply

No CRLF ! LF only !

- Ok, now you're starting to annoy me. With git autocrlf I can have my precious CR locally bu check in only LF and YOU CAN GIVE THE FUCK ABOUT WHAT LINE ENDINGS I USE LOCALLY WHEN EVERYTHING WILL BE CORRECT WHEN PUSHING COMMITS!

No semi-colons !

- Now I hate you

Pixel perfect layout bugfixing doesn't even feel like development, it only proves that some people got their priorities terribly wrong if they worry about a 2 pixel margin anywhere. And I do say this as a front end dev who does respect a respect a good design. But still, pixel pushing sucks!

Please don't use 'FE' as an abbreviation for 'front end'.

It's idiotic.

In 2019 I want to get better at PHP & React & stop being afraid to try & fail! I do a lot of front end work, backend still baffles me a lot. Time to get uncomfortable! 👩🏼‍💻🤓

The Zen Of Ripping Off Airtable:
(patterned after The Zen Of Python. For all those shamelessly copying airtables basic functionality)

*Columns can be *reordered* for visual priority and ease of use.

* Rows are purely presentational, and mostly for grouping and formatting.

* Data cells are objects in their own right, so they can control their own rendering, and formatting.

* Columns (as objects) are where linkages and other column specific data are stored.

* Rows (as objects) are where row specific data (full-row formatting) are stored.

* Rows are views or references *into* columns which hold references to the actual data cells

* Tables are meant for managing and structuring *small* amounts of data (less than 10k rows) per table.

* Just as you might do "=A1:A5" to reference a cell range in google or excel, you might do "opt(table1:columnN)" in a column header to create a 'type' for the cells in that column.

* An enumeration is a table with a single column, useful for doing the equivalent of airtables options and tags. You will never be able to decide if it should be stored on a specific column, on a specific table for ease of reuse, or separately where it and its brothers will visually clutter your list of tables. Take a shot if you are here.

* Typing or linking a column should be accomplishable first through a command-driven type language, held in column headers and cells as text.

* Take a shot if you somehow ended up creating any of the following: an FSM, a custom regex parser, a new programming language.

* A good structuring system gives us options or tags (multiple select), selections (single select), and many other datatypes and should be first, programmatically available through a simple command-driven language like how commands are done in datacells in excel or google sheets.

* Columns are a means to organize data cells, and set constraints and formatting on an entire range.

* Row height, can be overridden by the settings of a cell. If a cell overrides the row and column render/graphics settings, then it must be drawn last--drawing over the default grid.

* The header of a column is itself a datacell.

* Columns have no order among themselves. Order is purely presentational, and stored on the table itself.

* The last statement is because this allows us to pluck individual columns out of tables for specialized views.

*Very* fast scrolling on large datasets, with row and cell height variability is complicated. Thinking about it makes me want to drink. You should drink too before you embark on implementing it.

* Wherever possible, don't use a database.
If you're thinking about using a database, see the previous koan.

* If you use a database, expect to pick and choose among column-oriented stores, and json, while factoring for platform support, api support, whether you want your front-end users to be forced to install and setup a full database,
and if not, what file-based .so or .dll database engine is out there that also supports video, audio, images, and custom types.

* For each time you ignore one of these nuggets of wisdom, take a shot, question your sanity, quit halfway, and then write another koan about what you learned.

* If you do not have liquor on hand, for each time you would take a shot, spank yourself on the ass. For those who think this is a reward, for each time you would spank yourself on the ass, instead *don't* spank yourself on the ass.

* Take a sip if you *definitely* wildly misused terms from OOP, MVP, and spreadsheets.

I'm generally new to front end development, couldn't keep up with the eco system even if I wanted to.

But what the fuck am I supposed to do when UX gives me mock ups in absolute units of pixels?

I thought best practice was for development was like vw viewport units of em units, because of the wrinkle of supporting different screen sizes and devices.

Is the general industry practice I'm supposed to use their general ratios and just get close enough? Like I don't want to dick around for diminishing returns trying to get shit pixel perfect, I don't have an eye for this shit to begin with.

Junior Software Developer Job( $37k-$42k USD)

-1 year experience
- J2EE, Javascript, HTML, XML, SQL
- object oriented design and implementation
- management of relational and non-relational such as Oracle, PostGreSQL and Cassandra
- Lifecycle and Agile methods
- Familiarity with the Eclipse development environment and with tools such as Hibernate, JMS, ,TomCat/Gemini/Jetty, OSGi.
• UNIX skills, including Bash or other scripting language
• Experience installing and configuring software packages
• ActiveMQ troubleshooting/knowledge
• Experience in scientific data processing and analytical science in general
• Automated testing tools and procedures, including JUnit testing, Selenium, etc.
• Experience in interfacing with scientific instrumentation, potentially over IP networks
• Familiarity with modern web development, user interface and other ever-evolving front-end
technologies, such as React, TypeScript, Material, Jest, etc.

I am betting they don't get many people applying.

we want you to be
- full stack developer (you do everything front end, back end)
- dev ops/SRE (you can sort out the deployment CI/CD pipeline, cloud platform services AWS/GC/Azure whatever)
- architect (you can design the software as well)
all in 1, you gotta be multiple roles/departments
good luck getting this experience on the job (hell in a startup is not for everybody and certainly not for me)

also why the fuck companies who aren’t startups ask for this idk

not sure if i missed any roles/competencies so far , don’t forget you need like >=3 years of experience possibly in every field for entry roles and more for anything higher than that

Recently, our backend team has gotten smaller. The company has stopped the collaboration with the company of the backend lead developer.

We are currently lacking backend developers while we have way too many frontend developers right now (compared to backend).

How can I, as a front-end developer, switch to back-end?

I'm literally one junior developer building a front end stack for a company that uses the waterfall method of building shit...

My application has not been fully tested and none of the real user base has actually tested it. I have no clue what potential egde cases exist in my application. I did as much testing as possible but it's keeping me on edge that there is potentially something broken lurking underneath that I don't know about.

If it is broken it's all erupting into flames and there's nothing I can do about it because the application will have to go through a whole beuacratic process to allowed to be fixed.

Job post I saw today. They are either looking for:

- C/C# Dev to the company
- HAPPY Frontend dev
- Java Dev to the company

Well now.. only the front end gets to be happy but doesn't know where to work while the other two can be grumpy and know they'll work at the company? 🤔

Does anyone think tech recruiters are failed used car salesmen?

Bad experiences this week

One reached out to me on clearance jobs to apply for a job that I applied for, interviewed and was turned down for because of course they do not know Javascript is not Java and they were looking for a Java developer. She didn’t remember and then never responded. Out of spite I replied all to the last email that company sent me but of course no one responded.

This person who says that she is a recruiter for GOOGLE does not know the difference from UX designer and UX developer.

“ UX design still involves coding... idk where you got information that UX designers don't code but they absolutely do. UX designers are simply front end software engineers that work on refining the user experience of a particular program app or website.”

I don’t know because I used to be a fucking UX developer and used to work with UX designers??? Who didn’t code because figuring out what humans what is tough enough on it’s own. UI designers may know html/css but that is it.

I know we are going into a recession and I need to start being nice to these dumb recruiters because I may need them one day.

Front End Web Dev 💻 I've dabbled in game development and wish I had more time for it. 🎮

I love the job hunt, just thinking about ending my life everyday now. Maybe I'm just a bad programmer - or just completely dumb.

Anyone have any advice on getting front end developer jobs?

Does anyone else find it strange that the stupidest people in the company are making all the decisions.

In order to be able to engineer software you have to understand everything that the product owner knows, the business analyst knows, the product manager knows + how to actually make the system both work in a reasonable time frame and be maintainable long-term.

But we're not the one making the decisions. The irony of it is something that I can't get beyond.

And when I do go out on a limb to point out a logical inconsistency to UX or product... They don't thank me for it they hate me for it and then 3 days later figure out that they should be doing it and quietly follow my suggestions.

Seriously is the goal here to create good software or to avoid stepping on everyone else's toes in the company who is overwhelmed by the complexity of the project.

I think companies based on a hierarchy of non-technical people controlling technical people, in the creation of software products are a dying breed.

When it comes to creating software products everyone in the hierarchy should be technically minded.

I've seriously been trying to come up with an alternative perspective here.

The executives of the company are completely out of touch and the only thing which looks like progress to them in a sprint review is something visual on the front end.

The technical architect, the product owner and the product manager all seem to be engaged in keeping the executives happy and managing their expectations. By means of obscuring the truth.

Imagine how much more cost-effective building a software product would be if the executives were engineers themselves.

I'm keen to do an experiment and build a company comprised of engineers only.

Obviously they need to have insight into the other roles. But none of these other roles are as complex as implementation itself.

So why exactly are we the slaves of these well-meaning under thinkers?

WORDPRESSS DEVELOPERS:

What’s your #1 tip for getting started in this role? Useful training site or video? What’s best to focus on first? Hooks? I need all the juicy deets! 🙌🏻

I have to make a change to one of our web apps today. I hate front end, the code for this is terrible, the fix is going to be horrible and hacky.
I really miss having some kind of motivation for this work, it would make life easier.
Instead it’s just one empty pointless day after another.

when you gotta do front end tickets but the mockups you received to implement aren't finalized

fml

Never ever ever ever ever ever ever ever ever ever ever ever give the opportunity, not even once, to let a BE decide how a front end is going to work. They will fuck it up 100% of the time. I’m sorry but it’s true.

A new year, a new job.

After a years hard graft learning front end code I finally landed my first dev job!

Even though the job is a while away, there will be nothing stopping me getting there and learning all I can in this industry.

#bosh

Just to show you.

The overhead between actual SQL requests and the stack :

.Net 6 =>
Web API =>
EntityFramework core 6 =>
(middleware) GraphQl.EntityFramework =>
GraphQl =>
SQL

Seems a lot ? Yep. But actually... that shit just scales. More sql requests will not cost much. And this stack will take care of generating optimal querry better than me by hand.

(These querries on screenshot are fairly complex).

I like it. So, so much checks done for me and front end people love it too ! They don't need to open a tiocket when they need a new field.

So, /adpoted by me.

PS : And pair it with Blazor, miam.

On an all hands, someone talking about a spreadsheet and my brain hears "so we should turn this into a database with a front end but you're not a dev and none of us care enough to help".

Are we the bad guys?

I just started a new job where in my onboarding, I’m supposed to learn typescript and react. I am also supposed to gain some knowledge of databases. Since I am so new, I don’t really have any meetings. I see my manager maybe 2x a day. I’ve been using my time at work to learn these technologies.

I learn best by doing projects. I recently built a bot that scrapes media off of one site and posts it on another site. I was thinking I could create a react front end in typescript for the bit. I would also add a database to my project (the model for the front end) which contains the post history of the bot.

Would that be appropriate for work? I thought it would be good project to help me learn react. However, I am new to the “corporate” world and I feel like my manager won’t want me to waste company time on my side project.

The only other responsibilities I have are reviewing the source code and watching some onboarding videos

From my job applications I have concluded that there is a large surplus of front-end developers and a serious lack of back-end ones.

Why are JavaScript coders called engineers (ie front end engineers, node engineers) but dotnet and Java are called developers?

Randomly generated CSS class names make customization of sites much more difficult.

Randomized gibberish CSS class names like "r-acJ79b" are used by some sites like the new Reddit and the new Twitter web apps, which makes it impossible to customize the appearance of the site and to hide "trending" spam. The only way hide annoying and spammy page elements is through user scripts which scan the page for it every second and then hide it. But until then, it appears on screen for a short period.

I once thought this is caused by react JS, but the react JS front end of the video platform "Odysee" does not have randomized CSS class names.

I have been coding since 2016, am I overthinking applying for jobs because Im not that "current"? (my React experience is not that deep, I have been working on our startup whos stack doesnt use React or any other front-end framework (only simple handlebars templating))

I have built an actual stable working web platform and mobile app through ionic, is this enough to get a decant non-junior job?
I have never actually worked at a company, its been freelancing and startup (we failed, moving on). Am I overthinking how good I need to be to get a job? I like this one local company but I dont want to screw it up, Im sort of delaying applying there because of it

WooCommerce sucks, Block editor sucks, Elementor is no better, but if you want a real mess, just add more plugins. Bonus: if you use any "third party WordPress plugin", WooCommerce support can always say, oh yeah, I see that you are using a third party plugin, so we cannot support you, sorry.

Fuck, that's not the kind of front-end development that I was hoping to do in 2023.

It's a career suicide wanting to transitioning to desktop developement? I'm tired of fighting with tons of external dependencies (VPN, database, other microservices) just to test a microservice or a piece of front-end, I just want to focus on code.

My job description is software developer but I'm spending more time playing the sysadmin to keep my local developement environment working than what I spend actually coding.

What the fuck is this syntax in a typescript file, I'm having trouble finding documentation if anybody can enlighten or link me

const [, updateThing] = useMutation(UpdateThingMutation);

The [, throws me off

i fucking hate front end

Was having a conversation with a dev friend and he said, in every tech implementation, we are more or less doing CRUD operations at fundamental level.

To which, I agree with as there are three layers to tech

1. Data
2. Front end where the data is rendered
3. APIs to perform CRUD on data

Want to understand community's thoughts on this..

Me at 3 front-end tech screenings of candidates with +3y of exp last year: "can you name a few npm commands you have used?"

Candidate:
- "Ehh.. npm start?" (npm start is a shortcut to a user-defined run-script)
- "npm version, it publishes the package" (wrong)
- "not going to pretend I know and sound stupid"

Mind you these candidates were not necessarily bad, but come on? You never used npm info, outdated, audit, install, remove, update, why, link, init?

!rant

Just an appreciation post. Ant Design is the best React Library that I have encountered so far. It's so easy and clean to create new modules. It has already built-in features, especially for Tables.

As a backend developer who has been working in front-end for the past 6 months, I love this library.

We're using a setup with c# dotnet backend and js (React) front end... and do one in VS and the other in VS code. Any way to get one IDE to handle both properly? It's a huge pain but my manager told me that's just how they do it

I don't know how to CSS, react or front end

.entry:not(:first-child)::before {

however I read identical css in the chrome debugger for the ::before element generated and the general enclosing entry element for the elements displayed in a horizontal row

but the fucking divider element is askew for new elements of a different react component type i've added to the list

i fucking hate my life and front end

It seems to me that browsers lagging behind is the reason we've seen the JS framework boom both in recent years and ongoing, evident in what they regard as major updates. Most of the functionalities implemented in my time working on the front end are high level problems ubiquitous enough to have been solved at the browser level. Same goes for all the optimizations CSR frameworks are struggling to attain. Every CSR app genuinely feels like recreating a browser, both in UX and dev requirements. These problems exist because current browsers are analog software still accustomed to loading all content at once, no in-app state, just scroll states

The React-Vue-Angular wars of today are a direct hat-tip to the Netscape-Microsoft wars of the early years. If they can form a coalition that sets a standard for syntax, best rendering engine, natural way for user facing devs to control app state, fetch data or connect the back end, somehow render this on the server or find a workaround SEO issues on CSRs, etc, given the shared agreement on expectations for modern web software, it'll be fascinating to see such a possibility

When I wanted to make a game. I'm a front end web developer. Lol.

One of our senior colleagues in my last project at TCS had brought a pen drive with him, not sure why! He worked on a client system, which he believed was not monitored by TCS. So what he did was, he plugged in the pen drive in his computer and tried to copy some files from his pen drive to the computer. However, he wasn’t able to copy the files.

We weren’t aware of this until our project manager, who sits at the farthest end of the ODC shouted at the top of his voice, calling out his name. In front of the entire ODC, he was scolded since the HR team had called the manager informing that the machine assigned under this employee’s name has detected a security breach.

He had to explain the reason; where he said he wanted to copy some codes that he had to office machine in order to reduce his manual effort, which was probably very silly of him! For the next few days I hardly saw him inside the ODC, probably had to visit people to show cause or other things and was harrassed by our manager, insulted every time he passed by him.

He was not suspended although, maybe the manager or someone else saved him, although normally such violations would have seen him terminated.

!rant
I'll be the first to admit that my web dev skills are average. Where I work we don't get pushed much since we work off of a very limited (custom to us) platform, which doesn't leave one very well rounded. I am very good with CSS/HTML/FLEXBOX/RESPONSIVE DESIGN and have minimal skills in PHP and JAVASCRIPT. In school I've dabbled with SQL, but hell if I remember much (beside key, the whole key and nothing but the key). What other languages or codes do you recommend learning; what's hot right now? Or should I focus on putting higher emphasis on the ones mentioned above first? I am a front end developer and don't plan on ever doing back end so not looking for the toughest of the tough - just something that will help me grow and land a better job. If there's any cool learning sites you know of too, or other tools, please let me know.

Why is no one ever talking about cli flags in OS X?
For instance: "ls / -lahtr" doesn't work in OS X.

The flags must be directly after the command.

And I have no fucking clue why. The only reason I can think of is that there must be some best practice paper and for the OS X version they compile a version that complies with those best practices.

I mean, not all programs do that. But a surprising amount.

And it is so annoying when I use a Mac. I have the habit of first saying what I want to do and finally adding flags at the end as an afterthought.

Recently, my wife couldn't make a curl command work she got from a tutorial... Turns out the curl command was written for a linux system and ended with a "-o filename" argument. Solution, move the argument to the front. Worked like a charm. But if you don't know about this; this might stop you dead in your tracks...

And the strangest thing... I never read anyone talking about it. Complaining about it. Or at least warning about it. Something like "hey, when you're on a mac, make sure to put the flags in front". Just acknowledging the existing of this.

Why is it that this quirk did not make it into public debate?

A new position is opened at my company and I am tasked to conduct interviews for the candidates. I have no experience whatsoever in this.

If you’ve had any experience, how did you approach this? How did you conduct technical interviews with the candidates? We’re talking about candidates that have 3+ years of experience.

The position is for front end, mainly ReactJS.

Does anyone have experience with using Kotlin as a front end language? Seems to have excellent JS interop and I really don't want to deal with the garbage fire that is JS or TS 😬

I have some down time at work & nobody on my team has any extra work to go around, so I thought I'd use the down time to learn a new skill. I am a front end developer who mostly works with HTML, CSS, PHP & a small amount of JavaScript. I do a lot of work with flex box, and frameworks like bootstrap. I've been considering learning angular or working on my php as that's my weak area. Any suggestions on cool things to learn and/or where to learn them?

It’s a huge nightmare to develop a React front-end when:
- you have to adapt Bootstrap 3/jQuery based components to React
- the “back-end” is a sparse collection of micro services with cryptic URLs and finding the correct name means searching on a laggy WSO2 API manager
- the documentation of said micro services can be outdated and that means wasting a lot of time trying requests on cURL rather than in doing actual development and continuously breaking your concentration
- sometimes the micro services just become unavailable altogether
- the back-end shuts down at
6PM everyday, usually when after I finally achieved a flow and I’m doing meaningful progress

So I’m tryina put together a resume and I see a lot of dev résumé talking about increased revenue from x to y or user base from z to w.

What I don’t understand is while yes the user base did increase from z to w it wasn’t just you that caused it. The entire company was working hard at it to get there so why are u claiming that it was you. And apparently recruiters love these kpis that u make out of your ass.

Should I give in and just put them in there anyway?

I worked in a startup so my job didn’t really have a definition of what to be told to do and do I had to deal with building front end with vue to figuring out how to automate our deployment flow and it’s really hard to quantify my performance like sure 3000 tickets solved but u don’t know what portion of them were full blown features what portion was just a one liner.

How do you pick a new language to learn?

I am a C# developer and at work I work on desktop apps and legacy web services etc.

I fancy learning something else so I can have a bit of variety when working on personal projects etc.

I am doing a distance learning degree which has used Java and Python so far, with some PHP and JS etc to come later.

I’m drawn to Ruby as I already have experience there, but I was also thinking about looking at Node as that covers back end and front end all using JS which is definitely useful in general as I look at moving to a more web based role.

front end devs, do you put your dropdown values in a database or in the code? follow up question. if database, do you put all the dropdowns in one table?

So, I have joined this new company where I used to work few years back. Something happened before I rejoined, so no one is working there now except me. It's web agency run by my boss and I am the only employee working on over 7 projects including front end, back end, mobile, devops, and some marketing also.

Now, I got offers from couple of other series a funded startups who are willing to pay me 30% more salary. I know I will have less responsibility and more work life balance. But I hate the politics in those companies.

My current company is making good revenue but my boss isn't giving me the salary I am expecting.

He said it will take few more months to give me the salary I demanded.

I also want to build my own company and provide services someday. That's why I thought it'll be better to stick with the company so that I cam learn other aspects of the business.

So. If the company is making say over 200k usd a year and its paying me around 23k usd per year, isn't this kinda low salary for my experience, skills and value I bring?

How should I go about asking a raise?

Also, I don't wanna move to another big tech company. I hate coding questions in the interview as its been years I have prepared for a proper tech interview.

Also, how secure do you think my job is? Is there any future working here? Will I ever be able to reach a salary comparable to big tech companies?
Is it a good place be in right now? (i jave over 5 years of experience)

I tried Appgyver over christmas, since it promised easy front-end (no-)coding I was looking forward to getting rudimentary frontends done faster.
Well, the first real project that I wanted to start didn't compile anymore (internal error from the service), the page told me to reload and try again.
It failed again... And again.
Fine with me, I only spent 10 minutes on the project at this point.

I then searched for the bugreporting page and found it. The sad thing is that when I wanted to open a ticket the server crashed. It didn't even return a HTTP error, just a JSON saying there is a error and a GUID.

I have to say, if a Dev decided to have holidays without new issues that's one way of getting that done.

I truly believe that a back end needs to know about front end as much as a front end needs to know about back end.
And a more serious belief is that project managers / owners need to know about both. Thank you.

it seems the user have finally give up to use the system that i developed for 2 years. reason for not using : a lot of errors, and not meet their expectations.

client have demanding a lot of changes while we develop the system, and we only have 1 front end dev and 1 back end dev. thus, a lot of errors occurs. not to mention that the user also wrongly use the system, despite we already provide them training and user manual.

user have another error yesterday, and i have fixed it, but before saying to user that is fixed, i am still waiting for client to send me list of things he want to update (he said to me send me by this week but now its already thursday).

i feel lost.

After more 3 years developing for the web I’m considering to learn Swift and Objective-C and then switch to iOS hoping to find a job which involves less multitasking (now I’m split between front-end, back-end, DevOps and other), what’s do you think about a switch like this?

What should you do if the project manager is not assigning you any new work after the backlog already has been cleaned up?

I currently work as a junior front-end dev. For the past few weeks, the 2 juniors (incl. me) are lacking tickets. For example, I got 2.5 days of work assigned during our 3-week sprint. We already followed some courses, read some books & created some designs for upcoming features (that have no "functional specifications" written down).

Any salesforce developers here? What's your day-t-day life like? And can anyone compare and contrast it with their day-to-day as a full-stack or front-end/back-end engineer?

One of our previous clients is not paying the rest of the payments after receiving the codes. What are the things we can/should do digitally to make them pay the payment?

btw, it was a web app. we worked on the front end and the backend of the app. So, naturally we know all the API endpoints, we have the database access, and so on. So yeah, we can do so many things.

But still I wanna ask you guys, what would you do to make someone pay?