To all new devs:
- Your language of choice is fine.
- There is no superior way to indent, yours is fine.
- Your IDE is fine.
- Your OS is fine.

Unless you work in my team, of course.

My advice for new devs, or to all of us :)

To the new devs:
Never push production on friday

// repost \\
To all new devs:
• Your language of choice is fine.
• There is no superior way to indent, yours is fine.
• Your IDE is fine.
• Your OS is fine.

Unless you work in my team, of course.

Updated description!
Fuck Wordpress in the ass with a new kind of cms. Make devs happy with clean code. And Laravel

11 kids in Sydney recreated Martin Shkreli's drug for just $2. The moral of the story? When you do cool shit like this, it's ok if you don't wear pants!

Naming advice for new devs:

Test
Test1
Testtest
Final
Finalfinal
Final1
Asdjsfkd
Jkhfd

Three days ago I wrote a comment:

"It's weird how the internet shifted from protocols to platforms.

Devs still know the plumbing, but for most people IRC became Whatsapp, FTP became Dropbox, RTSP became Netflix, SIP became Zoom and RSS became Google Now... so people might eventually forget about SMTP and this whole "email" hype.

In a decade or two we'll have forgotten about URLs and HTTP and the "internet" as well. You just pay your monthly $10 sub to Google or Amazon or Apple to have your condensed streams of memes & bait funneled right into your eyeballs."

And now Chrome devs are considering removing URLs just like in Safari, just showing the domain you are on....

Enjoy your retard web, people.

What's next, new Macbook & Chromebook standardized designs to prevent people from being confused?

Just left a job where I felt like one of the best devs on the team. At my new job I feel I have so much to learn from the devs I work with. I'm so happy. :)

Here's my piece of advice for new devs out there:

1 - Pick one language to learn first and stick with it, untill you grasp some solid fundamentals. (Variables, functions, classes, namespaces, scope, at least)

2 - Pick an IDE, and stick with it for now. Don't worry about tools yet. Comment everything you're coding. The important thing is to comment why you wrote it, and not what it does. Research git and start using version control, even when coding by yourself alone.

3 - Practice, pratice and pratice. If you got stuck, try reading the language docs first and see if you can figure it out yourself. If all else fails, then go to google and stackoverflow. Avoid copying the solution, type it all and try to understand it.

4 - After you feel you need to go to the next level, research best practices first, and start to apply them to your code. Try to make it modular as it grows. Then learn about tools, preprocessors and frameworks.

5 - Always keep studying. Never give up. We all feel that we have no idea of what we are doing sometimes. That's normal. You will understand eventually. ALWAYS KEEP STUDYING.

Web devs are like autocorrect:
- You're needed but never told you are
- You're great at your job, but everyone complains about your few faults
- You learn more as you work with the client
- You improve little by little every day
- Your buttons are pushed a lot
- You use new technologies when you can

😥 Also their rep system is so mucked up

So I was looking at the linux environment at my new job. Found 2 VM's in the local network, only one of them is documented. Noone knows about the other one or what it does, let alone usernames and passwords.

Spent over an hour trying to break in, only to find out that a couple of bored devs, that have long since left the company, set up a game server on there and noone noticed it for the past 3 years..

So you poor devs... you have to be strong now, hr has a new tool to torture you: Skype has a new coding interview function.
What do you think about that? Good or even more abuse?

To the new devs: at least once a week, go for a walk outside

Just joined a new job. Got into a team of 10+ devs working on one code base. Its spread across many cities and few devs sit together.

They've been versioning their code by mailing each other .zip files of the entire 400MB code base at the end of each day.

Me: Can we have git or svn please?
Manager: SVN? Don't worry about that now, we'll get SVN when the project is finished.

Managed to get an SVN repo running after 2 weeks. FML.

A new sales guy in a startup I used to work at was using Internet Explorer. I told him why are you using IE, it's a shitty browser and how frontend devs suffer to support it.
Before I continued, he interrupted me saying that he used to be the regional head of sales team in Microsoft and started defending IE.
I was like Oookaaayy.
......he left the company a week or two later

The Devs decided!
Behold my new name:
@IamGay6969
What...
No...
THIS CANT BE!
NOOOOOO!

Not a rant, just awesomeness:
At my company our CTO organizes a meeting every month that gives us devs a chance to present new technologies to each other, offer advice about workflows and give feedback about current situations. This allows us to constantly improve.
Thanks boss!

Dev created a new service for our application that opened SQL connections. The catch? They never closed said connections. How this passed QA/review I've no idea, but after a few minutes on Staging the service would crash with "connection pool overflow".

I raised a urgent defect, and the devs "fix"? To up the maxConnectionPool to Int.Max!! Argh!

For new or young devs

If you think you're like a 8/10 in a language........ you're probably a 2

#newdevs #behumble

Always the same story:

Marketing: hey I'm gonna do a demo to a customer. They were asking for feature XYZ. That's ready on thr staging server right? Do you think I could use the staging server for the demo?

Devs: well feature XYZ is not 100% done. Basically just feature X is done, and it still has a few bugs. The deadline ain't for another month, since we gotta finish ABC first. I guess you could use the staging, but it has a lot of bugs.

Marketing: perfect!

*after presentation*

Marketing: the staging had so many bugs! Why didn't you tell me?! It was so embarrassing showing it to new customers! Anyway, they loved the new feature. We need it to be ready ASAP.

Devs: What?! That's gonna mess up with our schedule. You know what? Fine, but feature ABC will have to wait another month.

Marketing: Well, it'd be ideal if we could do both...

Devs: Pay for more devs or dor extra hours.

Marketing: Just do XYZ. It's a pity that you'll have to push back ABC but it's fine, XYZ is more important.

(I might ask, if it was so important, why didn't you notice so in the meeting where we had decided that ABC would be prioritized?)

*tons of working hours later*

Devs: There, we finished XYZ.

Marketing: Yay! Wow, this month we'll have two major features done: ABC and XYZ!

Devs: No, ABC is not done yet.

Marketing: What? But the deadline was this week.

Devs: It was, but then you decided to prioritize XYZ and we said we had to push back ABC to get XYZ ready, and you agreed.

Marketing: Did we? Fine. But do it quick.

Marketing and their mood swings.

*project manager + designer are showing new designs*

PM: so, can we get some estimates?

Devs (literally all of us): do we have a mockup for this interaction?

Designer: no.

Devs: What about that one?

Designer: not yet.

Devs: What happens when you click here? Hover there? How does this look if I select that option + this option at the same time? Does it make sense that a user can select *this* option with *that* option? They're kind of mutually exclusive.

PM: Well...

BTW: code freeze is in two weeks...

We’re recruiting new team members, and so our recruiting staff wanted some input on what to look for. We told them that we need more frontend devs, mainly for JS frameworks like React and Aurelia.

And now a few weeks later we find out that our newly recruited Java developer is starting this monday. Thanks

Manager: We are now using libraries for everything. I estimate based on nothing that this will increase productivity x20.

*Project grinds to a halt while devs scramble to learn/implement new library*

General Manager: Where was the productivity increase?

Manager: Our devs are not willing to learn new things quickly

Fuck that fucking company three way while dozens of homeless HIV crack junkies puke and shit their diarrhea on the three bosses!

I can't put it in words how stupid they are!

Let me try to tell you the latest story while I try not to get multiple strokes.

Backstory: We are three devs, all with a TCCI certification. One has been working for us for almost a year, the other one has been working for us since one and a half year. Both are good friends of mine, btw. I have been working there for almost three years.

Fortunately, I am allowed to work on a reasonable computer. The other devs work on PC's with Windows 7 and 8!

One has just 400 MB space left on his drive and has to delete every month some shit because he does not want to be able to call up websites anymore... How awful?!

The PC of the other great Dev Crashes three to six times a day and needs about 30 minutes to start up!

We can be so productive, but...

We told that in February one of our bosses and asked him to buy new hardware. His answer: yes, of course, I understand that, it's my turn (he always says that "ich bin da dran")

We got a new colleague in the middle of this fucking month. She is responsible for conception.

She works on an old notebook, but today she gets a fucking new PC to work on while the devs are trying to weld with a sparkler! Better hardware than every other Dev PC!!!

Guess what? She is the daughter of a friend of one of our bosses!

We are the only devs at this company.

Fuck that fucking company! Fuck that fucking bosses!

I think we don't go to work for that fucking company anymore!

As devs we like to complain about our jobs. But I just want to take a moment and acknowledge how truly amazing writing software is. Nothing else has given me so much joy and happiness. The endless stream of new things to learn, the elusive art of clean code, and deep understanding of systems required for architecture. There is so much depth to this career we have all chosen and I hope you guys love it just as much as I do.

Most unprofessional experience at work?

<about an hour ago> Went into the bathroom to do the morning deuce and there was crap all over the back of the seat. WTF!? Did you miss!? In our part of the building its only devs and network admins, so again, dudes, WTF!?

Oh, and never spit your gum out in the urinal. Its not a new, fun target for you to shoot at. *Somebody* is going to have to pick that nasty thing out. Our maintenance guys have hard enough job than cleaning up after 'so called' professionals.

So python, who knew it could automate a lot of crappy tasks 😎
Actually I did, but god it’s so quick and easy to implement than expected.

I have a new formed respect for python devs after my day of web crawling and ftp transfers and outlook mining 😘

Rant from my old company:

CEO decided he could cut costs by outsourcing to cheap devs in other countries.

Does this, the new hires are super incompetent. We're now paying for a whole team that is adding work cause they keep fucking up.

Leadership is super happy with the "savings" (which is basically just the team here working harder to fix everything).

All the smart people start leaving, leading to a downward spiral.

Last I heard, one of my junior co-workers had been promoted to senior (he hardly had any coding experience).

Fuck them all

post != rant;
post = "Feature Request";
@dfox

Stack Overflow is full of abuntch of downvoteing dickbuts. The devrant community is so much more accepting of new devs, why not add a question section.

Down votes would only be allowed for spammers.
One the question was solved, it would go into the devrant question archive, Searchable by everyone.

Ik you have heard this one before, but it's Just my two cents.

You know you're fucked when even the lead dev can't think of a decent solution for your problem which is...
.
.
.
.
.
.
.
.
.
.
... the most difficult challenge devs have ever faced:
.
.
.
.
.
.
.
.
.
.
What should be the name of the github repo for the new module?

Whether you hated 2017, 2018 will be better, promise.
Wish everyone a happy new year.

Best wishes,
cozyplanes

P.S.1. Thank you everyone for making me the part of devRant!
P.S.2. Thanks David and Tim!
P.S.3. If you need to work todayn and you don't think that it is the right thing to do, think of engineers working in a TV/radio broadcasting company. They should prepare the show! (Poor devs there)

To good to not to share.
The dev is to blame.
New devs remember to never do this.

Apple flips the bird to devs again...

So I go to release a new version of my app (critical updates and bug fixes from mgmt) and I had just updated my phone. Yeah, that was a fucking mistake.

“This version of Xcode is not compatible with the new version of iOS.”

Ok... update Xcode...

“The new version of Xcode is not compatible with your version of OSX”

WTF?! This version isn’t that old? Fine... update OSX. 5 hours later...

“Hey, just wanted to let you know that we decided to break every one of your web development tool setting and basically nothing works on your computer now, oh yeah, and we’re Apple so FUCK YOU.”

Facebook devs be like,
Today I'm gonna change a variable name and release a new app version.

PO: we want this new functionality, a new api call is needed in checkout process

Devs: okay, and what should happen in case of error?

PO: dont worry, it wont fail. Never.

🙃

Countless times. Here is two:
- when he said he prefers an external hdd over git
- when he said that git is just a shiny new thing, we young devs use just because it's new
- etc

I'M TIRED OF HEARING THAT DEVELOPMENT IS NOT A CREATIVE FIELD! Creativity is emerging new ideas from non-existent ones. It is not confined to pretty designs or well-written copy. Sure, devs are logical problem solvers – but not a single dev will solve those problems the same way. Code is like the paint on our dark-themed canvases and you can see yourself out if you think devs are just robotic coding machines

"We don't have time for writing tests"
"Yeah we could write them but only if the client paid us for that"
"You can just test new features manually!"

- Most devs of our mobile team.

Every day they're fighting with bugs and when they're fixed, a couple more pop out of nowhere.

Dear god help me.

Why don't devs read the fucking docs?

Time and time again I find my coworkers inventing new ways of doing stuff that could easily be done with existing features.

Today I saw this on a code review (functions are from lodash):

head(filter(...))

That's what fucking `find` does, you dense motherfucker!

This is just a tiny example. I've seen so much of this shit. Sometimes it's almost art how they find ways to solve problems without actually reading the docs.

Dear fellow JS devs, if you make 1 more good damn module loader I swear to god....

Hi - here's a new module bundler named parcel.

FFS

I'm curious, is email campaigns such as 'constant contact' part of a devs job? new job wants me to be in charge of this and I could not think of a worse job I would like to do.

I don't even check my own email!
I hate social media and suck at posting anything besides random useless memes.

REALLY??! Email campaign????

To new web devs from a new web dev:
Try to design your site before you write a single line of code. Be it Photoshop, Paint, a piece of paper, a literal goddamn canvas, you name it. You may thank yourself for it later.

I find it ironic that some python devs hate on nodejs because of npm modules. But then go ahead and create a virtual environment for every new python project.

The management brought some devs from another outsourcing company into our project to overcome the fact that we, the existing developers, are retarded. We are retarded because they change the scope continously (aka daily) and we can’t keep track with their requests. They want something and after we implement it, they want it changed. Completely.

Instead of getting the project and deep dive into it using the materials (setup, architecture etc.) I prepared along the way, their PM said that we have to make some low level knowledge transfer. This knowledge transfer session happened on Friday.

The presenters were me and one of my colleagues. After 2 hours of training, we found out that the supposed senior devs don’t know how to use GIT, they don’t have a clue about Spring nor Angular (nor any SPA framework), their only questions were ‘why didn’t you use X?’ (where X = bootstrap, jQuery etc.) etc.

What is even funnier: during the presentation we were asked to keep a screen sharing opened during working hours for a couple of days just so the new devs could see how we are working.

Guess what happened with the scope on Friday evening: it changed again because ‘you got new devs so there will be multiple resources to handle tasks’.

2 more weeks and i’m out of there...

Where I currently work (and have done for 10 years) we were recently recruiting for another dev, and one of the other devs and our line manager were running the interviews.

After 3 or 4 failed interviews they decided to test the questions on me... I got 3 out of 10 :(

My argument was (and still is) if I get stuck programming I can google, or you can teach me new stuff. And I can make a good cup of coffee

Adventures​ Of The New COO

So when that new COO joined our company ( read my previous rant to know that story ) he brought a graphic designer with him

as a designer he's ok, more of a old school package designer type, but as a person one of the most annoying one I've ever met, always want to be included with our conversations, talk about rain and stuff

so few days ago, i was working on a website, headphones plugged in, music playing, he comes near my seat

Designer​: Are you busy ?
Me: yeah, I've this website to finish
Designer: So i have this idea for an app
Me: *taking off headphones while thinking doesn't this dumbass know the meaning of busy*
Designer: what if we create an app for super markets, like this isle has this stuff, that isle has soap or something and how it'll be easy to find what you want to buy and keeps going on and on for about 5 minutes
Me: *making my voice as polite and sarcastic as possible*
It wouldn't work, every market has a different layout even among same market chain it's different
Me: have you ever been to a super market, they have a board saying what the isle is above the isle, all you have to do is just look up
Designer​: hmm yeah i guess
*walks away*

everyone​ wants to make apps and make money, but doesn't have the fucking brain capacity to think about the idea for a bit and do some research, instead they come and waste our time

Ok, so I work at this "Great" company. I joined a new team recently with a project that is supposed to be a lot better than many of the other projects we have.

THESE MOTHEERRRRRFUCKERS don't even have hot reload on the app. You have to rebuild the app everytime you make a change. Are you kidding me?! We are using React. One of the basics of React is hot reload. I get into a fucking meeting and one of the devs is like, "I have one important thing to tell you, don't use hooks (a not so new feature in react yet something everyone should use at this point)" and the critical reason we don't use it is because they don't want to confuse the Java devs who are used to their little oop style o_O

Maaaan fuck your developers, it's not my fault you guys can't learn something so simple like functional programming. I haven't even started a sprint yet, I'll burn this app and make you rewrite it all.

"Hmm, I have a meeting with a few of the executives today to go over that new feature... I'd better wear my good t-shirt and jeans today."

I love working at a place where there is no dress code for devs!

One of our backend devs just changed an existing migration instead of creating a new one.
Thanks a lot mate.

Super stressed.
What I did is:
1. git pull --rebase
2. Forgot to build to check if everything is working after pulling new changes
3. git push
4. Now, I realized I forgot to implement a method of the recently changed interface.
It's a production code. Not a joke. And was my first push to prod and I messed it up.
Sad life. Fixing it. Senior Devs must be crazy for my silly mistake.

Colleges aren't teaching enough practical applications of why we devs do what we do. Get students engaged with small business! Get them to think about how they apply what they learn to the real world!! We need creative new ideas from developers that think outside the damn book!

New country, new company, new team, new projects.
I'm supposed to be the TL of a team working on a React project.

A guy in his late 40s celebrates himself as "the senior", he basically just finished watching a youtube thing, React 101 crash course or similar. The other two juniors who did only Wordpress so far venerate him like a god.

The code, of course, is one on the finest pieces of crap I ever had the pleasure to deal with in my life: naturally a bunch of JQuery plugins for everything, no tests, no state management, side effects everywhere, shared state and globals like hell, everything written in ES3/ES5 style, no types, no docs, build and deploy totally manual, deep props drilling at every level... and not to mention the console.log() shipped in prod.

First day, already headache.
Full rewrite start tomorrow.
Hiring real devs as well.

Oh look, a new fancy MacBook Pro 2018.

How come noone is talking about the extreme heat throtteling problem they have with the 2018 laptops?

They can't even hold their base clockspeed when doing compiling code. And they become extremely hot (worse then the last gen, which was already insane).

I know devs/creators/editors want the most powerful computer out there, but supporting something like this is just laughable.

Regards, disapointed customer who tested and returned the laptop after 2 days.

Devs: We fixed a bug, so watch out for some changes.
Management: The new values are too bad, you need to change it back.
Devs: But ... it was a bug?
Management: Rollback ... now!

I swear, the moment shareholders are involved, management is just about who has the best lie.

Ok, so I'm one of the new folks here, and spent some time looking around.

And I've read so many of you write about levels of insanity at work that just baffles me.

Why do people do that to themselves? And no, I don't mean you sales-manager, or your boss who hired the wrong kind of dev, I mean YOU.

You are a developer, currently the market for devs is so large you can literally pick your jobs. And if you don't know how to find a new job, just Google (easy mode, search on LinkedIn) a company which specializes in recruiting, there are tons of them, and they will gladly search an employer for you.

Don't get stuck in a job that sucks - you will kill your motivation, and you deserve better.

!rant
Just started working for a new company. Super cool. Just like the last one (as far as perks), except they actually trust their devs.

Old company: Make sure your code is extensible
Devs at old company: You know it's not written in stone right?
Old company: Does that mean you can make it do this?
Devs at old company: No. That's the wrong code base

New company: I need a feature. Get it done when you can
New company devs: Well, guess I'll take some time to refactor all this stuff while I'm at it
~Some time later~
New company: Thanks, that feature works great!

No staring over shoulders, asking when it will be done. No asking why we want to refactor something. As long as work continues to flow, there are no issues. It's great!

Also, if we want to try a new tech, we just have to put together a short paper explaining why it will work better in that situation than the tech that's already in place.

Yay I'm hiring two new devs 😎 hope they are good

Thank you VERY MUCH for wasting my life, ruining my new career and destroying my family. It hasn't been 24 hours from joining devRant and I am already addicted. Checking my phone every 5 minutes or so. Is this some kind of a conspiracy to wipe out weak and liable to procrastination devs? To suck them/me to a big, colorful fluffy garden of instant gratification?
Are you HAPPY!!!???

Employer asked, whether I could tweak the site's admin template that was made in 2005.
It uses tables to generate new webpages.
It uses php.
UI is a nonsense spaggethi crap.
Whole thing is shit.

Well, for good money I will just write everything from scratch. Took me ~10 hours and I already have the functionality that was in the original crap. Crazy how these 'devs' scam people!

Bethesda is full of shit. Starfield somehow needs a super new PC because it alledgedly uses modern SW tech.

Strange point: while a high-end PC with 7800X3D and 4090 makes the performance bearable (though not great), the graphics don't look spectacular. In fact, they look outdated.

No Bethesda, you don't use modern tech. You require modern HW tech to make up somewhat for your shitty engine and incompetent devs.

I’m a devRant virgin and also a new dev so...
Anyone got any general tips for a newbie? For example, what are some bad habits that newbie devs should avoid picking up? Good habits?

My company has two offices in separate cities but they treat each the devs of each location very very differently.

In one office the devs get full power to experiment with whatever tech they want, they just stomp their feet and management gives em whatever they ask for, freedom of choice regarding anything they are working on, to be allowed to do greenfield work or experimental stuff

But in my office we are forced to do ONLY. Bug fixing and refactoring shitty code from over a decade a go, our tech is ancient and we are not allowed to to
Shit , anything we ask for is denied
And improvements to our process is shut down with the reasoning that whatever we got works so why meddle ??

For us , management is solely focussed on making sure we respond to support calls , deployments , configurations and little bug fixing. Basically they only care that we manage to finish for out next delivery.
No new work whatsoever!
If there is any hint of something new to to
Implemented the golden boys from the other office just stopm their feet tillmthey get it or just go off and start working on it then seek permission afterwards, with their much larger team they obviously get further than we do by the time management hears about it so they end up taking over the work since they already have more done already

My manager decided to push us to attend a company devCon to share ideas with our devs from our other location. This rapidly turned into a sour experience

Basically we do all shitty boring work which puts money on the table which goes straight to those idiots to play with...

They have the guts to laugh when we mentioned that we never get anything interesting to work on

Never seen so many of our devs looking up job sites on the bus back...
This is gonna blow up in management's face...

I've got 4 words for new devs:

Get your basics right!

My new job will be finding new jobs for jobless devs... 😄

- Be me
- Been in a new job for 2 months
- Was excited because of 50% salary increase and better position

- Have a new team of 6 devs including me. All new guy
- Market crash
- Top management demands a trim down to all divisions
- Will be left to 3 devs next month

- All the while being asked to
- Deliver a shopify like marketplace from end to end
- Deliver integration with partners for data inventory tracking
- All within 2 months

- Furious when target is not met
- Demands a micro management to every single person on the team on what their day to day schedule
- Demands everybody to live by hustle culture and ready to work non stop even nights or weekend

- Be me
- Been working non stop for at least a month
- Sacrificed weekends and holidays

Beginning to think that maybe the money and position isn't worth the hassle

Ask yourself a couple of simple questions:
Do you like to code?
Do you like to learn new things and improve?
Do you like to solve problems and spend hours on a single detail until it finally works?

If your answers contain a "no", then development is probably not for you. You will hate it and you will suck at it. And you will make lifes of devs who actually love it miserable. So do something else.

Dear new devs/me five years ago:
Practice the 30 second rule-- Whatever brilliant thing that your about to say, just think on it for minimum of 30 seconds. Is it still a brilliant idea? Then share. Else trash it 😉

There's this huuuge project I was a part of for half a year. I was kicked off along with a few dozens of other devs (>60% of total manpower) a while ago for particular company reasons.

Now the remaining devs are oh-so-enjoying their time there..

1. workload has not changed
2. deadlines have not changed
3. no one will have Christmas-NewYear vacation
4. a new k8s-based infra is scheduled to roll out to PROD on Dec 23 (k8s is still far from ready - might need a few more months)

The most fun part is that it's not client's mgmt who has decided for #4 -- it's our own....

Boys.. Girls.. Save yourselves.

First two minutes in a meeting with new clients that hate devs.

Devs: Can we please get adequate hardware to do our job correctly? Please, just a new set of larger monitors.
Lower management: Sure, this is going to be easy.
Upper management: Wait what? This will cost us around 500€ times 10? Any maybe in the end other departments will want that to, so make it times 100.

We're a 4+ billion company ... but yes, please, I love scroll bars and they make my work so much faster.

Really loving the instant legacy code being added to our new project by devs who think they are too good to follow our peer review process, yum... today I found out that there are two different implementations of an API endpoint that does the same thing running in prod, in two different places, because the guy who wrote the second one wasn't aware that the first one existed and didn't let a second developer look at it before he pushed it to master.

Many people were hired to work on new product, but no one have told them that for one or two quarters they will have to maintain 20 years old project. I was ranting about this, but in the end accepted my fate, wiped tears with money and moved on. However one of devs took another path. When he was asked to work with .aspx and jquery 1.X instead of react, he just said : "Not going to happen" and left the building.

Being 25 and just now getting employable dev etc skills is really quite daunting when you learn of the old geniuses like Bill Joy, Linus, Wozniak and then hear daily stories of 16 year olds doing amazing things.
Inexperience in a field where everyone demands experience is scary. Still excited to see where I Can l can get though.

Dear JavaScript devs,

Can you please stop with using new Framework(); everywhere?

Sincerely,
A PHP dev

Happy new year, fellow devs!

I’m so fucking sick and tired of !devs telling me how simple a feature should be to implement.

Like motherfucker the most complicated thing you’ve ever done with a computer is attempt (and fail) at working with tables in Microsoft Word and you’re trying to tell me how long a new feature/K8s architecture/noSQL aggregation should take to implement?

A monitor cable wiggling loose paralyses you for hours but I’m supposed to bow down to your understanding of what is causing a bug?

I'm the kind of dev who is willing to overtime because I enjoy coding. But my previous boss (owner) abused this opportunity and thinks he can call me whenever he wants. After my shift, he would be surprise if I go home immediately and ask If I will be working at home. He even called me while I'm in vacation (he wants me to work on a new feature). I already filed my leave 3mos before that. He is very manipulative to the other devs and doesn't even trust his managers.

> Advice to new coders

Don't worry over picking language A or B.
Just pick A, use it for a month, then move on to B.
In a normal 3 year college degree you'll try multiple languages, some of which you'll never use again, and they'll each teach you something.

I had classes in Java, C, C++, C#, Prolog, Assembler, F#, JS.

Never used F# again and no one uses Prolog. But they were great for learning recursion and logic.

It's not like you take "a step down a bad path" if you pick a language you're never gonna use again.

You'll also learn new stuff on the job. We have one team that uses Go and one that uses Rust. None of the devs ever studied those languages. They were mostly former Java devs who leaned on the job.

New web devs don't know the struggle of using spacer.gif, nested table layouts, and vibrant "web friendly" colors out of requirement.

New business opportunity. Hire the worst, cheapest devs on the planet and get them to build a HR system.

Judging by past popular HR systems, it'd become a best seller instantly.

When I arrived at my new job last year they were working on developing a large site using a live server with all the devs ftp-ing every change in the build process to test it. 😵

It was not uncommon to hear 'is anybody in the style sheet?' being shouted across the office!

Needless to say, I had to fix many bugs multiple times when my fixes were overwritten!

You know what kind of devs I hate?
- The "Oh I never worked with it so its shit"
- The "I dont wanna learn something new"
- The "You can use JavaScript for this and everything else"
- The Pro ++ Ultra Dev who never heard of modulization and layering
- The hard coded values guy

Oh, it's finally done and works well!
Oh, let me just optimize that a little... And probably rename this...

5 minutes later:
Shit it does not work now.
10 hours of debugging later:
I'll fix it later

To all new devs:
Commit more regularly

Trying to investigate why the team of new Devs are reporting a particular set of modules is not properly maintainable, found this little gem at the root, written in 2014.

At my previous job, no matter how many times I explained it, "a jquery" was an image slider for by boss. No need to say new devs didn't know what the hell he was talking about when he said the clients wanted "a jquery".

Jesus, using vim in browser is such a beautiful thing, thought it's pointless.

Also, FUCK managers/bosses that change their technologies for no fuckin reason.
I didn't spend 1+ month to learn .NET core, which is a fine piece of tech and you suddenly come and say that we should move to PHP because the new guys you hired are PHP devs and don't know a single line of .NET.
I DONT GIVE A FUCK.
TAKE YOUR PHP AND SHOVE IT UP TO YOUR ASS.

I'm really excited to have a job where I'm not the lone developer. Kinda nervous, too. Now other people will see the crap I write. :P

NEW TALES FROM THE FUCKING CRYPT. It's disgusting...

... how managers keep to invest money into totally useless gadgets at the company to keep themselves motivated with stupid toys, tech and gear. WHY in fucks name would you not spend the money on hiring more devs and a dev consultant?

It's funny how they presented the stats first: "yea well we have ten big projects in dev right now" (we are FIVE FUCKING PEOPLE, tells you everything, right) "... BUT WE HAVE BOUGHT NEW SCOOTERS FOR THE COMPANY!".

Ok... why though? Who would actually use those things except the ones that bought them. Just another way of spending more money to reduce the promised employee return on the company's profit...

!rant, but some kind of story

I work as a lead dev on a gmod server of a pretty big german community. With the fun stuff, there come the duty‘s to help Jr. Devs or even help people get into Developing. The part, where you help junior devs is always fun, but what I find interesting is the part where you help people learn coding. It’s not easy work, but you learn more every “lesson”. I catch myself exploring and learning something new, even if I know the topic. For me it’s a new journey every time.
Not sure if there are many people who can relate but I just wanted to tell my side on it.

Nobody:

Overexcited new devs: JavaScript framework 178946252 is so awesome dude

😒

I fucking love my job. The boss just bought all the devs, QA and support guys brand new sit/stand desks and gaming chairs. Those chairs are so damn comfy! :)

What is it with devs (not all, by any means!) who don't understand networks or basic computer operation? I'm not talking about anything complex, but things like the dev who asked if his IP address could be whitelisted so he could remote in from home. We asked what his public IP address is and he said 10.0.0.27.

Or the new dev who started and said her laptop camera didn't work and logged a ticket, only to be asked if she had the camera cover open or closed and said, "oh, that's what that lever is for."

Don't get me wrong - many devs and sysadmins and IT people of all fields are excellent. And there are some who are crap in every field. This is no rant about devs in general, just *these* crap devs that I can only throw my hands in the air and think, well, they scored ok in the SQL test.

Hey rejection, my old friend, I’ve come to grips with you again. Because a technical interview with a question that I thought I knew, required the use of a structure that I didn’t yet understand. And that I planned... to study... when I was done with hash maps....

My current job at the release & deploy mgmt team:

Basically this is the "theoretically sound flow":

* devs shit code and build stuff => if all tests in pipeline are green, it's eligible for promotion
* devs fill in desired version number build inside an excel sheet, we take this version number and deploy said version into a higher environment
* we deploy all the thingies and we just do ONE spec run for the entire environment
* we validate, and then go home

In the real world however:

* devs build shit and the tests are failed/unstable ===> disable test in the pipeline
* devs write down a version umber but since they disabled the tests they realize it's not working because they forgot thing XYZ, and want us to deploy another version of said application after code-freeze deadline
* deployments fail because said developers don't know jack shit about flyway database migrations, they always fail, we have to point them out where they'd go wrong, we even gave them the tooling to use to check such schema's, but they never use it
* a deploy fails, we send feedback, they request a NEW version, with the same bug still in it, because working with git is waaaaay too progressive
* We enable all the tests again (we basically regenerate all the pipeline jobs) And it turns out some devs have manually modified the pipelines, causing the build/deploy process to fail. We urged Mgmt to seal off the jenkins for devs since we're dealing with this fucking nonsense the whole time, but noooooo , devs are "smart persons that are supposed to have sense of responsibility"...yeah FUCK THAT
* Even after new versions received after deadline, the application still ain't green... What happens is basically doing it all over again the next day...

This is basically what happens when you:=
* have nos tandards and rules inr egards to conventions
* have very poor solution-ed work flow processes that have "grown organically"
* have management that is way too permissive in allowing breaking stuff and pleasing other "team leader" asscracks...
* have a very bad user/rights mgmt on LDAP side (which unfortunately we cannot do anything about it, because that is in the ownership of some dinosaur fossil that strangely enough is alive and walks around in here... If you ask/propose solutions that person goes into sulking mode. He (correctly) fears his only reason for existence (LDAP) will be gone if someone dares to touch it...

This is a government agency mind you!

More and more thinking daily that i really don't want to go to office and make a ton of money.
So the only motivation right now is..the money, which i find abhorrent.

And also more stuff, but now that i am writing this down makes me really really sad. I don't want to feel sad, so i stop being sad and feel awesome instead.

Solo Android app developer here. It's 4AM where I'm working. Been working alone on a project for the last 20 days. Looking to get some inspiration and discuss new ideas with other devs.

So hi!
What's up with you? What do you do?

Developers are supposed to be eager to try new stuff, however most devs on devRant prefer to hate on Edge and hate who use it.

I'm not here to defend Microsoft but I bet 95% of the people that hate on Edge haven't tried the latest version.

It's really easy on weaker hardware and on battery life. Try using an old ultrabook (2nd gen i5) as I did for some time while using Chrome or Firefox as your main browser!

New phone after 5+ years and it's fucking awesome.

Successfully avoid American and Chinese stuff by going with a Korean brand.

And I fucking love Android. The kind of feature advancement that has happened in past so many years is outstanding.

The amount of customisation options available for the users are beyond one can utilise to fullest.

And my favourite feature is dynamic lock screen pictures every-single-time I unlock. I fucking love it. Makes me cheer up with joy. Very similar to Bing Wallpapers for Windows, but more dynamic.

Lately, I have been hearing from Apple users, that iPhone lacking a ton of basic features, apps not supporting functionalities, and we all know the overall advancement in Apple ecosystem.

While this post was more about sharing my experience with my new phonw than iPhone comparison but let's face it, the reason Apple went bonkers with the first iPhone launch was the app capabilities which led to a larger developer community building apps for iPhone while Android wasn't even born yet.

This is where Google is trying to capture the market now. More devs > more apps > more users > more devs and repeat.

Is it wrong to expect some widespread documentation from a $350 billion company to properly document a key part of their upgrade path for a new SDK version? beware any Android devs upgrading from API 3.X to 4.X on the Facebook SDK.......you'll want FacebookSdk.setLegacyTokenUpgradeSupported(true); before your call to initialize.....

Positive story ahead.

Had to try and make a new system on my own in a company with no tech staff. I was scared shitless of the responsibility. About a year later we got 2 new devs and people are somehow paying for our very flawed and incomplete mvp.
It's fulfilling and fun. Taking something from zero and suddenly having an actual application with customers.

The other 2 engineers are fun and we talk shit while coding and teaching each other. We also study new tech every day to keep getting better.

I'm even getting some stocks soon.

Long road ahead but honestly, life's good.

There are indie devs which still builds games for the NES or the first GameBoy... and then we have Apple which goes to extra lenghts to ensure which nobody can develop, publish or install new apps on devices which are too old for the newer iOS versions.

(Hopefully this is the meta rant to kill meta rants)

I'm fucking sick of devrant.

New users posting shit memes with the wrong tags.

But worse are old users complaining about said new users, or just beginner devs from other sites

Yes, some people need stack overflow every 5 minutes.
Not everyone has the capacity to understand every documentation.
Not every documentation is updated or entirely correct.
Not everyone has more than a year or two of experience.

Don't be part of the dumb circlejerk. Just complain about your bullshit boss, coworker or tech.

Hi guys, I'm back!
I spent some time not using DevRant, I got a new phone and thought it would be better not to install it for some days. I had to do a lot of stuff for school these days and didn't want to geht distracted by amazing devs posting cool rants. So here I am, happy to see you all again. (Or at least your avatars)

Yesterday I had another job interview. This time from home via Skype. Today I was blown off. I was not technical enough according to the company.

This company was working with an ancient cms nobody ever heard of and made Sass sound difficult and new.

Good luck in the Stone Age fellow devs. Make sure you upgrade your pc to Windows 7.

A 'senior' dev just questioned us (by question, I mean scold) when I suggest writing some additional information regarding db patching scheme of our project on our Wiki, just thought it might be useful for other possibly new devs later.

Apparently that would be 'spoon- feeding' them and it is totally NOT GOOD.

Smh.

It's depressing how much time I spend asking, begging, demanding, and pleading for the older devs on my dev team to follow simple naming conventions. And every time I ask, they act like it's new information.

I was doing code reviews for some of the new Devs recently joined... One guy wrote his entire life history in the check in description... Like Why he took this approach, why interfaces are necessary in coding, when did he lost his virginity (I doubt he ever did), what's his pet name? - sadly no information related to his online banking... Shame really...

I see a trend for new devs to want to focus on JavaScript while dismissing relational databases and backend languages as boring and to rigid. A week into real jobs they want help with data and .net.

For you game Devs out there,

There should be a UE 4.20 this year... Gives a whole new meaning to baked lighting 🌿💡

Devs knows everything (even new technology) syndrome by managers

This wanker approached me via LinkedIn before new year to be team lead to a diverse team of devs spread over a few time zones.

The mission? Build a metacritic clone, but geographically constrained to New York.

Me : How much are you offering?

Him: <radio silence>

I wish more workplaces realised how stupid it is to quibble, argue, debate etc. about stupid things like buying Devs intellij licenses. I mean sure, we'll throw a meeting to discuss it, argue back and forth, ignore questions about why the sales guys always get any new tools they want, and then waste more on meeting time than the damn license would have cost... Great idea...

I still do exist, long time no see, fellow Devs! How is it going?

Didn't posted here in long time. Anything new relevant? I just started studying at an university. Hoping to post again here.

Companies try to find young devs, less experienced but more openminded and flexible.. do you think we will still find some cool sobs when we're > 40 || > 50 years old, even if we keep up with new technologies and stuff?

Never thought about it until now..

boss said: "we need create new version of our software. copypaste old version in new branch. so we will have dozens of versions and all of them online and working."
my question: "what if old bug will appear in all off 100500 branches? we will need fix all the versions of bug in different copies we have modified!"
boss said:"c'mon when we will get this problem then we will think about it. all the devs in world working on many versions. its easy."

your opinion?

Working on Ruby on Rails for first time..
Blogs mention it's more human readable..
I guess I feel like semicolons, args and braces to be more readable...

Hey devs! I'm new here and I don't know any people on this network, wanna talk about things?

Got some new coffee, Trung Nguyên from Vietnam. Now that's some in-your-face coffee! Strong and interesting taste, slight cocoa aftertaste. Only recommended for hardcore devs.

This happened a few years ago. We started this new project that was estimated to take 3 devs around 5 months to complete. We had a meeting where the client, the project manager, me and two other devs were present. When the client asked if we were still on track to complete the project by the end of September, the PM just said “yeah we are totally on track, no worries”.
Me and the other devs looked us straight in the eyes and nonverbally agreed that this guy has to be sniffing glue or something. For context: it was August.
After the meeting we immediately raised our concerns with him and our boss. The deadline was shifted and a freelancer was hired to assist. The PM quit shortly after and a way more competent guy took over. But the damage was already done.
In the end we finished that project in February or March the following year. Client was still happy but this shit triggered a whole clusterfuck of a year. Other projects were lagging behind because of this and we had to push out project after project that had accumulated in our backlog.

I have never understood why there is so much animosity from seasoned devs in the community.

I see it in a lot of places. Stackoverflow, reddit, even devRant. In so many cases, an inexperienced dev will post to the web, only to be shot down by things like "this question is stupid" or "you all have it too easy and its apparent you never learned basic CS principles" or things of that nature. In a lot of cases, these are generally unhelpful replies and often teach new devs to be wary of seeking help.

Please help me to understand, why this is.

Is it because the community is angry at these devs trying to get a high paying job by going to a bootcamp and shortcutting the hard work it takes to understand core CS principles to become a decent developer? Then why not take a moment to provide resources or insight to these folks so they can learn to be better?

Is it because the community feels that devs from bootcamps are just watering down the pool of talent making our worth decrease? I feel this isnt really valid because seasoned, experienced architects will always be needed to build good software. And at that, why are we not ensuring that the next wave of developers is equipped to handle tasks like that?

There are a lot of good people in this community who want to help and make the net a better place for all developers (after all, many of us consider it home), but there's a lot more people out there with really shitty attitudes, and it frustrates the hell out of me that my juniors now equate arrogant, self-entitled responses and attitudes with "seasoned devs" and discourages them from even bothering to get involved in the community.

Starting up the new Java project I'm assigned to.
Just to see that this project is made of pure black magic and tears of forsaken devs.
Crashing the jvm with segfaults on a regular basis is just one part of the magic.

Now I understand why no one volunteered for this project...

Got a promotion and had a loose definition of what my new tasks were. I got overwhelmed with being the go-to for project and account managers, and 75% of our devs, on top of my own work I had to complete for clients.
Eventually I wrote up a 2 page document of things I had to deal with daily/weekly and how I don't have time to do my work, so why should I even bother to do it.
We got it resolved, my boss took some of the tasks off my plate (like training the new hires) and allows me to work from home whenever I need to finish up work.

My fights with other devs always revolve around the position of curly braces:

Should they be on the same line or should they have a whole line just for themselves?

I mean, if they go on the same line you have less lines of code and you can fit more into the same view, but putting them on a new line makes it all a little less messy

So I landed a senior linux admin job in August, moved to a new city, and signed a 2 year contract for them to pay my moving expenses. I took an employee survey in October, not knowing anything. As a department (all ops and devs), we reviewed the results as a whole with HR.

Now HR is coming to our remote office tomorrow (4 hours away).... to be continued...

I took a bit of a break from devRant because I was way too disgruntled at my current position. Flash forward and I am now a manager at the same company.

Note to new devs:
Make waves, make tons of waves. Get the attention of your superior’s superiors by making things better. Never rely on your superior relaying information, they only have their job security in mind.

My job. Working in a small IT department. Web programming most of the day and being able to help people with their phones, software, internet connection, and so on...

The only thing I sometimes wished for were some other devs in my company that would understand me and my problems and with whom I could discuss new technologies.

But now I got devrant. I'll be fine from now on.

Hated function naming in python, because some functions are like "dothisorthat", some are "do_this_or_that", some are "doThisOrThat", some are, I don't know, what new technique of naming would python devs invent in the near future. Honestly, these naming creeps me out

Had a feedback meeting with one of my senior devs today, it went really well and allowed me to get a new view on some things, like some common behavior patterns I do. Really happy about it :3 If you didn't have something like this yet, go for it, it's definitely worth the time ^^

Why do I have a hard time finding a new job when senior devs are not only changing the data model, but naming keys "key" and "value"!?
"Oh look, a SQL error."

We have so much pl/sql at our company and it really sucks because the "young" generation of devs must convince the pl/sql guys to switch to some more powerful and newer languages like java.

But not everyone wants to use the new stuff or learn anything new. I mean there are some programmers who really appreciate that there is new stuff. They have no problem learning from the younger generation. But some of them just resist any change in that direction, and thats the much higher amount of devs.

Does anyone of you have such experience? What can i do against that?
Is that some kind of "i am too old for this"-trip?

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

Best wishes for the new year. Happy 2017 fellow devs!

How can so many devs have NO FUCKING CLUE what DNS is or how it works

FFS the amount of times ive had to tell devs to clear their dns cache when the browser tells them right in their fucking face a nxdomain error after deployment of a new test system and they just come screaming in confusion why its not working is entirely too high

When you find out all of your new fellow web devs are all from boot camps, and you spend more time teaching them than getting your work done. New job time maybe?

Please tell me why my boss thinks instead of just implimenting a language picker, it's a good idea to:

1) store the browser's language option in the DB only for new users, but only the first time they log in, never again.

2) never give existing users the ability to change language, and just default them to English.

3) deal with all upcoming language change tickets by having devs manually do DB updates ON THE LIVE PROD DB.

I'm screaming.

God I hate it when devs complain about not having a decent job 😠 And then they're like "Oh, I've been looking for the past 6 months, but every company just ignores me"

Look, hate to be the one to break it to you, but companies are constantly searching for devs, and many companies have such shortage of quality devs, they'll take just about anyone with even remotely relevant skills as long as they have a decent attitude. If you can't find a decent job in this market, well, it's either that nobody needs a dev who spent the last 10 years doing basic UI and simple NodeJS apps, or they don't want a dev who loudly shits on new technologies while acting like their GitHub profile is impressive enough.

Hey fellas,

So, our company is taking up some consulting projects to survive this pandemic since our main business is a little down. I've been assigned to a RN project and the client company has 2 other devs. Those devs are so incompetent that they don't even know the basics of JS and RN. They don't even understand how to split code into components and make it resusable. Okay, fine they must be new devs. I get it but can't you even fucking follow the instructions and guidelines that I'm giving you!! The code is very bad with a lot of pitfalls. In the first 2 weeks I reviewed all the code they were writing and gave comments for improvements. They didn't even care to do that! Now I've given up!

Every single day looking at the codebase makes me sick and not want to touch anything. I've practically started hating the project. How do I deal with this situation? Now, we are reaching the deadline and they're piling up the work on me. Any suggestions on how to handle this?

Thanks!

P.S: This is my first actual rant!

One of new junior devs after his 3 month "trial period" was good enough to keep him so he went to boss to talk about his future.

He came back with big smile and told us how much of big raise he got (now earning as much as seniors)

I asked my boss what was so special about him, maybe we should improve somehow, he answered "He was yelling at me, what could I do?"

Now I know how to approach him next time I talk about a raise :p

Currently working on a new project with a group of people, (about 8 guys, no ladies 😒).

Anyways, out of the eight, there are only 3 devs, 3 designers and 2 main idea guys. I'm a member of all 3 sets and to top it of, the other designers don't know what they are doing.

Life is beautiful, fucking beautiful.

Happy fucking new year my fellow devs!

Everytime I face a new bug, my innerself tries to convince me that I can never find a solution to this.
But my gut feelings know that sooner or later I've always found a solution.

Thanks to all the devs sharing their problems in the internet.

I've said it before but for the sake of new devs, never ever force push to fucking master.

Devs who use the array map method for purposes other than generating a new array, and who use an empty return statement to satisfy the linter, should receive a slap in the face. A gentle one, but a slap nonetheless

How do gophers (Go devs) feel about the new Go logo ?

I can get used to it but it feels more like a logo of a company that might rival Uber.
The gopher gave it an easy to use and understand feel, this new one gives a fast and sleek look. It wants to showcase "Fast" more than anything else.

Please share C++ advice for devs new to the language. What do you guys think is the fastest route to self learning C++ development for infrastructure systems and please suggest resources.

> client finds a plugin
> devs implements the plugin
> client finds a new plugin that makes the same than the last one
> devs begin to question client ideas

Happy New Year From Singapore!
In this year,
May all the Devs out there be able to code peacefully everyday without being disturbed by that annoying coworker.
May all the Devs out there be able to get clients who understand our pain.
May all the Devs out there be able to work on the projects that they love while getting paid proper amount.
Cheers! Love live devRant and it's community.

Happy new devs 😉

Some common themes I have observed:
1. Why is this API using XML? It should be JSON.
2. Why are they using old shit? It should be new shit.
3. Why are they mixing new shit with old shit?
4. Why is the technology being used not fitting my sense of perfection and order?

What happens when JSON is the old shit? What happens when a new format is adopted that solves some corner case issues with JSON? What if those corner cases were solved by using XML, or a mix of XML and JSON? What happens when all the new shit is the old shit?

We will still be using the new old shit and listening to fucking noobs complain about mixing, matching, and abusing everything ever written. Oh JSON, how quaint and limited. Why did anyone ever use that? Fucking senior devs...

So a product manager emailing devs long essays on requirements? how does that sound? Aren't developers just supposed to implement the specifications? Is requirement gathering and design their job too? Maybe I need a new job before I go crazy.

Got our snazzy new HP Elitebooks from IT. Nice lil laptops.

Guess how many apps they installed for us off the list of "Applications Devs Need" that was submitted with the original request that they asked us to provide.

Goddamn 0. 0 Apps installed. ”Instead here is admin access, install what you want.”

Being a PC guy I don't mind setting up a new environment but things like Office365 and Adobe CC could of been installed for me, I don't have the licence info offhand so now I gotta bug IT again and why ask for a list if your not going to install any of them?? Ugh. I don't have time to sit here while Adobe installs the whole suite....

/rant

What's the first thing you install on your new PC? I find I grab ConEMU first.

Every. Single. Time. I've tried to learn and implement proper Unit/Instrumentation testing, the main Android devs decide to go for something else or introduce some feature or Gradle plugin that breaks every tutorial out there. I find it way easier to just test everything manually than learning the new yearly trend. Am I the only one?

I'm currently working as a full stack web developer.
Now to my situation. Me and my team partner are part of a bigger dev department. My department lead now wants to split his responsibility into smaller groups. All groups get a new lead out of the group of devs except mine... No let's put together web and hardware development. It's not like I already coordinate all web and app related stuff. But hey let's hire a new guy for this... Hopefully someone with the same knowledge of the web as my current lead... Like none...

Finally.... After 3.5 months of serious job searching... I start a new job on Monday.

Even a few months ago , finding a new gig in mobile development was very fast - 9 calendar days from initial search to sitting in a new desk was my personal record. But a couple of weeks was pretty typical

What happened? Was there a huge influx of mobile devs? More H1-b visa holders? The competition seems like there are far more developers

Anyway, happy to be sitting in a new desk on Monday

A whole bunch of new features were added mid-sprint without ever consulting any of the development team. They dogpiled on devs from other projects who had no prior experience with the code base, so naturally I lose traction because I'm tied up answering questions and explaining things.

This sprint I'm not getting any feature work done as I'm stuck fixing bugs and awful half-ass implementations (by well meaning devs that were thrown at unrealistic expectations).

Concerned at the burn down rate, next week they're planning on dogpiling on more guys to play catch up.

I'm so sad

I don't have to deal with this, cuz I know I am shitty dev..
I get the job done, most of the time better than the previous devs on this project.. but if you drop me in an entry level interview, I know I'd flunk it.. big time.. I don't have the necessary theoretical knowledge and my terminology sux..
Was discussing new hires with my boss and he was like wtf you're talking about, you're a senior.. I'd consider myself a middle at best due to lack of theoretical knowledge..

Had junior devs work on a new feature on a project I spent days fixing. They spent days on the new feature but built it off of the broken version of the project and never pulled from the repository. Now when I merged their new feature onto the working and correct branch, their feature is all broken. I swear Im going to kill them all.

(Not a rant)

New to devRant :^)
Tell me the reasons why you started programming.
I want to know since there are so many devs out there..

!rant
We found our new boss! (although not evil)

Have a great weekend devs, remember to enjoy it!

Hello, I am new on devrant.

Trying to finally land a job after studying for so long. I must say that for a lot of interviews their questions are quite unpleasant and after interview itself I often feel like an idiot. Guess it's not my thing to communicate that much.

If there are any other devs shy/with an introvert personality: How did you overcome stress and later initial uncertainty in new job?

!Rant

All Devs in the room!! Have a happy, healthy, prosperous, safe new year filled with joy.
Happy coding!!

Fuck it. Two big releases plus all the minor shit raining down on our team with only three active devs. A new team member who's unfortunately more of a burden and nuisance while the whole ship burns so beautifully....
And stupid me? I fucking break my arm, is in a cast now for four weeks. So I can mostly watch, while everything sinks.

Learnt a lesson today:

Never try out new hotkeys in a SQL query editor window.

Or if you do, at least make sure it's not connected to anything important :)

I was trying out new hotkeys and accidentally executed a SQL deploy script to rename something in multiple stored procedures in a large system.

Thankfully - so I saw after my heart stopped - it was only our QA db so not too bad, just a couple of devs set back.

Who woulda thought ctrl-l would execute :O

Visited a friend at their new workplace. Awesome office, really cool interior, nice people, devs are working on cool projects. Started to feel pretty envious.

Then we felt a rumble. Well, it was more like a rrrrruummbbble. Turns out they are located right next to a train track and the whole building shakes a bit when a heavy freight train goes by.

Guess who isn't envious anymore.

Gentle note to aspiring devs, that SO is not hacked. It just their new 90's theme design (More to come).

Search for history icon beside search bar to toggle to normal(Modern) view. Stop Panicking!

Happy New year fellow devs!!!!

May it suck less than the previous one!!
And may we all get what we want :)

I start my first "real" job on Monday. I will be one of roughly three new junior full stack developers on a team of 15 senior devs. The company has a casual dress code and they allow headphones. What should I expect? I want to grow and I don't want to be a nuisance, I also want to earn a reputation and become respected when I do have something to say.

Do we have any C# devs who have switched to Scala?

I've got a very sweet job offer... at a company that develops in Scala. On the one hand, I'm pretty pleased with my depth of C# knowledge, for a variety of reasons. And I've been targeting .Net shops in my job search.

They know Scala devs are rare, so they are aware they need to train new employees, which is nice. But I don't have strong opinions yet on whether this is a language I want to pivot to.

Does anyone have any thoughts/opinions/experiences?

Last month, I learnt Docker via the 1 hour crash course of the YouTube video.

Now, I don't remember all the content of that video which made me think that I should start making notes.

I understand the basic fundamentals of the Contanarization and a couple of commands.
But I still feel like I'm lacking the whole picture of the docker.

I wonder what other devs do to learn new tech and also about note taking habit for revisions.

I'm so sick of devs not caring what happens after they push their code. A new feature was released on the front-end two weeks ago but the backend was never deployed. It's been logging errors for 2 weeks now.

I know I'm equally at fault for not noticing but I feel like the only person that ever notices things like this. I also discovered a data issue today by looking at the error logs.

How can I get my teammates to be more invested in how the service runs live?

First post yay!
I'm a "tech" lead for my team. The "tech" stands for technically, I can go on a whole different rant there but that's not why we're here today.
So we have a new PM on our side and a new PM on the client side. I've been working on this project longer than any of the devs and PMs have.
One of the tasks that my team does is validate and ingest data. It's pretty straightforward and it's fully automated. It takes minutes, and at most an hour, to complete this task. We get these tasks from users randomly and they don't have any schedule to it. It's FIFO basis and we just add it to our current sprint if we have bandwidth or add it to the next one if we don't. Not a big deal, no users have complained about it before, it's just business as usual. And we have a tracker of when we received it, how big it was and when it's been ingested. Super simple.
So now comes in the new client PM. He's been asking us to come up with timelines for these ingestions. My project's new PM is bending over to him and saying okay we'll come up with it, no problem. Well, there is a problem. We don't know that far in advance for when these tasks are coming in. Even if we did, now we're supposed to create timelines for a 10 min task? It literally is uploading a file and our system handles everything and I've explained that to my pm but he still is like well that's what they want. It takes less effort to do the ingestion than to make these timelines. It just means project managers bothering devs about timelines.
Idk how to deal with this. Thoughts? Any similar experiences?

The Web 3 has coming and I really love that. The descentralized web is a new way for the devs. Some projects was started, like: Patchwork built on SSB protocol (Secure Scuttlebutt), Dat Project wich create the dat protocol for share files in P2P network. Someone has started same project into the new web?
P.S.: All projects before has built in Node.js/JavaScript

Seriously guys, how do you deal when remotely collaborating with lets say not the most motivated and competent devs?

Our scrum team got formed about 6 months ago from leftover devs of other teams, choosing a couple competent devs at the core and other devs who were kinda gotten rid of by their old teams, and after 6 months of working together I can see why.

Situation is that we are 7 devs in our team and 4 of devs are not pulling their weight. They are seniors on paper, but in reality not really.

They rarely take something complex to work on and even if they do, they make sure they take as much time as possible. Two of them are contractors who I imagine decided to treat the job as a paycheck and nothing more. There is no initiative, no push to make things better and in general attitude is to do bare minimum: only what is being asked and then delaying the hell out of tasks.

Im not exaggareting: Im talking about every possible way of dragging out the tasks: delaying communication, sitting around for a few days while not asking for new tasks to work on if they are blocked, also avoiding standups. Working for days on very basic comments in their MR's. Getting "sick" for a couple days on deadline when things get tough, so that someone else would come in, refactor and save the day. Once or twice it could be a coincidence, but nowadays I can already guess ahead of time what kind of trick they will pull now.

Our project is an android app where we have to support few different tablets, so the most recent new trick that I witnessed is devs avoiding hardware delivers, sometimes for months. Idea seems to be if you dont ping your team that you dont have hardware, then you can avoid working on related tasks with that hardware.

Worst part is that they get away with it. Our teamlead is a senior dev who is first time teamlead, doesnt code anymore and doesnt want to rock the boat. He is the type of teamlead who sets arbitrary deadlines, makes it sound that they are urgent and takes a few days off in the middle of chaos just before deadline. Restrospectives don't help at all and if I try to bring up stuff directly to him he tells me to bring it up during retrospectives. We discuss issues, rant a bit ant then continue carying on like nothing happened and nothing changes.

So little by little in the past 6 months we came to this point where 2-3 devs are carrying the weight of the team and are in a constant crunch mode, while others are allowed to slack. Its becoming ridiculous.

Problem is that this is starting to affect our morale. Only way that is left to keep my sanity right now is to pull away sometimes and also slack. Then I come back at full capacity, give my best for a couple weeks until I have to go and fix some basic leftover task that has been purposefully dragged out for 2 months and left unfinished, then I just want to scream and I know that its time to disconnect again.

Devs are the new Working Class Heroes

I always thought wordpress was ok, not great not terrible, from a coding perspective. Now every new framework I have worked on makes me see why Wordpress is on 40% of the internet.

Now I love wordpress not because of what it did do, but because of all the really stupid things it managed to avoid doing including: over abstraction, trend chasing, using "new transformative technology" that disappears in 2 years, breaking plugin economy with updates and making devs start over, making everything OOP for the sake of making everything OOP, making adding on a bit of code take multiple files of multiple formats and boiler plate code, boiler plate code, compiling dependencies, composer, twig, laravel, one page applications, react, angular, vue, javascript only stacks (MEAN), not letting you control sql queries, protected/private scopes and design that doesn't let you fix or alter bad code others did, and the list goes on and on.

Wordpress did a lot right, and devs should try learning from it instead of making more problems to solve. Sure it's not elegant, but you known what it does do? Focus on a solving a problem. Then it does. Without inventing new ideas or concepts to inject into the code and create new problems.

And you know what else? Hooks are actually very well implemented in Wordpress. I've seen it done much worse.

Honestly my main gripe with the entire platform is a slow moving to OOP for no reason and the database design should separate post type into different tables, the current design makes it less scalable for large data sets for multiple reasons so I'd fix that.

hey linkedin!

hey linkedin!

hey linkedin!

"you have one new message!"

no i don't you stupid fat fuck slimeball garbage idiots - btw your devs suck and you as an organization suck

these type of lying emails have to be illegal somewhere right?

like something the clowns i used to work for would have concocted... good amount it did for them, they are unemployed, and at least i have my income from my meager saas products / savings (they are gen z, probably don't even know how to spell the word "savings")