Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.

(Q: How much are you allowed to Google as a developer?)

“You’re allowed to Google as much as you want. This is not school, you’re employed to solve a problem. Nobody cares whether you Google for the answer or remember the answer from another Googling.”

Not my mom, but my girlfriends grandmother. I told her that I am a software developer, a guy who makes the programs which run on computers.

She became really excited about that, because finally she found someone to repair her 40-year-old radio. I told her that I have no fucking idea about radios, but she did not want to hear that. So I looked at the case, randomly pushed some buttons and again told her, that I could not find the broken part, let alone repair it. But she didn't listen and told me to open the case and look inside.

Sighingly I opened the radio, looked at the inner parts and told her once more, that I don't know anything about this stuff. She told me to look more closely. About to lose my mind about this pointless task, I finally told her, that "the transistor" is the problem and that the best thing she could do is to throw it away and buy a new radio. She was happy with that answer.

Tips for all the programmers out there:

- A programmer is not a PC repair man, just no one seems to remember about that

- Programming is thinking, not typing.
Counting starts from zero, not one.

- Even after completing a degree and courses and working on IT projects, learning never stops. If you want to stay competitive you should also work on personal projects that force you to use languages and software you never work with on the job.

- You don’t need serious math skills to be a developer. However, you’ll need basic algebra, logic, strong problem-solving skills, and most of all, patience.
- You don’t need a degree to be a developer - programming is like almost any profession: if you’re good at it, people will pay you for your skills, regardless of how you got there.

- Sleeping with a problem, can actually solve it.

Most technical issues summed up in one picture!

I was at my uncle's village.
Where getting internet is big thing,very far from main city.
I was talking with one shopkeeper.
I told him ,I am software developer.

He ask me questions that
"How can I improve my business using software?"

To help me figure out situation.
He told me problems he is facing right now.
Accounting/inventory management/contact's with big retailers.

He was so genuinely explaining it.

He don't want next billion dollar startup.

He want to solved his problem.

I am really impressed after that conversation because person who don't know what is excel is talking about ERP software.

I am going to develop that software.

#respect

This pro developer in my work just made me look like a fucking useless potato today. Although he was really nice and made me understand what the problem was.

Damn man, he knows too much 😓

Phone call...
Caller: we contact you to arrange an interview for Java developer position, what time is good with you?
Me: Sorry Sir, I am javascript developer not Java developer!
Caller: You mentioned in your CV that you are using Java and Ayax for building applications!
Me: Trust me Sir, I don't have any relationship with your Ayax...
Caller: No problem, we can discuss this small technical difference in the interview. When you are available for it?
Me: No Sir, I am not available.

I'm 54 y.o.

I think I'm completely outdated in my skill, as in the last 14 years, I worked on a specific business problem, with an old technology: a JSP application + javascript + postgres.

I do understand software development, agile, web application development, linux server, basic/moderate AWS skills, etc.

Now they laid me off instead of including me in the evolution of version 2 of the software. Maybe covid, company had almost no cash-flow. Well they have now...So basically they fired me to find money to rewrite the application.

I feel without hope at my age.
I'm a generalist.
I can understand fairly well everything you'll throw at me, reactnative, angular, nosql, python, but I have little first-hand experience.

I don't have a lot of management skills, even if I've given frequent presentations to C-roles and board, and I implemented a whole agile methodology in my team.

I don't know what to do.
The amount of technology to study is huge nowadays. When I was younger I could get away with some php and java.

Full-stack developer is a big word for me. Maybe I could handle a full stack web application, but not from scratch.

I feel at my age, I'll compete with 20-something guys with better skills and lower salary requests.
I don't think I can pull a night anymore.

I'm trying to shoot high to management positions with no much success.
I'd like to go on developing, I know that there are 50-something developer out there, but who managed to find a new position at 55? at 60?

As soon as I finish the few money I spared, I'll be on the street, I'l be the "website for food" guy.

Started university of applied sciences to become a computer engineer instead of a web developer.

Met a lot of kids that are in the "computer studies = games + YouTube".

They struggle hard, but don't do anything to learn...

Then there's this classmate, the guy is 10 years older than me, is trying really hard, and struggles a lot.

I've been helping him out with assigns by asking questions, and he asks me how to solve a problem in general, not the assignments which is super refreshing to see someone that wants to learn.

Currently trying to help him "translate" the simple stuff into c++:

So, if you want the char at a certain position in a string, how would you tell me to do it?

"well, take the list, look at position x and bam its done"

Try writing it like that!

And instead of "[i]" he writes "stringvar[i]"

He really appreciates the help and I hope he'll get the mindset soon :)

Would hate to lose a motivated guy when there's so many idiots copy pasting everything from tutorials...

Please don't make junior developers feel they're a burden.
Have you ever googled "how to mentor junior developers"? It's quite mind-blowing how many articles, talks and panels are on this topic. And yet still junior developers are not feeling welcomed in their companies.
Yup, you guessed it, we also have something to add (based on our own experience):

1. Asking for help is not easy. Please don't blow juniors off by telling them to read docs when they ask a question. Always assume they've read it and did a sprint to solve the problem. They ask you, because they see you as a mentor and really need your help. If you can, spend more time with them and guide through the entire problem solving process.

2. Please don't think "I learnt it this way so you should too". If you're in charge of teaching a junior developer, don't expect them to be a carbon copy of yourself. Because even though in your opinion your approach is more "pro", they might not be there yet to use it properly. And last, but not least:

3. Of course, juniors will compare themselves with seniors on their team. And there'll be moments they feel so guilty and so afraid that they cost the company too much, that they need training, and supervision, or are between projects and are not bringing in any money, and they'll fear that their company regrets hiring them. Make sure they don't feel like a burden. As juniors, we often
have this misconception what is expected from us.

Dear tech companies, please set very clear expectations and tell your juniors you're happy. Don't get us wrong here. We don't expect unicorns, roses and pats on the back from companies. We do understand- this is business, and at the end of the day we all are here to make money. To do so, companies need to make smart investments. Junior dev with a great assistance, planned support, and a clear training program will become a great asset. It really is as simple as that.

So the job was for a web developer, specifically.
We needed a person who was very confident with PHP, JS, HTML, CSS.

This dude comes in, he says he's confident with all of them, we ask him how he would solve a problem we're having and he answers just like we answered the first time. Which is a good start.

By the end of the interview, he just says: "ok, but like I'm not here to work as a developer"
"WTF are you even here for, then?"
"To work on anything else than that"
"But we just need that"
"I won't do it"
"Ok, then, bye"

1. There are 10 types of people in the world: those who understand binary, and those who don't.

2. How many programmers does it take to change a light bulb?
None. It's a hardware problem.

3. A SEO couple had twins. For the first time they were happy with duplicate content.

4. Why is it that programmers always confuse Halloween with Christmas?
Because 31 OCT = 25 DEC

5. Why do they call it hyper text?
Too much JAVA.

6. Why was the JavaScript developer sad?
Because he didn't Node how to Express himself

7. In order to understand recursion you must first understand recursion.

8. Why do Java developers wear glasses? Because they can't C#

9. What do you call 8 hobbits?
A hobbyte

10. Why did the developer go broke?
Because he used up all his cache

11. Why did the geek add body { padding-top: 1000px; } to his Facebook profile?
He wanted to keep a low profile.

12. An SEO expert walks into a bar, bars, pub, tavern, public house, Irish pub, drinks, beer, alcohol

13. I would tell you a UDP joke, but you might not get it.

14. 8 bytes walk into a bar, the bartenders asks "What will it be?"
One of them says, "Make us a double."

15. Two bytes meet. The first byte asks, "Are you ill?"
The second byte replies, "No, just feeling a bit off."

16. These two strings walk into a bar and sit down. The bartender says, "So what'll it be?"
The first string says, "I think I'll have a beer quag fulk boorg jdk^CjfdLk jk3s d#f67howe%^U r89nvy~~owmc63^Dz x.xvcu"
"Please excuse my friend," the second string says, "He isn't null-terminated."

17. "Knock, knock. Who's there?"
very long pause...
"Java."

18. If you put a million monkeys on a million keyboards, one of them will eventually write a Java program. The rest of them will write Perl programs.

19. There's a band called 1023MB. They haven't had any gigs yet.

20. There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors.

I'm a new developer. Here is the top advice I've received:

0. Think like a programmer, outside of work too.

1. Programming is tough. It takes a certain kind of mindset to sit in front of a monitor and think it through a problem till the end. Develop that mindset.

2. Handwork pays.

3. Do it for fun. Be exceptional. Money will follow.

4. Care about the craft you build. Write such a beautiful code that your fellow devs would think about your code and have a nerdgasm.

5. Simple is beautiful. Anybody can make things complex. It takes a stroke of genius to make things simple.

6. Write modular code. It makes your code reusable and easy to maintain. Future developers who will work on your piece of code will appreciate it.

7. Share your knowledge. Unlike materialistic things, knowledge grows when you share it.

8. Add comments. You think you'll remember why you wrote that piece of code that way or a clever hack you created but trust me, you won't.

9. Be humble. You'll never know everything. Don't hesitate to ask for help.

10. Writing code is exciting! Of course there will be some frustrating moments. But don't give up! You'll miss a lot of fun.

Man, we have a snake in our company.

This snake is responsible for terrible code. They oversee a offshore team, but hold them to no coding practices. They don't do code reviews or checks. They let them be lazy and get away with sloppy work every time.

And if you critize their team - they will defend them and get angry at you. You can't adress the problem because said snake is always around. He's in a senior position for giving our company cheap workers, doing years of damage to our product while the non-code savvy managers remain blissfully unaware of their product being ruined in the background.

This snake is the senior product office. He has a share in the company now. He is from the overshore team's country. That team now has their claws so dug into our companies roots and are just pumping lsd's into it constantly. Feels good untill you die from an overdose.

Here I am, the new junior software developer, trying to tear out the claws that have sunk into these roots. Im up against the snake. The snake hates me. I hate the snake. I am trying to open the eyes of the managers. They hate that. They want to silence me so I don't expose the awful, unprofessional level of work they do.

Well, that's too bad. I won't back down from this, snake.

When you show the senior developer your clever solution to a problem and they come back with "you can also do XYZ" and his solution is much more elegant. Appreciate your superiors kids.

Backend internship interview

They: Can you reverse the given string without using pointers? (C++)
Me: Yeah, sure
*Then I start explaining how I am gonna approach the problem and such*
They: Ok, we understand that you can do it, now can you write a front-end that has a couple of routes. Also, these routes should have some sort of list views because we want you to print information **attention** that you are going to parse from Amazon inside those list views.

Me: *dumbfounded and trying to explain that am not a front-end developer*
They: But we still want you to do this.

I hired a new developer after careful screening and interviewing many candidates.

First thing he's asking first day on the job
- I have already booked august month for holiday, is that a problem?
- I need to come 2 hours before anyone else in the morning and leave 2 hours before, everyday because I have things to do at home.
- I've seen that espn.com sport news are blocked by the firewall, why is that?
- I've installed bitTorrent on my PC but it's very slow downloading movies

I hope he's good.

!rant

Just found out that the year 2038 problem fires exactly on my 42nd birthday.

I didn't choose to be developer, it was destiny...

So today I got a call that an end user decided to try to be a developer. He built and ran a bulk edit script on his company's server.....

Without a scaled test....
As root....
From root....
Without backups....

How's this my problem again?

Oh right, it's not (yet)!

I have had this conversation well too often:

- (him/her) Do you mind helping me with this problem I have on my computer ?
- (me) Sure, what is it ?
- (him/her) *proceeds to explaining the problem*
- (me) Ok, I don't know about this particular thing, you should try googling it.
- (the pissed off version of him/her) Never mind, I'll find someone who's willing to help me.

Please stop taking that as me not caring about your problem.
Googling things is basically what I do all day as a developer.
You really should try it. That thing is actually pretty useful.

Client: "the content is pretty confusing and inconsistent. Would you say the frontend is ready?"

Me:"please do not ask that way."

Client: "i just asked a question. What do you mean?"

Me: "well.. you basically say that is bad and then asked me if I thought it was bad."

Client:" i was asking a question. It is your problem if you find that offensive. You were to deliver a finished design until 3pm. "

Me:"you just reviewed it and came up with new input..and apart from that there were just some buttons in the wrong shade."

Client:"yes but I expect that kind of critical input from the developer. "

Me: "I understand, but this was a tiny project for 300 cash. I can't go all out on a budget like this. "

Client:"but all the other jobs I gave you lately were paid much better.."

Me: "yes. Those were other jobs, right? Should I feel obliged to work overtime I eager expectation of more and different work?"

Client: "you used to be more excitable...."

:/

So I'm a entry level female Developer and I started a contract to hire position in July. Its my first job as a developer and I love almost everything about it. Except this..., there is a Senior Female Developer on my team who hates me and isn't shy about it. She goes for the throat man! She magnifies any mistake I make, hell she calls me out on things that people would consider positive. In sprint planning this week she got mad at me for pulling tasks from the backlog after finishing mine early. I've tried to do everything I could to make her like me. I patiently listen when she goes on and on about her damn cats, kids, sports, ah everything, and she is a non stop talker.

Her main problem with me, so she tells the head of engineering, is that I bug her too much. I almost laughed when I heard this was her main issue with me! Sure, I asked her the normal amount of newbie questions but it's not like I don't know how to read code or google! In fact I started avoiding talking to her about a month ago because she was so rude to me. Now getting hired on full time comes down to whether or not she can stand me still if I am working on another team. I'm so frustrated because it's impossible to prove my worth to this company with this crazy lady making me look bad. I have no problems with anyone else at work. In fact a lot of us have become good friends. No one understands why she hates me so much. It feels like middle school all over again.

On top of that there is an even newer hire who she is supposed to help bring on to the team, but because of her horrible management skills, I have become his defecto mentor for learning the project, as well as the technologies we use. The stress of being in an uncertain contract to hire position + tyrant coworker + helping the new guy + still learning and having my own work to do has been overwhelming! I don't know what to do other than hope that she doesn't try to sabotage me moving to a new team.

So yesterday one of the "senior" python developers woke me up at 1 am (we work in different time zones, and he knows how many hours I'm ahead) asking why isn't his code working. The error message was:

[ERROR] Runtime.ImportModuleError: Unable to import module 'app': xxx is not installed, run `pip install xxx` Traceback (most recent call last)

I am at lose of words and patience. Not only idiots who can't google simple stuff are seniors, additionaly we went from "DevOps is a culture" straight to "hey I'm developer in my silo, if it doesn't work on my machine it's DevOps problem, plz fix".

After trying to explain a problem I was facing at work to a Non-Dev friend of mine

Non-Dev Friend: Why did you even choose to become a developer in the first place?

Me: I didn't choose coding, it choose me!

only developer with linux. everyone else are on windows.

constantly finding myself in following conversation

me : "something is not working for me on the web page i am writing"
jim : "let me see just a.... WOW! WHAT IS THIS?"
me:"ubuntu"
jim:"wat?"
me:"linux"
jim:"well... " +sigh + "that's your problem right there! this works to everyone else. and they're on windows. why would you ever not use windows?"
me:"have you ever tried anythig else?"
jim:"never needed to. windows works just fine.."
me:"well... does your computer ever freeze?"
jim:"constantly"
me:"that doesn't happen on ubuntu. at least it is quite rare"
jim:"nah... you're mistaken. windows rocks! anyway, you should probably talk to someone who knows ubuntu cause my chrome works just fine so it must be this ubuntu of yours.."

Had a discussion with a developer about security. His software transfers all user data (password and files) unencrypted, so anyone can grab them with wireshark. I told him that this is a severe issue. He said no its no problem because if you get hacked its your own fault, because you probably used an insecure network. NO ! YOU FUCKING MALADJUSTED SHEEP-MOLESTING OBJECT OF EXECRATION, YOU SHOULD ALWAYS ENCRYPT SENSITIVE USERDATA NO MATTER WHAT NETWORK YOU USE. FUCKING KILL ME ALREADY.
Not implementing encryption is one thing but then acting like its no problem is a fucking nother one. Why do people not understand that security of userdata is important???

Yesterday the web site started logging an exception “A task was canceled” when making a http call using the .Net HTTPClient class (site calling a REST service).

Emails back n’ forth ..blaming the database…blaming the network..then a senior web developer blamed the logging (the system I’m responsible for).

Under the hood, the logger is sending the exception data to another REST service (which sends emails, generates reports etc.) which I had to quickly re-direct the discussion because if we’re seeing the exception email, the logging didn’t cause the exception, it’s just reporting it. Felt a little sad having to explain it to other IT professionals, but everyone seemed to agree and focused on the server resources.

Last night I get a call about the exceptions occurring again in much larger numbers (from 100 to over 5,000 within a few minutes). I log in, add myself to the large skype group chat going on just to catch the same senior web developer say …
“Here is the APM data that shows logging is causing the http tasks to get canceled.”

FRACK!

Me: “No, that data just shows the logging http traffic of the exception. The exception is occurring before any logging is executed. The task is either being canceled due to a network time out or IIS is running out of threads. The web site is failing to execute the http call to the REST service.”

Several other devs, DBAs, and network admins agree.

The errors only lasted a couple of minutes (exactly 2 minutes, which seemed odd), so everyone agrees to dig into the data further in the morning.

This morning I login to my computer to discover the error(s) occurred again at 6:20AM and an email from the senior web developer saying we (my mgr, her mgr, network admins, DBAs, etc) need to discuss changes to the logging system to prevent this problem from negatively affecting the customer experience...blah blah blah.

FRACKing female dog!

Good news is we never had the meeting. When the senior web dev manager came in, he cancelled the meeting.

Turned out to be a hiccup in a domain controller causing the servers to lose their connection to each other for 2 minutes (1-minute timeout, 1 minute to fully re-sync). The exact two-minute burst of errors explained (and proven via wireshark).

People and their petty office politics piss me off.

My favorite part of being a developer is that no matter what craziness is going on in my life I can put on my headphones and lose myself in logical problem solving.

"IT BROKEN!", the QA tester spoke in unintelligible broken English.

The developer asked for more details.

Then the QA person attempted to explain the problem in a surge of verbal diarrhea and horrible English.

Why do we hire people who don't speak the language of the development team as our QA people? I have nothing against devs and qa guys from India...but it makes my job really difficult when I can't even begin to understand what you are telling me, or even worse...you just tell me "IT BROKEN!" and don't give me a single bit of useful information on how to reproduce the error.

There was this wonderful QA person I used to work with. Her name was Ranjana. She was a beautiful Indian girl with two children, and the best QA person I ever worked with. She took screenshots, grabbed logs, and gave steps to reproduce everything she found. And then one day at stand up we were told she had died. And since then...there has been no one who has ever come close to her level of excellence.

Job interview.

Head of development: "I'm looking for the perfect php developer with perfect MySQL knowledge."

Me: "We'll ok. Good look with finding that unicorn. I think we are done here."

The problem with some people is that they are the gatekeepers for other people's careers and that they are begging to be bullshitted: "Yes of course I am the best of all php developers! And I don't only know MySQL but am pretty awesome in YourSQL as well!" As if I want to work in a team posers.

Once upon a time as a developer for Palm handhelds I wrote an application in C which had to print via a Bluetooth printer.
When connected by wire everything was perfect, switching to BT it kept crashing for weeks without me finding the source of the problem.
Then came the day of my companies summer party. I've been the last guy to sit in front of the PC, investigating my problem, when at about 9 PM my boss came and told me, I should grab something to eat. So I went down, drank three beer and got back to work.
At about 9:45 PM the damn wrong * was replaced by the correct & and everything was fine.

PointerIssuesSolvedByBeer++;

On June 2016, I've quite my job. 15 years as developer/system administrator in a middle company in switzerland. 30 people with everyday problem. 30 calls per day.
Now, i work in my own company.
More work, no more time, but u know what? No regrets!! I'm freeeeeeee! :p

!rant

Let's take a moment to appreciate interested and enthousiastic non-developers who really want to learn a programming language.

I am studying Medical IT at my college and most of my classmates aren't coming from an IT background.
We're currently working with Java, PHP, JavaScript and some require Node for their semester projects.

Some of my classmates approach me when they're stuck while coding and I try to teach them as much as possible so they understand what they are doing wrong and how to fix it.
I also show them how they can optimise their code step by step and they love it!

As a classmate told me yesterday:
"It's always so much fun working with you. I come up with a small problem, but I end up learning so much more about programming when solving a problem with you. I appreciate that."

It's a mindset I've learned when I was doing my developer apprenticeship back in the day. One of my colleagues told me: "if they want your help because they need a quick fix, tell them to kiss your ass. If you know they've already tried everything they could and ask you specifically because they want to understand what they are doing wrong, they are future developers with great potential, so go teach them."

May the force be with you, my enthousiastic little non-devs ❤️

Our web department was deploying a fairly large sales campaign (equivalent to a ‘Black Friday’ for us), and the day before, at 4:00PM, one of the devs emails us and asks “Hey, just a heads up, the main sales page takes almost 30 seconds to load. Any chance you could find out why? Thanks!”
We click the URL they sent, and sure enough, 30 seconds on the dot.
Our department manager almost fell out of his chair (a few ‘F’ bombs were thrown).
DBAs sit next door, so he shouts…
Mgr: ”Hey, did you know the new sales page is taking 30 seconds to open!?”
DBA: “Yea, but it’s not the database. Are you just now hearing about this? They have had performance problems for over week now. Our traces show it’s something on their end.”
Mgr: “-bleep- no!”
Mgr tries to get a hold of anyone …no one is answering the phone..so he leaves to find someone…anyone with authority.
4:15 he comes back..
Mgr: “-beep- All the web managers were in a meeting. I had to interrupt and ask if they knew about the performance problem.”
Me: “Oh crap. I assume they didn’t know or they wouldn’t be in a meeting.”
Mgr: “-bleep- no! No one knew. Apparently the only ones who knew were the 3 developers and the DBA!”
Me: “Uh…what exactly do they want us to do?”
Mgr: “The –bleep- if I know!”
Me: “Are there any load tests we could use for the staging servers? Maybe it’s only the developer servers.”
DBA: “No, just those 3 developers testing. They could reproduce the slowness on staging, so no need for the load tests.”
Mgr: “Oh my –bleep-ing God!”
4:30 ..one of the vice presidents comes into our area…
VP: “So, do we know what the problem is? John tells me you guys are fixing the problem.”
Mgr: “No, we just heard about the problem half hour ago. DBAs said the database side is fine and the traces look like the bottleneck is on web side of things.”
VP: “Hmm, no, John said the problem is the caching. Aren’t you responsible for that?”
Mgr: “Uh…um…yea, but I don’t think anyone knows what the problem is yet.”
VP: “Well, get the caching problem fixed as soon as possible. Our sales numbers this year hinge on the deployment tomorrow.”
- VP leaves -
Me: “I looked at the cache, it’s fine. Their traffic is barely a blip. How much do you want to bet they have a bug or a mistyped url in their javascript? A consistent 30 second load time is suspiciously indicative of a timeout somewhere.”
Mgr: “I was thinking the same thing. I’ll have networking run a trace.”

4:45 Networking run their trace, and sure enough, there was some relative path of ‘something’ pointing to a local resource not on development, it was waiting/timing out after 30 seconds. Fixed the path and page loaded instantaneously. Network admin walks over..
NetworkAdmin: “We had no idea they were having problems. If they told us last week, we could have identified the issue. Did anyone else think 30 second load time was a bit suspicious?”
4:50 VP walks in (“John” is the web team manager)..
VP: “John said the caching issue is fixed. Great job everyone.”
Mgr: “It wasn’t the caching, it was a mistyped resource or something in a javascript file.”
VP: “But the caching is fixed? Right? John said it was caching. Anyway, great job everyone. We’re going to have a great day tomorrow!”
VP leaves
NetworkAdmin: “Ouch…you feel that?”
Me: “Feel what?”
NetworkAdmin: “That bus John just threw us under.”
Mgr: “Yea, but I think John just saved 3 jobs. Remember that.”

When I left university I got a Graduate Developer role at a local start-up. For the first year there i did html and css, second year I was in the support team.

Not a problem because sometimes you have to eat some shit to get where you want to be. But third year I got moved into the Dev team properly.

A month in, the Support team, without someone with a devs brain and a "devs" knowledge of the product, started falling really far behind and struggling and the MD told me I'd be going back into Support for another 6-12 months. So I told him to fuck off, and if he did I'd just leave. They never did and I stayed. 👍

I just had a rather stressful morning. I should've known something was up by the sounds of thunder as I walked into the office.

I sat down and checked my emails. There was an email from the boss who was away on a business trip. The subject read, "CRITICAL BUG" and my name was mentioned. "Great...No time for coffee", was my first thought.

I began searching commits to see when and how the bug came to be. "SHIT! It was my fault", I said aloud.

(A bit of backstory, I am Irish, working in Germany with a B2 level of the German language.)

I now had to communicate the problem quickly with a senior developer who is Russian. He can't speak English well and I would not expect him to speak it. We are in Germany after all. I tried my best to communicate the issue, but I found it so difficult to understand his German in a Russian accent. Normally, in the office I speak German except when it is urgent and I must explain a problem in greater detail through English. I got past that obstacle, however, the real challenge of fixing the bug awaited.

After 2 hours of coding, I had a solution and committed it to the master branch. All the while, I had been replying to the bosses emails with updates, probably with many grammer mistakes.

We have no dedicated testers here and the code is written in a way which makes it very difficult to test (i.e. it was written many years ago). When I had initially written the code, I tested rigorously and found no issues.

Just needed to rant. I need a coffee break now...

how about 2 because you can't have everything 🤗

How many devs does it take to fix a light bulb?
None, it's a hardware problem.

Developer came to our area to rant a bit about a problem he was having with Xamarin. A particular android device was receiving a java runtime error trying to de-serialize data from a WCF contract. What he found was not to use WCF and use WebAPI (or a simple REST service that sent back/forth JSON).

When he proposed changing the service (since the data transport didn’t really matter, he could plug the assembly into a WebAPI project in less than an hour), the dev manager shot down the idea pointing him to our service standard that explicitly stated no WebAPI (it’s in bold letters).

I showed him the date on the “standard”, which was 5 years ago. We have versioning on our sharepoint server, so I also him my proposal notes on the change request document (almost two years before that) stating we should stop using WCF in favor of REST based web standards. Dev manager at the time had wrote in his comment “Will never use REST. Enterprise developers prefer RPC.”
He just about fell over laughing when I showed him this gif.

tl;dr read the whole thing you lazy goat-molesting arse.

People. It's unpopular opinion time!
Windows is brilliant.
There. I said it.

Why? Because it has the balance of user-friendliness and customisability that is great for most workloads. Its enormous user- and developer- base allow almost anything you want to be done on it.

For instance, a few years ago I hooked up a MIDI synth pad to my PC and found an obscure program to use MIDI events as macros. I did not have to write any code, compile anything or any crap like that. (If you're a developer then you'll have no problem with that kind of thing, but not everyone's an über-technical nerd like you. Deal with it.)

I don't like Windows. But it's still brilliant for most people. All you Linux fan- boys/girls/helicopters are right to advocate it, but it will never expand its market share to more than the percentage of people who are developers, (unless it turns into a corporate enterprise (which it probably won't)). It has its flaws, but most of them will never affect the average end user. OK? Thanks.

Me (as a Senior developer): How will you solve this problem using regular expression?

Junior developer: *Explains*

Me: Good

Junior developer: I truly feel like a programmer when I code regular expressions

Me: Now, we have two problems.

The developer's date
-----------------------------------
Me working as a developer, after a date with a cute girl
Bestie: Bro, how was the date?
Me: We cant be in a relationship.
Bestie: Why man? She is cute, she likes you and she has got a decent job.
Me: Yeah the third one is the problem. She is a SOFTWARE TESTER!!!😫

How to be a successful developer:
1. Identify a problem that you don't know the answer to.
2. Spend 10 minutes searching Google for a solution, trying various keyword combos.
3. Click the link to the solution in Stackoverflow.
4. Find the solution with the most +1's.
5a. If solution looks good, implement the solution in your code.
5b. If solution is not applicable, return to step 2.
6. Test your implementation.
7a. If the problem is solved, bask in the glory of success and return to step 1.
7b. If the problem is not solved, move your hand vigorously through your hair, pulling out several strands. Exhale loudly. Next return to step 2.

Once went for an interview for a senior web developer role. The first interview was a coding test ( not a problem, been coding for years and know I can do it). The company boasted that it supported pair programming.

I was sat at in an open plan office In front of a machine and given a question sheet of 10 code questions/puzzles and asked to solve them. Then out of nowhere 5 other senior devs appeared and stood behind me and proceeded to comment /question every single line I typed (so no pressure then).

I did questions 1-5 (fairly easy tbh) but all the devs behind me critiquing every single line started to drive me crazy so I asked if it was normal for them to interview this way and was told 'yes' and that after a year of trying to find someone they had been unsuccessful.

I told them that I wanted to leave the interview at that point; I don't mind my code being critiqued just prefer it when I've at least finished the line. Forcing you into a pair programming scenario in the interview really didn't feel right.

To this day (2years later) I still see ads for that very same job

When your boss removed you from the team because he found a better developer that can deliver a task faster than you. Then after a week, he asked you for help and if you want to work for him again because the developer that he replaced to your position can't solve their problem.

I have NEVER had a trust issues with a hard-working developer. It is always good to have someone you know would move heaven and earth to solve a problem, if demanded. It was a privilege to have worked with a handful of them.

PS: If your team doesn't have one such, either be one or change the team/company!

➡️You Are Not A Software Developer⬅️

When I became a developer, I thought that my job is to write software. When my customer had a problem, I was ready to write software that solves that problem. I was taught to write software.

But what customers need is not software. They need a solution to their problem. Your job is to find the most cost-effective solution, what software often is not.

According to the universal law of software development, more code leads to more bugs:

e = mc²

Or

errors = (more code)²

The number of bugs grows with the amount of code. You have to prioritize, reproduce and fix bugs.

The more code you write, the more your team and the team after it has to maintain. Even if you split the system into micro services, the complexity remains.

Writing well-tested, clean code takes a lot of time. When you’re writing code, other important work is idle. The work that prevents your company from becoming rich.

A for-profit company wants to make money and reduce expenses. Then the company hires you to solve problems that prevent it from becoming rich. Confused by your job title, you take their money and turn it into expensive software.

But business has nothing to do about software. Even software business is not about software. Business is about making money.

Your job is to understand how the company is making money, help make more money and reduce expenses. Once you know that, you will become the most valuable asset in the company.

Stop viewing yourself as a software developer. You are a money maker.

Think about how to save and make money for your customers.

Find the most annoying problem and fix it:

▶️Is adding a new feature too costly? Solve the problem manually.
▶️Is testing slow? Become a tester.
▶️Is hiring not going well? Speak at a meetup and advertise your company.
▶️Is your team not productive enough? Bring them coffee.

Your job title doesn’t matter. Ego doesn’t matter either.

Titles and roles are distracting us from what matters to our customers – money.💸

You are a money maker. Thinking as a money maker can help choose the next skill for development. For example:

Serverless: pay only for resources you consume, spend less time on capacity planning = 💰

Machine Learning: get rid of manual decision-making = 💰

TDD: shorter feedback cycle, fewer bugs = 💰

Soft Skills: inspire teammates, so they are more productive and happy = 💰

If you don’t know what to learn next — answer a simple question:

What skills can help my company make more money and reduce expenses?

Very unlikely it’s another web framework written in JavaScript.

Article by Eduards Sizovs
Sizovs.net

People like this guy commentating are the main reason why evolution is still just a theory.

Let's take for example someone having a problem with their car not starting up.

Already seeing this guy's response would be:
"Personally I hate cars. Seems like its always they're broken. Have you just tried using your legs and run 40 kilometers to work every day?"

No I didn't you fucker, and you know why? Because it's not convenient. The same way how it's not convenient for me or any sane developer to drop to a command line and run custom query (which can be automated) every time I want to quickly check some values in development.

And no, the OP didn't ask for setup of this on production, the conversation kept on in comments below and this guy was still defending his productive idea.

Listening to professor tell stories about when he used to develop, is like listening old war stories.

Back when I was in university, this teacher would tell us different stories about his days as a developer. This was one of the last ones, and I think it has not changed much since then.

*Phone rings*
Professor: Hello?

Client: I don't know what the fuck you take me for!

Professor: Oh, hello Client_Name. What seems to be the problem.

Client: This doesn't work! There's nothing here!

Professor: Ok, do you see the program file?

Client: No. I just said that there's nothing here.

They proceed to go over the issue and how to get the program to run. Or at least show up on the PC. This goes on for about 30 minutes.

Suddenly my professor has a thought.

Professor: Have you tried inserting the Floppy disk from the other side? Try flipping it.

Client: ...

Everyone's crying about big bad companies using innocent graduates by offering them a few non-paid internships. But when it comes to mgmt manipulating devs into non-paid overtime by questioning their estimates, noone sees a problem.

For fuck's sake, you are the devs, YOU and ONLY YOU can do tech estimates, not the mgmt. You are nothing close to a developer if you allow them to manipulate you like that. Just a dummy coder at best. A puppet with no backbone. An amoeba. You are DISGUSTING and a disgrace to developers' proffession.

Start acting proffessionally for once!!

One of classmates presented an idea of children tinder as her final project. (To find friends, not...you know..)
So, after a pretty logical question how they're going to prevent it from turning into a platform for kidnappers, they said 'I don't know, not my problem, tinder doesn't do it, Facebook doesn't, it's not my sphere of responsibility. And as a developer I cannot guarantee anything, why are you asking me this you're wrong'
Bravo.

P.s. idk why both of my latest posts are about tinder lol

What are you on about?

I got my first programming job half a year ago, the lead developer there is really fucked up... he is old fashioned and stubborn as hell. He developed a platform that is a mess, his comment: “it works”... but now I have to fix it... I argued with my boss and convinced him to put more time in making it more scalable and feature proof. But the lead developer back then... he didn’t agree it seems like he want to do everything as quickly as possible... now half a year later he stopped working for us and I’m the lead developer now.

And I’m discovering more and more bad decisions... HOWWWW

WHAT DID THIS GUY DO???

At one time I was arguing with him and he backfired a comment: “I’m doing it like this for 10 years”... so I guess that’s the problem... he didn’t put effort in keeping up with the latest developments...

There is literally no structure in his work, every file is different... HOW DO I FIX THIS IN A NICE WAY??? I’m thinking to just start over again...

Sent another developer instructions for generating an SSH key pair and to send me the public key. He did so. There was a problem getting it to work. So, naturally, he emailed me the private key.

Introduced a ‘new’ logging framework for our web site. Web team is testing the integration and I get an email saying the logging wasn’t working. Instead of sending me how she is searching the logs, she sends me a screen shot of the code (which is ass-backwards of how I documented the logging library, but that’s another rant). OK, she wrote 5 lines of code that should be one line, but OK, the error still should have logged fine. I search the logs, and sure enough, there they are. Errors logged just as they should.
So I email back (with screenshot of the search query and results) asking how she searched for the errors.
Hour later she responds ..”I don’t know.”
That’s it.
WTF do you mean “I don’t know”?…WTF…you are a –bleep-ing developer too! This is not the first –bleep-ing splunk query you’ve written!
OK..I’m calm..feeling better. Wouldn’t be so bad if she emailed just me with the question (I’m not a splunk query expert either, we can figure it out together), but she was sure to cc 3 of the PMs involved in the integration, my boss, and other team members to make it sound like the problem was my code.

Yesterday I experienced a developer related situation in a completely different scenario. Let me explain:

A friend asked me if he can borrow my angle-grinder. As I was curious, I asked what he needs it for. As he is not that experienced in woodworking he wanted to cut small piece of wood with it. Of course I told him, that this tool is a complete overkill and recommend him to use a small saw.

Now what makes this programmingrelated:

I believe that often unexperienced programmers tend to use to heavy tools for small tasks. His lack of experience let him choose the most powerful tool, but made him blind for analysis of the actual problem.

GoodGuy BroCow
Senoir problem
2years back

Senoir dev was assigned to make a webapp for billing

Dude uses dreamviewer and writes code like a bitch

Phpmysqljqueryhtml whole thing mixed very badly and undocumented

His function name format fun_1()

a simple update cost him a day,

Told him to use brackets atleast and also a framework ,guy denies

Days go by

He learns a lot of stuffs from me ,like how to use inspect in chrome lol, how to use sqlite for small projects , and orm and frameworks.

He used to pin his mistakes on me, so that boss gets angry on me

Then i quit the job

2 years went by

Now he is unemployed, nobody wants a 24 year old plain php coder and template editing web developer

Anyway I hired him, he was my first senior, whatever he did,it didnt matter to me, bcoz i remember

the days we spent on the same hall right next to each other coding in php,

days we brainstormed to fix a div

Also the days we ate lunch and breakfast together

I hardly even know javascript, but I was able to identify and fix a problem in my Father's corporation website. Should I be worried, that the developer working for him wasn't able to do so?

Got offered a project to develop e-commerce site. Bespoke. E-commerce. Sage pay. CMS. 4 days. When I said it's basically impossible, got told that the company was offered the same solution by an Indian developer but in 2 days, so it shouldn't be a problem to do it in 4.

When I was 17 years old. I had difficulties in understanding math problem “Calculus” (I can’t remember which one was it). This one day when we were in a Computer Lab, our teacher was showing us how really software’s are made. During my time, it was vb6. I paid close attention. When I went home, I started to think things that I can make using that software so one day I went to my teacher and asked if I can have a copy of the vb6. He gave vb6 and told me that inside are few eBooks that will help in learning.

Fuck School, from that day I started to concentrate on programming only. Made a small calculator which will help me to understand a Calculus problem and double check my answer. From that day, I love programming.

I’ m 26 now and a full stack software developer. All I want to do it build cool shit, something that will blow the eyeball of my friends and that eyeball should pop out from their asshole.

Joke: The person who scored highest in the computer class was afraid to switch on the PC.

I spent the last 3 months trying to hire new developers for my team. I found someone experienced who is great and a graduate, who is, well, a graduate.

For some reason he thinks he knows everything about our framework he has never used and seems to think he knows how everything works in our codebase which he has never seen.

That’s fine. I’ve had my share of cocky developers.

But what confuses me is that when I ask him what critical bugs are left, he reels off two significant ones. I ask what it will take to fix it. Of course he says he knows how to fix it. So I say great. Then fix it and let’s move on to a more fun part of our project.

Suddenly he didn’t know where he problem was and so I told him he had to investigate and come back with something concrete.

It’s just frustrating managing this developer who is deceitful.

>be me
>join new firm
>only developer
>Task : Migrate our PHP based website to reactjs
>okay not bad, I can do this
>*Completes in 2 days*
>get inputs from boss and he gives
>go back again to inform we're now SASS integrated
>asks for new wireframes
>wtf lol.exe
>wants new design for the same website like of the parent company which is WordPress template
>*Internally : I'm a developer, I don't do wireframes*
>okay no problem

Seriously, if you wanted a new design in the first place why didn't you said so?

Boss asked hey can you build me out a site?...Me ...sure got the PSD for the site?...Boss...no just build something out...Me...okayyyy....I build out a site...Boss...I don't really like the design...Me... ....*internal eye roll because I'm not a designer*

My job title on paper:
"Application developer"
How I'm introduced to interview candidates:
"Senior software engineer"

Does anyone else see a problem here? 🤔

I am a passionate software engineer.
That means that I strive towards excellence, in all aspects of software engineering. It also means that I cannot abide impediments towards those goals.

In practicality, it means that I will try as hard as I can to make the best possible solution for any specific problem. And that if I can make an improvement to the codebase that will make it easier for the next developer to work with it, I will absolutely make it.

I used to believe that my immediate manager had an understanding of my philosophy and why it was important not just to me personally, but to how the company had to move forwards in general also.

I just had a conversation today that completely flipped my perception of him and his role in the company.

I need a new job. Again. Because business people do not understand software, even if their entire business is based on software.

Dev: *walks into therapy office*
Therapist: what's the problem?
Dev: I'm a developer in a retirement home
Therapist: MARTHA CALL 911!!!

[YYYY]-[MM]-[DD] or [DD]-[MM]-[YYYY]

Across all dashboards and clients we have in current company you'll find one of the above,
Every developer who ever worked on part of the system have chosen either one..

So it's a total mess,
In an attempt to standard all date formats across all our clients I setup a Slack poll,

And guess which one is winning by more than 2x votes!!
[DD]-[MM]-[YYYY] !!!

And here I thought ISO-8601 is enough reason,
But apparently not!

They say our users are more familiar with the other one,,,

It seems main problem is with the education system of this country,
That's how they were thought in schools,

So... FUCK WORLD'S STANDARDS

Man, what a way to start the week. Our mailserver went nuts (something about a Shellbot virus, I don't know) and we were forced to migrate to a new one. Clients calling in panic and threatening to sue us and shit. I was the one tasked to fix the problem (I am a developer mind you, my sysadmin knowledge is limited to google searching and contacting support). At the same time, Turkish hackers attacked our other server and forced me to fetch backups and clear spamming scripts. And to top it all, I was forced to answer the phone calls and respond to the threats. Man, I must have been a complete prick in my previous lifetime to deserve this.

Why is it that an issue is only critical-priority until the person who's raising the biggest fuss has to do something about it?

I was notified that a website hosted in AWS went down overnight and never came back up. I was then bombarded with email after email after email while I logged into our AWS account and poked around. I'm responsible for cloud infrastructure stuff, like VMs or virtual networking or security or whatever, not the actual applications running on said infrastructure. Once I confirmed their EC2 instance was reachable and I could login with SSH, I told them they'd have to fix their application.

They told me that they had no backend developer on their development team. I'm still getting a deluge of emails from multiple people on this team and their managers and managers' managers and so on.

"Perfectly understandable," I told them, though it was anything but. "You should probably look into obtaining one."

The emails stopped immediately. I assumed they were handling it and closed my ticket and moved on. But apparently I was wrong.

Six weeks later, the site is still down, they still have no backend dev, and I'm convinced that they were lying to me when they stressed the importance of this web app because now that it's no longer my problem, not a single person seems to care that it's still broken.

When the department’s large plotter printer broke down, the users demanded they still be able to execute their large reports. The area manager understood reality, if we are waiting on parts, not a lot we can do, but one developer decided to re-write the report/application as a web/.asp application. Mind you, he wasn’t a web developer, mostly VB experience, so the ‘report’ executed the same queries and filled up simple html tables. Did it work? Sort of. The output had none of the specialized formatting like headers, grouping, summary calculations, etc. Since the users could see the data in the web browser and scroll left/right, they were OK with the temporary fix. When I heard this:
Me: “You do know the application could output the report in HTML exactly the way it prints to the printer. All we would have to do enable that feature in the application.”
Dev: “Yea, but I thought it would be cool to do it as a web app.”
Me: “OK, but we should just update the app.”
Dev: “Um...that is going to be difficult, the boss liked my idea so much, he wanted the report replaced with my asp application. I deleted the application from source control and from the network. Sorry.”
Me: “OMFG!…tell me you make a backup!”
Dev: “Ha!...no…boss said you would fight innovation. Web is the future.”
Me: ”What is going to happen when the printer is fixed!? Users are going to flip”
Dev: “Oh, we didn’t think of that. Oh well, that’s your problem now.”
Me: “WTF? My problem?”
Dev: “Yea, you are moving to the team responsible for those legacy applications, since innovation really isn’t your thing. I just got promoted to senior developer.”

So... I've got a confession to make.
I'm no longer a Dev. After the disaster that was my last commercial gig, I went and got a sec Ops role... And I love it. It's just technical problem solving and explaining all the way.
Don't get me wrong, I still love to code. But that's exactly the thing. As a commercial developer employed by corporations, I spent close to 80 % of my time not coding, but in useless meetings, or trying to figure out just what my colleagues thought was "common sense", reverse engineering their work and documenting how to get it running, etc. Basically, fixing shit for braindead academics with next to no real world experience.
Now, when I code, I get to do it on my own terms, with my own stack and as much comments and docs as I want to have. I own my time, and the only ones that are allowed to interrupt me is the local fire department.
I can do what I'm fucking passionate about and leave the rest for the useless people.

I had a project where I completely suprised the client and the company within the beginning. It was silky smooth, working on multiplatform ios android,standalone. I wrote the most complex shader I ever made. Everything was great and I even got a bonus for the project.
Then one day. Videos started to stutter. Not playing, completely black on some cases and some devices.
I started to think about reasons. I tried every solution I come up with. No success.
Updated all the codecs, middleware still nothing. Tried to solve the problem for a week. It was a total diaaster and I even thought I a dont deserve to be a developer.

We encoded the videos a few times. Decided to export the original video again, boom! It worked. Theres no particular reason why it worked. But it worked. I guess I am a good developer. Not the best but, eh.

Story time.....

I only had one mentor. I am a self-learned guy.

He was my mentor in a company where I was interning. He was a Senior Android Developer and I was just a rookie Android Developer working under him.

He never taught me directly but at times he used to send me links of a source for the problem I was having.

At the end of my first working day, I asked him-"Do you think I was useful to you today? "

He bluntly replied-"Nope, none at all"

Those words hit me so hard. My eyes became moist. When I thought about It I did realize that day I was overwhelmed by so many topics I was new to. I was determined to work my ass off from the next day. And I did.

Fast forward to the last day at the company. It was 31'st December, we were having New Years Eve's party. Everyone was a little drunk except for the interns. In front of everyone, my mentor said-"You were the best intern I have ever had such a good intern that I did not have to work last few days", everyone agreed and then he hugged me.

I was on the seventh heaven that day. Throughout my journey back home, I had a broad smile on my face.

"it's the software that's causing the problem not the hardware (that I picked)"

*extensive research is done by technicians and senior developer*

"what's the problem?"

"shit hardware (that you picked)"

There is this minor problem that won't affect any user in thousand years...

But then a developer notices it one day before release

Life of a developer. Wake up in the middle of the night on a weekend and have the solution for the problem at work.

Ask a developer to code entire night

Developer:
😏🤓No Problem. I was born to play with fire 😤😎

Ask a developer to complete the associated documentation in next couple of hours

Developer:
😳🤬🤯 Better call the devil to take me to hell 😱🤒🥵

Past two days one of the senior devs has been complaining to anyone who will listen about a UI assembly containing 'hard-coded' references to a third party component causing several builds to break. The developer who added the telerik component probably had no idea the reference is pointing to his personal directory instead of a relative path. Easy fix? Uh...yea...but he just ranted to our boss for about 10 minutes about he has no idea how to fix the problem and the TFS build failure holding up his other projects.
WTF!? You fracking know what the relative path is!...just fracking change it and move the frack on.

The drama this drama-queen keeps spewing out is driving me out of my mind.

PM : "I will not tolerate this."

Me : "I don't like it either inside callbacks."

Fellow dev sitting next to me : *facepalm*

I love my job as a developer, I think it's the one of the world's most most fulfilling occupations but I procrastinate with personal projects (even paid ones). Is this a problem for anyone else, and how do you beat this?

I can only imagine what goes through clients’ tiny brains. Do they really think: “oh I know what will get shit done, insult the developer, his work, and demand things be fixed while saying the whole system is broken even though they have multiple times in the past demonstrated that it was either me using it wrong or an extremely quick and simple fix. I also have a problem with a few listed items in particular not the whole system, but I’m gonna insult everything.”

Fucking rude fucks!

I am working on a project that integrated with Microsoft Dynamics. The D365 team changes the data and API too often. I keep munging the data over and over so that it fits view models.

Yesterday I had a technical discussion with someone that the company installed to coordinate building technical solutions that get shared between projects. This is a problem across all of our Dynamics projects and is a technical one than needs coordinated approach.

The management heard that I am “doing repeated work because the data isn’t stable.” So they decided that it must be a problem with the project manager. The executive decides to use it as a reason to fire him. Which shows me that I can’t talk to even a technical person without risk of project chaos.

After the conversation but before the firing I get an offer letter from another company. I plan on taking it to get away from this crazy company. The project is going to lose their key web developer and also the project manager.

This executive seems to love firing project managers. My other project is on its third PM. My trust for the upper management is basically gone. I can’t even discuss the technical hurdles with a technical person without someone getting fired. I’m so ready to be out of this zoo.

The only downside of leaving is that I won’t have as many stories to tell on devRant.

why people around me act like dump. i have recently worked with this site, which is written in php.

customer: (yelling) my website is hacked, fix it immediately
me : ok sir, we will restore your site immediately

after finishing talk with customer. i have checked website, there is no sign of website being hacked. i have checked server logs and website for security breach, there is no sign.

me: your website is not hacked, sir. can you please tell me where you have seen hacked page.
customer: look at those pages

after seen that page i facepalmed myself. it's a bug, person who created that page just splitted string without using any multibyte function, so page is showing with corrupted characters. i fixed it and problem solved. i have told about that bug, to the person who created that page.

me: hey you have used this function which is not able to handle multibyte characters, you should use multibyte character functions for that one.
person: every characters are the same. we shouldn't need to handle that way.

he is actually a senior developer. who don't even know the difference between unicode and ascii characters.

There is a fuck-nut moron developer in my team who's been driving me crazy. I end up having multiple conversation with him on the same problem; I give him the solution; he nods his head and then makes the same mistake he made earlier.

I really want to help him learn and grow, but one can only tolerate so much stupidity before giving up.

When u spend too much time writing Java and suddenly go back to C# yet continue to write Java code 😪

I think nobody as a developer or as a sysadmin wants to deal with a grouchy sysdba. As a full stack developer who sometimes does the work of a sysadmin or sysdba I prefer to do things myself when I can.
But last week I was notified that my app was failing in prod. After some debugging the problem seemed to be related to some queries.
Upon further inspection I realized that the cunt revoked the select grant for the user my app was using.
I will let that sink in. He revoked the fucking select grant. Wtf😶

Where there's a problem, there's a hack

It's rant time!

So, as a broke electrical engineering student, I got this job in a local company. They used JSF and my skills in java were, at the very least, small (former PHP developer). But as a self taught developer this didn't stopped me and I went full on java learning (very bad year for my EE studies).

I became the 'guy in charge' for several of their projects (yeah, they did exploited broke students, I realized this far too late). I was very proud of myself, I worked hard, showed my true value, and they became impressed.

One nice thursday night, my "handler" emailed me with a urgent request. They needed an entire jsf application done by monday and the requirements were fairly complex.

Oh boy, I had a total of 10h of sleep from thursday to monday. I didn't even slept before going to my monday class, but I delivered the system. Got an pat in the back... "you're awesome"... I was happy.

6 months later: I received an email asking to fix a bug in the system. No problem with that. Oddly, this bug was a MAJOR bug. There's no way the system worked properly for six months with it. I fixed it in no time and commited the changes.

Turns out that this was the first time the system was going to be deployed. They made me go in an insane weekend dev project, and didn't even used the system for SIX MONTHS!!! I started to work my way out the company after this, aiming to open my own software company.

I still remember some other rants from the time I worked there. But these are for later.

Nice week for you all, may the sprint go gently and the clients be kind.

Teacher asks the class:
"How do you become a good developer?"

All the students starts talking about algorithms, problem solving or working in a team.

He nods and starts writing on the board. w w w. g o o g l e . c o m
He then leaves the classroom.

So here I am years later, a master googler and a expert stack overflower.

So apparently I can't test my apps on my own device without paying my Apple Developer Certificate.

I knew it is needed to pay for it if you want to publish/distribute your app but c'mon... This is ridiculous.

My app was literally a fresh app creation, a fucking white screen one page fucking app and when I tried to run in on my iPhone, then I ended up having this problem:

dyld: Library not loaded: @rpath/libswiftCore.dylib
Referenced from: /var/containers/Bundle/Application/BCD48EAA-82C2-46F6-ADEE-45C740C3B66D/HWorld.app/HWorld
Reason: no suitable image found. Did find:
/private/var/containers/Bundle/Application/BCD48EAA-82C2-46F6-ADEE-45C740C3B66D/HWorld.app/Frameworks/libswiftCore.dylib: code signing blocked mmap() of '/private/var/containers/Bundle/Application/BCD48EAA-82C2-46F6-ADEE-45C740C3B66D/HWorld.app/Frameworks/libswiftCore.dylib'
(lldb)

If any of you guys know how to solve it without paying (even more) PLEASE let me know

THANKS

Working with a developer from another company, nominally called Jo. I had a programming session with Jo today.

Sometimes it's hard to succinctly describe an individual developers level of aptitude in highly technical fields to outsiders because it often requires a lot of context relating to the problem being solved and their attempts to solve it.

In this case I think it could be pretty accurately summarised in this little anecdote: there was a 10 second pause in our work today while Jo was trying to figure out how to type '<'

So I help out in a development forum for a framework I use at work. I learned a crap ton by seeing questions people ask, then learning to solve them myself. I have really enjoyed being in that forum that past 4 years.

Yet, I see people who cannot seem to reason themselves out of a paper bag at times. I see questions of I cannot run this linux executable because there are parenthesis in the filename. I mean most console interfaces are just tab complete even with special characters. This is for a developer in their 50s that has been coding 30 years. Or I see other programmers asking basic questions that 5 minutes with the docs would solve. Most of the ones that I have issue with seem to have been a part of that community a lot longer than myself.

How do developers survive without problem solving skills to understand the frameworks or tools they use?

I had another conversation with a dev in another forum about using "man" in Linux to figure out how to use something. They said something to the effect: "try learning awk from a manpage". I explained about how "back in the day" we learned EVERYTHING from man pages. That is why they are called "man" pages.

Is the industry flooded with idiots now?

I find many of the peculiarities about our kind (developer) to be amusing.

Here is one I have seen too many times to count...

You ask a group of developer something like...

“We have a project built using X, Y and Z. We are looking at integrating the “example framework” to solve a specific problem. Do you have any experience with “example framework” or would you suggest another framework?”

Inevitably you get the same useless response of “Why are you using X, Y, and Z. It’s so <insert generic complaint here>!” Followed with no actual attempt to answer the question asked...

Listen, I know some of us a socially awkward (I can be) and I know we like to debate and argue.

But, if someone asks you a specific technical question about an existing product, either...

1. Answer the question with your experience
2. Declare that you do not have experience with it
3. Shut your fucking childish mouth

No one cares about how you feel about the size of the underlying technology in existing products! What do you expect?

“OMG, we didn’t realize X technology as 100mb large! Hold on while we go and reengineer our entire product base because of this fucking revelation you just told us!”

You may want to hear your own voice but the rest of us would prefer it if you would shut your mouth if you have nothing useful to add.

(Reads as: we would prefer is you fucked right off!)

I think the worst problem every developer has is that world has never answered back.

After 2 years in a small company as an all around software developer (started with xamarin for Android/iOS, then Unity, then OpenXML, augmented reality, virtual reality and .Net MVC...yeah all that and lots more) I changed to another company and I'm here 1 month and some days. I am super enthusiastic and I like it here!! They're more specific and professional, exactly what I need at the moment.

What is the problem, you might ask?

I was given some projects, I have done most of the work but now an issue arrived. I did almost everything and now we're waiting for some answers needed before closing the projects. And I get bored. I want to work!! I need to continue the streak! Just give me something and I'll make it happen!! I am boreeed!!

What is wrong with me? Am I buggy or something?

I work in a bitcoin startup , my fucking boss really wants everyone to use ubuntu because of security and all , the bad thing is i am the only guy who knows how to install and deal with it , so when any one joins or has some problem he always bugs me and the thing is i am an android developer not a sys admin and now he fucking want to get 2 factor in ubuntu desktops when they log in

This is something I'm proud of about myself as a developer, which is rare.

My setup with the Alt key.

All the keys in my left hand (as in, for all the keys in my left hand region, qwerasdfzxcv)
have their Alt and AltShift combinations mapped to (almost) all the special chars related to programming.
For example:
Alt + z -> /
AltShift + z -> \

Here's me typing them in 2 seconds.
{}()_-'"/:+=<>[]|#~`\;*!

And, on my right hand, I emulate the arrow keys movement:
Alt + hjkl moves chars
AltShift + hjkl moves and selects chars
AltCtrl + hjkl moves words
AltCtrlShift + hjkl moves and selects words
Alt + n. backspaces/deletes chars
AltCtrl + n. backspaces/deletes words

And the best of them all:
Alt + space -> <return>
AltShift + space -> Shift+<return> (which does a newline in chat editors like fb messenger)
AltCtrl + Space -> Ctrl+<return> (which can do the submit in some forms, like send email in gmail)

Now, my hand sits for real on the home row and rarely moves because it's not there just for vim, but for the entire system as well.
This setup is very compliant with my little mouse use, since I use vim, and the vim extension for chrome.
I still use and need the mouse for some tasks.

Another one huge benefit is that I don't have a problem remembering where the keys are. This is a problem I can have because I go between different keyboards because of having used different keyboards: argentinian, american, japanese and now brazilian (I'm not trying to be cool, it's just a series of circumstances that led me to using different keyboards).

At the same time, this thing might have become a hinderance because it's not as easy for me going to a different keyboard.

Regarding implementations, when I used MacOS I used Karabiner, insanely clean interface.
On linux, I have to create my own mapping in X.

What was your most disappointing moment as a software developer?

Mine was the realization that when you're working for someone, all they want to see is the final product. The people paying you don't give a shit whether you put your braces on a new line, your domain model doesn't call a database directly or if you're applying the best practices. Your teammates do, but the people paying you don't.

People hire you to get the job done, and that job is to solve a problem for someone. Not in the way that's best for you, but in the most effective way for them. Since I realized this, I lost some pride in my work.

Hello everyone, first time ranter here! I have been studying Computer Science for 2 years starting September. The program introduced me to Java,HTML,CSS, JS and php. I feel like even though I am currently studying this I still do not "know" how to code. For example when I look at my classmates when they code it all seems so effortless and smooth, if they run into an issue they will usually solve it within the hour where as when I run into an issue I struggle to even see what the problem is. So the real point of this rant is, how do I improve? I am currently doing the #100daysofcode to get better but sometimes I feel so far away from calling myself a "developer" what is your road to the "developer" title? did you struggle as much as I am at the moment? or did you just sail into it like my classmates?

A server application pulled off some sort of listings as table. Problem was, it crashed with some thousand data files after one and a half hours. I looked into that, and couldn't stop WTFing.

A stupid server side script fetched the data in XML (WTF!) and then inserted shit node-wise (WTF!!), which was O(n^2) - in PHP and on XML! Then it converted the whole shebang into HTML for browser display although users would finally copy/paste the result into Excel anyway.

The original developer even had written a note on the application page that pulling the data "could take long". Yeah because it's so fucking STUPID that Clippy is an Einstein in comparison, that's why!

So I pulled the raw data via batch file without XML wrapping and wrote a little C program for merging the dumped stuff client-side in O(n), spitting out a final CSV for Excel import.

Instead of fucking the server for 1.5 hours and then crashing, shit is done after 7 seconds, out of which the actual data processing takes 40 bloody milliseconds!

This is meant as a follow-up on my story about how I'm no longer and Ada developer and everything leading up to that. The tldr is that despite over a decade of FOSS work, code that could regularly outperform a leading Ada vendor, and much needed educational media, I was rejected from a job at that vendor, as well as a testing company centered around Ada, as well as regularly met with hostility from the community.

The past few months I have been working on a "pattern combinator" engine for text parsing, that works in C#, VB, and F#. I won't explain it here, but the performance is wonderful and there's substantial advantages.

From there, I've started a small project to write a domain specific language for easily defining grammars and parsing it using this engine.

Microsoft's VisualStudio team has reached out and offered help and advice for implementing the extensions and other integrations I want.

That Ada vendor regularly copied things I had worked on, "introducing" seven things after I had originally been working on them.

In the almost as long experience with .NET I've rarely encountered hostility, and the closest thing to a problem I've had has been a few, resolved, misunderstandings.

Microsoft is a pretty damn good company. And it's great to actually be welcomed/included.

Why I don't use Stack Overflow 99% of the time:

Me: I'm not a ruby developer, but I have to write a small script in ruby. I ran into a problem where i'm getting behavior I don't expect. I have a method which expects an array, and when multiple items are passed into it from the command line parser, behaves appropriately, but when only one command line argument is passed, the method breaks because it was passed a single element, not an array of one element. Here's my code, how do I get my desired behavior?

Most highly voted answer: your problem is your passing it a single element and not an array

Question downvoted into oblivion. As if i'm a pleb for not immediately having a perfect grasp of dynamic typing because when I have the choice I stick with strong nominative typing.

Regardless of all my complaining, and the current drunk urge to cyber bully right now, I am thankful for my job and for all the support and knowledge from the developer community that has made me a better human - that includes devrant. I am thankful that I have found something I’m sorta good at and I am able to support a very good lifestyle because of it. I am thankful for the good times I have because of programming, and I am thankful for the struggle that has helped develop me as a problem solver and professional. I am thankful for all my friends I have met in this field. I am thankful to God for this place I am in.

I found weird that some developer never ask why when facing a problem. "What do you mean never ask why?" here some story.

Let's say a developer work with simple app. Laravel as Backend and Postgresql as Database. He face a problem that the app very slow when searching data.

In order to solve that problem he implement cache using redis but he found problem that it fast occasionally. In order to solve that problem he implement elasticsearch because he think elasticsearch very good for search but he found another problem that sometimes data on postgresql out of sync with data on elasticsearch. In order to solve that problem he implement cronjobs to fix out of sync data but he found another problem that cronjobs cannot fix out of sync data in real time. and so on...

Do you see the problem? He never ask why the app slow. Which part search the data? Backend or Database (Search in the Backend mostly slower than Database because Backend have to get all data on database first). Has the query been optimized? (limit offset, indexing). How about the internet connection? etc.

For me it's important to ask why when facing a problem and try to solve the problem as simple as possible.

So I work for a company that does outsource, this company is pretty nice, but I don't get to see it too often. The one where I'm outsourcing though is the one where I spend all of my time.

Now, this company is a kind of a startup working with AI and Deep Learning (but not if statements :o ), but I came here as a full stack python developer that should implement their AI modules into real apps (mainly web apps).

Everything sounds good untill now, I learn lots and I'm doing what I wanted: python development. The problem is: management + one kiss ass guy.

The amount of work that should be done and the deadlines that should be kept are so messed up that I end up working extra hours, sometimes even in weekend, just to get it done. I'm the only apps developer there, so passing my tasks is not an option. I tried to talk about this, but I was met with a "loser can't keep up even with these few tasks..." kind of attitude.

Moreover, there is a guy that would do anything for the boss's attention, so he speaks everyone there behind their backs (and we all know it, but he's the favorite and he actually knows his stuff so we can't do much about him).

Now the question: what should I do? I only have 5 months here (so leaving would put a hole in my CV, I don't even know what to answer at this interview question "why are you leaving"), plus that the managers from these two companies are highschool friends which means that if I go and ask for a different project, the atmosphere at work will change (maybe this is overthinking already, but I can't help it). Also, last week I could barely get through the days without crying from stress.

TL;DR: I learn a lot from this company, but the deadlines are killing me and my stress level is at an all time high. I want to leave, but I kind of can't because I want my CV to look good.

So yeah, this is my first real rant, feels good to put it out there

So not too long ago I made a rant about this time I told my superiors of a problem and it got shot down because "We don't want to save developer time".

I warned them that the CPU was going to reach it's limit because the issue involves exponential growth on CPU usage the more we develop.

As it turned out, despite my thoughts that we wouldn't reach that limit for over a year, a new development led to it blowing up in their face today.

I am now treated as the expert on the topic and they're rushing to plan my suggested implementation in the next release.

I'm mildly amused.

Yesterday I had to merge new features. As these have been developed by one developer, I thought "hey, that'll be no problem". Little did I know that every one of the 6 branches had merge conflicts *sigh*. These merge conflicts were so severe, that there where sometimes two methods in the same class with the same name doing different stuff in each branch... Normally I would tell her to fix her stuff but as she is on vacation right now, I had all the fun resolving the conflicts of code I hadn't written and repairing the failing unit tests she wrote.

The best thing is that our software will be featured in one of the most renowned business magazines at the end of the week while simultaneously being presented at a congress in Berlin in front of over thousand of potential new customers. So these knew features have to be running stable in production by then... Needless to say I had a great day yesterday and will have an amazing upcoming week 🎉

Today at 7am i got s phone call please go to this client

I responded sure no problem what am i going to do at this client.....

Don't worry they said you will find out when you get there...

So i go to the client and as I expected its not dev related at all

It was for installation of point of sale tills and printers 😱😱

That are 7 years old with no cables
(2 hour drive to get here)

Anyway I ended up selling hardware to them....this developer is going places 😂🙈

!rant

OK, I have a dilemma and I need some developers helps. I'm going to tell you about myself. I am 19 and have been programming since I was 11. I consider myself a full stack web developer and that is where my passion lies... I love web development. The problem is that I am currently studying comp sci at a top 10 uni and I don't really like it. I kind of enjoy it, however, I am mostly doing it for the degree because my goal is to move to the valley (currently in the UK). I'm not sure whether I should pursue this degree because it's interesting and tbh I might just need time to get used to uni life or should I just go for it in the industry?

Just go to GPT and get me the code today!!!

Like wtf why does every non-tech guy thinks GPT is the solution for each problem.
So, a workmate wanted a fullstack system ready in 2 days and argues that its too easy with GPT. I mean yeah GPT helps, sometimes, on frequent rare occasions. But, that can't be the solution to everything, like ask it to setup the whole backend frontend integration, will it? ask it to manage assets will it? ask it to write complex code, it fails, miserably, okay like me but that's the point. Just because random transformers pop up each week containing some random shitty weights (not always agreed) that can't replace a full stack developer. These 'attention' seeking models are as good as another tool, a bit efficient, but at the end of the day its just a tool, all it does is lessen the typing time but gives more errors too. The average time remains the same. And my non-tech manager can't understand he can't do it himself earlier using GPT. Succkkkkkkssss!

What really gets on my nerves?
People that think I can fix every computer problem there is, just because I'm a developer and therefore must know everything about PCs.

What do I look like, a Tech Wizard?

developer makes a "missed-a-semicolon"-kind of mistake that brings your non-production infrastructure down.

manager goes crazy. rallies the whole team into a meeting to find "whom to hold accountable for this stupid mistake" ( read : whom should I blame? ).

spend 1-hour to investigate the problem. send out another developer to fix the problem.

... continue digging ...
( with every step in the software development lifecycle handbook; the only step missing was to pull the handbook itself out )

finds that the developer followed the development process well ( no hoops jumped ).
the error was missed during the code review because the reviewer didn't actually "review" the code, but reported that they had "reviewed and merged" the code

get asked why we're all spending time trying to fix a problem that occurred in a non-production environment. apparently, now it is about figuring out the root cause so that it doesn't happen in production.

we're ALL now staring at the SAME pull request. now the manager is suddenly more mad because the developer used brackets to indicate the pseudo-path where the change occurred.
"WHY WOULD YOU WASTE 30-SECONDS PUTTING ALL THOSE BRACES? YOU'RE ALREADY ON A BRANCH!"

PS : the reason I didn't quote any of the manager's words until the end was because they were screaming all along, so, I'd have to type in ALL CAPS-case. I'm a CAPS-case-hater by-default ( except for the singular use of "I" ( eye; indicating myself ) )

WTF? I mean, walk your temper off first ( I don't mean literally, right now; for now, consider it a figure of speech. I wish I could ask you to do it literally; but no, I'm not that much of a sadist just yet ). Then come back and decide what you actually want to be pissed about. Then think more; about whether you want to kill everyone else's productivity by rallying the entire team ( OK, I'm exaggerating, it's a small team of 4 people; excluding the manager ) to look at an issue that happened in a non-production environment.
At the end of the week, you're still going to come back and say we're behind schedule because we didn't get any work done.
Well, here's 4 hours of our time consumed away by you.

This manager also has a habit of saying, "getting on X's case". Even if it is a discussion ( and not a debate ). What is that supposed to mean? Did X commit such a grave crime that they need to be condemned to hell?

I miss my old organization where there was a strict no-blame policy. Their strategy was, "OK, we have an issue, let's fix it and move on."
I've gotten involved ( not caused it ) in even bigger issues ( like an almost-data-breach ) and nobody ever pointed a finger at another person.
Even though we all knew who caused the issue. Some even went beyond and defended the person. Like, "Them. No, that's not possible. They won't do such dumb mistakes. They're very thorough with their work."
No one even talked about the person behind their back either ( at least I wasn't involved in any such conversation ). Even later, after the whole issue had settled down. I don't think people brought it up later either ( though it was kind of a hush-hush need-to-know event )

Now I realize the other unsaid-advantage of the no-blame policy. You don't lose 4 hours of your so-called "quarantine productivity". We're already short on productivity. Please don't add anymore. 🙏

So today my pr needed approval. One of the lines of code created a unique ID using the uuid4 functionality.
I got a reject saying I didn't handle a case where I would get the same uuid twice.
Well, I guess it would be the problem of the developer working on my code in a couple thousands of years 🤷‍♂️

My newly joined developer colleague had some problem starting the web app we are working on locally. After changing some configuration files,

Me: Restart the app

My Dev Colleague: Do I have to close it?

Me: Yeah, there will be a red cross on the right top corner, just click on that😑😒

I have just started working in this industry, and so annoyed by the fact that managers are insensitive to the efforts put in by the developers.
1. They ask for estimates, and sometimes consider it to be the hard line for everything and then they make you feel guilty if you are not able to live up to them.

-- I am not asking to be always lenient but they need to understand that this is problem solving and one might not be able to gage the problem at first sight. A problem might have several sub problems or a solution to one issue might raise compatibility issues with other which were tough to foresee .

2. Why do they always want an instant response to their email or query, a developer being online isn't just there to answer your damn obvious and sometimes stupid questions which can be understood just be glancing at the logs once.

-- How annoying would it be if the manager himself is being poked every other minute for trivial things. Does he have the same patience with his/her developers?

3. In tough times the manager easily delegates the responsibility to the developer and instead of standing by his/her side, interrogates them as if we have done some crime.

-- Wasn't this approved by you. Weren't you the one who had these stupid demands before and didn't let me do things the correct or optimized way. I am not saying I am always right, but you can be atleast open for feedback or discussion.

Why are you the first to take credit for the success and yet hold us responsible for any mishaps.

It's sad to see that some of these people have been tech developers.
I can go on ranting for many more things.
I am not saying all those people out there are like this. But trust me many are.

Note: I am not seasoned as you guys out there. I may even be biased by my own experiences. But this is in complete contrast to what I was expecting when I graduated from college and was excited to finally learn by working.

I think God is a developer. I have to say a most impressive feat, even for God, is the idiot algorithm. It has persisted through millennia of attempts to remove it, but it just keeps refining itself. While it's incredibly brief, its functions are yet to find an environment in which they cannot operate. It's full adaptable to any task, impressively modular, and self replicating.

No matter how what problem you present it with the idiot algorithm can always find a solution. It never leaves well enough alone. It can even give you an answer before everything is fully processed!

Developer: we have a problem

Manager: remember, there are no such things as problems, only opportunities.

Developer: Well then, we have opportunity to recreate the entire project we're working on 2 years

This is definitely a total first world problem but I am so frustrated.

I am stuck in a team that embodies the Japanese proverb "The nail that sticks out gets hammered down".

The management are there because it is convenient and flexible and have no interest in managing or keeping up with tech.
The lead developers are extremely anti-social and are not approachable and the this stems down to the devs (not all but really most) - all there just to do the bare minimum and spend most of their energies in trying to avoid work or having learn something.

Unfortunately I am passionate about what I do and want to build high-quality products and this has put me at odds with the way things work.

I could fill up alot of time talking about how I was ordered to "cut" images/icons out of PDFs rather just getting them from the branding team, or how I was scolded for having set up logging, detected a problem caused by another developer and fixed it before it cost a big client a massive amount of money... But really the point is that I have never worked somewhere with such an awful attitude to enthusiasm and quite frankly it boggles my mind trying to understand how they rationalise these things but the answer is always laziness.

Obviously there are worse problems in the world than working in a job where you are encouraged to do nothing... But it actually really depresses me and causes anxiety that I am working with people who don't care about testing or monitoring or learning new things or even collaboration.

...sigh...

Hopefully the job market will start opening again soon

!rant && advice
I am an Android Developer, but about to start my final year. I got a mail from a company telling me saying...
"... and we are looking for problem solvers like you.

We Invite your CV and look forward to hearing back from you."

Stupid it may sound, but how do I reply to them? Do I also send a cover letter? If yes, what do I write? What do I mention in the email?

Thanks.

!myrant

I'm a junior developer in a small company alongside with a fellow programmer. Since I have an interest in Security and our Sys Admin left, my boss offered me to do some sys admin stuff.

I feel bad for my fellow programmer just because there is an old man in the company that doesn't come to me with his tech problems and goes to him.

Something like this goes down today:
OM: Hey, I can't watch my Fox Live News. Can you help me?
FP: The problem isn't on our side

*OM keeps pestering him*

FP: Let me check it out

*Goes and fix the issue and comes back laughing *

My coworker is to kind 😬😂😅

Ah, the little subtle things we have to iron out as we progress from Junior Developer to Medior Developer.. things like:

- knowing the difference between a carriage return and a line feed (although having worked with analog typewriters helps) and later knowing that Unix-based systems and Windows NT-based systems implement it differently..

- knowing that serialization is important because not all computers interpret data the same way and some computers allocate 4 Bytes for a construct, others 16 Bytes.. and then we get the funkiness of transferring character sets between machines..

- knowing that a whitespace character is not only an actual space (as is known in ASCII as code 32). This one can cause even medior developers a headache, as in: why the fuck does this string function say that "hello I am a duck" and "hello I am a duck" are not the same?! Turns out then in the debugger that when you expand every character in the string you see that string1 contains 32 32 32 32 as usual.. but then string2 contains -96 -96 -96 -96 and you're like.. what the fuck..? Then you know you have to throw \\h regex at it. Haha.

- finalizing our objects and streams (although modern languages do that for us).. otherwise we have to do funky shit like trying to find what's locking a file, which is not so easy to figure out.

- figuring out why something won't work often requires you to not only break down the problem in smaller steps, to use a debugger, but sometimes it's even better to just create a proof of concept, slap some minimal code in there and debug that.. much easier.

- etc.

:)

*Nervous student comes in for the first interview I am conducting as a developer*

Me (as an interviewer): What is best approach to search data?

Student: It will take linear time but if data is sorted, we can do it in logarithmic time.

Me: [Smiles] Take a hint Hash Map?

Student: Yes, with it, we can do it in constant time.

Me: Okay, Bloom Filter anytime?

Student: *sweating* noooo...

Me: Okay. I am a developer so I know this.

Student: *about to cry*

Me: No problem but why will you search data when there is no problem? Don't you have better work.

Student: *confused* yup

Me: *laughs but immediately controls* Take it lightly. You know what you need to do this job. You are HIRED. :)

WHY DO PEOPLE ALWAYS LEAVE CLOSE TO DEADLINES???

My team exists of three developers and a product owner. By the end of the month we have to deliver two new applications. It has not been going as smoothly as we'd hoped so far. However, one of the developers has cut his time for this project from fulltime to 1-2 days a week starting this week. The other developer is also needed on another project and has to run to the rescue whenever there is a problem with the servers, so he doesn't really solve any bugs either. Also he'll be leaving straight after deadline so he has to document everything only he knows and he'll be on holiday next week. Also, the product owner leaves tomorrow and will be back after deadline.

So.. Here I am, junior developer, have been here for about three months and I have to fix everything and do the communication to our testers as well. I'm feeling too overwhelmed right now...

Trying to switch my job. Applied for a well known company. Gave an interview today. I don't fucking get the obsession of these developer recruiters so fixated on data structures and algorithms. I know it's a massive part of computer science but guess there is no fucking room left to innovate in there. There are legitimate researcher teams working for implementation of these barebones inside system foundations. No general software developer gives a fuck about this piece of shit discipline of study. You wanna know why they propagate this as the panacea to test people because it's fucking easy. Give a project to somebody as interview procedure, it'll take time to bring out an interesting problem and an interesting solution to that. Sorry to say but all these data structure enthusiasts are nothing better than board game enthusiasts.

Also why can't you refer existing solutions to create your solution. I've seen some good problems which actually require you to think. But again those are heavy and can't be tested so you're left with reversing a fucking linked list with O(1) auxillary space. Fuck me ig.

Moreover, what the fuck is wrong with the moral policing internet crowd. Its so sad. I've hardly seen anybody rant about this piece of shit system put in place to push the absolute dead-end nutcases up the ladder. Every other search for it returns a Quora link with some Indian guy complaining about his interviews and in the comments you have the same scholars sitting in their data structure throne imparting knowledge about how data structure holds the fabric of reality together.

I don't hate data structures and algorithms as a subject. It is cool and quite extensive but once you try to make that as a metric of all the knowledge in the world, you've lost my drift. Maybe I'm just angry with the state of things. Maybe I'm just angry with token Quora crowd.

LoL.. I knew this one successful independent developer who told me:

"Why do all these companies use inefficient technologies - seriously? What I usually do is: I present myself to a company, I ask them what they would like to happen, what their problem domain is and then I present a solution. A lot of companies I've consulted for were jaw-dropped that an entire efficient and complex system was only a size of 52 KiloBytes because I just used simple languages to accomplish the task".

He has a point.. look at all these companies nowadays forcing you to Java, GlassFish, NodeJS and what not. Just the frameworks and libraries alone hog down 10 minutes of build time (sometimes 30!!), the worst companies using frameworks that require you to rebuild an entire project just to see a change in the UI.. they don't even add a watcher, and even then.. omg, not to mention averaging project file sizes of 100+ MB.

Sigh.. where is the development world going?

What do you tell interviewers as a "Senior developer" when they ask you what you do at your current job.

I've been with my current for almost 8 years, since graduating... Few different time but not very well managed (semi/barely agile). Hasn't really provided any skill growth opportunities. Mostly fixing production issues, chasing other teams.

The projects I've worked on are in many different languages either enhancements or some standalone stuff. But nothing that's huge and I don't think I've learned anything from them. I usually apply what I learn and practice outside of work to work.

So to me I can probably list a whole lot of projects but to me their not that amazing, I didn't learn anything from them.

Also about those algorithm questions. I've never used any of this stuff actually at work. Concepts yes but not how do you implement ... And honestly I've never once had a situation that required algorithmic thinking other than maybe writing recursive functions in rare occasions...

But to me I've never once done anything harder or new which I haven't already done on my own....

Sorry for the disorderly rambling this turned into... which is sorta a problem too.

Everytime I think about interviews, I want to give rants about we technical questions are BS, how I probably have enough real experience to tackle any problem and come up with a good plan/solution (in a realistic timeframe, not 20 minutes from design to implementation)

As a developer I have a problem I have to get over and it's called: negative spiral thinking. It's the biggest impediment to progress (that and bureaucracy).

You sit there facing a problem, you keep focusing on the problem, but the problem spouts other problems and then you care too much about those other problems and you start fussing around, negative thoughts start to spout everywhere and you end up continuously losing your focus.

Blah.

Yes I'm a developer, no I can't solve your generic IT problem :(

Proudest bug squash experience?

Fixed a N+1 pattern bug on our web site. Wasn't a deeply technical problem, but I was proud to shove the fix up the arse of the developer who blamed me (and even got a VP involved) for the web site crashes (the N+1 involved his code calling a service I wrote) and none of the half-dozen other devs found it.
I really wanted to make a t-shirt with his initial 'blame' email outlining all the 'technical problems' with my service, and the fix was literally moving the service call outside 5 (yes 5) level deep for..each loops.

does anyone else feel that "developers are on high demand" and "if you're a good developer you should have no problem getting a job" is kind of a lie that the industry sells to you?. I mean I didn't expect to polish my linkedin profile and get 20 offers but damn. Yeah I see a lot of job offers on multiple platforms. Yeah I apply for them. Yeah I never hear back from most of them. (I have a bit more than 1 year of experience) I don't wanna work for FAANG, I'd just like an entry/middle job on an industry I like

Newer Dev here. Just recently started in a position as a developer. I'm tasked with consolidating our monitoring systems into one cohesive display. After lumping together all the indexes and helping build a custom API I'm now working on front end. Front end is easy, I've done it before. Should be no problem. I was wrong. I spent a whole day fiddling with a React dynamic table and the CSS to format it. Today, I stumble upon the react-table component. Got the results I was looking for in less than 2 hours. I'm convinced that this was a lesson better learned early on.

Are you worried about your development environment becoming more and more unstable?

Let me give you an example: I've been (mostly) a .NET developer for about 10 years now and yes Visual Studio crashed sometimes but not very often. Also whenever I found something that seemed like a bug in e.g. the MVC framework I always realized that the problem was in my code. However recently there is a VS update almost every week, and I more and more often bump into open GitHub issues without a fix.

Is this the same with other development environments? I also had a lot of issues with XCode/Swift but I never expected that to be stable...

I think I'm a good developer. I have pretty decent debugging skills, including pulling apart disassembled x86 and other architecture code.

I'm fascinated by how things work.

But almost everything is catered for by a library. Or has already been done.

I find it enjoyable to create a library or program myself, but get disheartened when I find some library or program that is written seemingly very well, compared to my own code. And then I start to think I'm not a good developer after all.

Sort of relates to my previous rant about repeatedly rewriting code.

Applies to me doing programming as a hobby but probably affects my code at work as well... I just can't help but think my code is probably awful compared to what someone else might write.

...then I see incredibly ugly, messy, badly written code by other people and I feel better...

I suppose it is like an artist who sees amazing works but cannot paint to that standard, but is well beyond drawing stick figures with crayons.

Sounds like a trivial problem but it probably impedes my progress with a lot of things.

I have a problem!

I used to love programming and I really had a passion for it! I was a fast learner and realized quickly that I had a talent for this. It felt obvious that I should go for a career as a software developer! I have now been working with this professionally for about 2.5 years and I already hate it! I'm not sure if it's the job or the career that I hate but all my creativity and passion for this is gone! I feel like it's way too early to get tired of a career!

Has anyone else been through something similar? Is it a phase? Should I get a new job? Should I change career completely?

As we currently see a lot of codeless software platform, in the next 10 years there is gonna be high demand for people to extend these shitty apps into something proper, just like it happened with wordpress. There is a key missunderstanding that writing code and developing an application are the same thing; they are not.
Once you can write code you sure ass aren't a developer, thats a grueling journey until then, and being able to create an application without code exaggerates the problem even further.

This week we had a live production issue that our staff were catching/fixing on the fly. We're a relatively small software team without any direct external customers, so this is not too unusual.

Unfortunately, the person in charge of dealing with these issues didn't resolve it during the work week, so we were stuck with it over the weekend. Said responsible employee left at 2:30 on Friday without figuring out how we'd deal with the problem without any staff in the office to intercept problem cases. Better yet, he drove all the way back, and was there from 3:30 to 4 and promptly left again without telling the rest of the team what was going on with the production issue. We asked how it happened, what it was, etc, but didn't focus on his fix (in hindsight, a mistake).

Since it's his job, I assumed that he would let us know what was up before he left on Friday. It turns out that he never addressed the production issue at all and just decided to leave.

A junior developer and I spent two hours contacting management (who, at this time are already at home with their families) to get clearance to either shut the system off or fix it. No one wants to give it and no one that's high enough up to approve the decision is available.

In the end, we asked the weekend mechanical support team (some friends of mine) to monitor the issue and they kindly accepted.

All of this could have been avoided if my coworker had either told us his plan earlier (so we could ask about the lack of coverage), gotten approval to shut it down for the weekend, or covered his own ass before he left for the day.

Ugggh. I get that we all make mistakes, but I really hope this guy shapes up soon.

I feel bad for a college:
She's an android developer, and i used to do ionic and now i moved to web.
Our manager asked her to learn ionic for some project and let me help her arround, i did, and she started working on that project, the result was bad for the fact that js itself is now to her, as for angular/ionic, and lets not talk about the cordova shit .. The problem is that he's blaming her and letting her work for extra hours to fix the issues .. I tried my best to help her, but i'm still feeling bad for her, thats not her fault that her manager let her jump into some shitty situation using some framework (language even) thats far from her knowledge.

So in the project I’m working on we were about to do a push to live, no major functionality just minor adjustments and nice to have stuff. One of the things I did was a reminder, nothing special just sends an email out if something hasn’t been done for 3 days and then sends an email every day following. Push to live and every thing goes fine with no issues. Day 1 there are no issues. Day 2 there are no issues. Day 3 and I’m inundated with people telling me that the emails are getting sent to practically everyone, shit. What have I done? What have I missed?
So I start looking at the live database hoping for a data problem, no such luck. I look at my code looking for something blatantly obvious but nothing. I start replicating the data but I can’t reproduce this bug and it’s annoying the hell out of me. I checked one of the emails that the client sent to us more thoroughly and seen that it was sent at 07:01. This is odd as our webjob runs at 1am so I start looking at environmental factors and started looking at release management, more out of hope than expectation. I check the staging environment and see that the webjob ran at 7:00. Coincidence I thought, the webjob gets packaged on the release pipeline and everything in the database was dummy data anyway but I’d better check anyway. The database was an exact copy of the live database, turns out a “senior developer” wanted to sanity check everything by running live data through the code so he copied the database over. It was fine for the first couple of days but the data was now 3 days out of date triggering my email code and I get hit with the shit storm. I’ve never met such an incompetent developer in my fucking life, functions 700 lines long, classes that are over 20000 lines, repetition every where and the only design patterns he’s used is when he picks up a child’s colouring book. I can live with the fact that he writes code like someone on their first day of University But copying a database because he wants to “visualise” the fucking data is absolutely farcical. No wonder the project is fucked with a “developer” (in the loosest possible use of the word) is at the helm.

Alright, buckle up, fellow developer, because we're about to embark on a thrilling journey through the world of code and creativity!

Listen up, you amazing code wizard, you're not just a developer. No, you're a digital architect, a creator of worlds in the virtual realm. You have the power to turn lines of code into living, breathing entities that can change lives and reshape industries.

In a world where everyone is a consumer, you are a producer. You build the bridges that connect our digital dreams to reality. You are a pioneer, an explorer in the vast wilderness of algorithms and frameworks. Your mind is the canvas, and code is your brushstroke.

Sure, there are challenges—bugs that refuse to be squashed, deadlines that seem impossible, and technology that evolves at warp speed. But guess what? You're not just a problem solver; you're a problem annihilator. You tackle those bugs with ferocity, you meet those deadlines with gusto, and you master that evolving technology like a maestro conducting a symphony.

You live for the 'Aha!' moments—the joy of cracking a complex problem, the thrill of seeing your creation come to life, the satisfaction of making a difference. You're a digital superhero, swooping in to save the day one line of code at a time.

And when things get tough—and they will—you dig deep. You summon that relentless determination that got you into coding in the first place. You remember why you started this journey—to innovate, to leave your mark, to change the world.

So, rise and shine, you coding genius! Embrace the challenges, learn from the failures, and celebrate the victories. You are a force to be reckoned with, a beacon of inspiration in a world that needs your brilliance.

Keep coding, keep creating, and keep being the rockstar developer that you are. The world eagerly awaits the magic you're about to unleash! Go and conquer the code-scape! 🚀💻

I have an idea and I want some feedback.

I'm the only web developer and I've been updating our systems so they can be maintainable. Previously we have used Wordpress for landing pages which is complete overkill So here's the idea:

Static sites for landing pages and any forms that would need to filled out would be on a separate site.

Ok so here me out. First the landing pages barely need any maintenance so using pure HTML/CSS/JS wouldn't be a problem. This means I can strip away all of the crap from Wordpress and make the load times faster. Second all of the landing pages forms would be hosted in a single place making analytics easier for the reporting system.

Really I just despise Wordpress and am trying any practical reason to not use it as much as possible. Oh and don't worry I'll use preprocessors and minify the production files.

Some days I'm really not sure if I'm a developer or everybody's general problem solver because I'm an engineer and can think critically about your site configuration THAT YOU SHOULD BE ADMINISTERING YOURSELF!!!! AAAAAAAAAAAAAAAA

"Doesn't work, must be the dev."

Wrong. You misconfigured something and fucked it up. Figure it out yourself - actually read the error message right in front of your face - and don't waste my time.

some guy asked me to look at his react project,

I'm yet to find out the problem with his routing but look at this dependency list.

for a simple frontend project, I really dont know how many lazy developers are being introduced into the javascript ecosystem,

might seem normal to others but it feels wrong to me, as a beginner developer who isnt even dealing with a deadline

or......... maybe they are just plain clueless that they dont realize this level of redundancy

So today, i talked to my manager about my burnout and she offered the extra resources to help my project. And if nothing goes wrong, i’m going to take leave for 2 weeks by next week.

My advice, we are human and developer is special human. So, talked to your manager or boss about your problem, it’s their job to help you on this.

On last thing, i hope you guys pray for me and i hope i can be a better person once i comeback. 👌

Dev: Hey this library you are mandating the use of doesn’t do one of the things you assumed it does

Non-Tech Manager: Well I think it does because I looked at it and that’s what it seemed like and the only reason you can’t figure it out is you are a bad developer and have attitude issues that’s why you are failing. You need to look on the bright side of things more often. This library has over 100k downloads which means it must do what people want it to. I think the problem is you. We can’t spend anymore time on this we have to just fix it and move on.

I have a confession to make...I am a PHP developer with a Python problem!

I don't know if this is exactly a rant. But - I am sure somewhere out there has run into this situation before.

I've been a developer (professionally) for a 3 years. And in that time I've stayed with that same company.

Over that time its become incredibly apparent that my boss (senior developer) isn't exactly keen on new technologies, source control (I had to push hard for this. And even then he doesn't use it properly), or any kind of project management. It's only he and I.

I've started interviewing other places and while I have no problems answering their technical questions. I'm worried my lack of experience in a team is becoming a problem.

We don't work on projects together. We don't do code reviews. He does not ask my opinion on anything. We are basically two separate teams. I want to improve as a developer. I love the rest of the company and I enjoy what I'm working on. I just feel I'm hindering my growth as a developer.

Anyone have any advice? I know I can find a project to contribute to on github or something. But honestly that's intimidating to me for some reason. I am self taught. And don't have any experience in working with teams.

Started a new job as junior developer. One of my first task was to sent a simple notification on an event in out product. Write the code, test that it works, push to devops.

Code compiles, tests pass, it’s deployed to internal test env. Check that my notification works in the test env. No problem.

It’s deployed to the customers test environment. It works and customer accepts it for prod.

We release to prod and of course it fails. Seems to be a simple string.Format that fails for god knows why. After 3h of debugging on prod without success we decide to roll it back.

Today we decided to try it on a backup of the prod db since one of the strings was taken from the db. Still working. No matter what data I input when trying it locally it still wont reproduce the issue we saw on prod.

Fuck this

Fuck it, fucking fuck it.

Consulting company, been here for 2 years, had some decent projects (surprise, only those that me and my coworker started from scratch), but OMG the fuck ton amount of bizarre code I've seen is just mindblowing.

Everytime I start on a project, spend days improductive because the stack won't fucking work.

We use some frameworks, but the creators of the projects said fuck it, why would we follow the framework guidelines if I can create a supersmart way that nobody fucking understands way of doing things. I mean, It will look smarter and so nobody else can touch this shitty code.

I hate that the most praised developer is the guy that created most of this shit, and his nº 1 skill is moving Jira tickets to the correct state, tracking time (PM's love this, I hate it) and blocking my fucking merge requests because I left an extra blank line, dangling comma or whatever the fuck else, he's like a human linter.

Dude, the code is a piece of shit, my dangling comma is not going to be the problem! And if you really care that much, setup a linter or something.

Fuck this, I'm quitting this week.

I’m an idiot. Stackoverflow issue that I documented to a T. Javascript. So I put requirement of not having jquery or framework.

Get a comment about do I know it is working? My answer, debugging. They respond back with a question about debugging and some details I totally didn’t read.

Well, that was the bug. Chrome debugger was showing a message I didn’t understand. So they answered my problem perfectly.

But before realizing he answered my issue, I blew up. Of course I know what is going on. The debugger is showing me....did you even run my example?

I almost felt like giving up as a developer. Here is this awesome guy, solving my issue, and some dumbass like me has to be frustrated. Now he won’t respond to take a bounty he so awesomely deserves.

I’m still a dev. I just don’t feel so professional anymore...

Title: The problem with "good enough" code

Body:

I'm a software developer, and I've seen my fair share of "good enough" code. You know the kind of code I'm talking about: it works, but it's not pretty, and it's not very maintainable.

The problem with "good enough" code is that it's a slippery slope. Once you start writing "good enough" code, it's easy to fall into the trap of always taking the easy way out.

Before you know it, your code is a mess of hacks and workarounds. It's hard to understand, it's hard to maintain, and it's a nightmare to debug.

I've seen projects go down in flames because of "good enough" code. The code was so bad that it was impossible to fix, and the project had to be scrapped.

I'm not saying that you should never write "good enough" code. Sometimes, you just need to get something working, and you don't have the time or resources to do it perfectly.

But if you're going to write "good enough" code, you need to be aware of the risks. And you need to make sure that you're only writing "good enough" code for a short period of time.

Once you have a working prototype, you need to start refactoring your code and making it better. You need to make it more readable, more maintainable, and more testable.

If you don't, you'll eventually regret it. Your code will become a liability, and it will hold you back.

So next time you're tempted to write "good enough" code, think twice. It might save you some time in the short term, but it will cost you in the long run.

Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.

Fucking Power Apps and Automate/Flow:
You want to make an app?, great!
- Easy UI and editor, you can make a decent app in a day
- Best data integration in MS space bar none, connect to anything under the planet no problem.
- Deployment on mobile and desktop instantly and at scale, you better believe it.
- Wanna take from sharepoint, manipulate the data and throw it at XRM, we gothcu.
- Source control? FUCK YOU FOR ASKING GO DIE IN A FIRE.
- Proper permission system, Yep, based on O365 and azure AD
- Just let me get the source code please?: BURN IN HELL MOTHERFUCKER
- Integrated AI, indeed we have it. And chatbot frameworks on top of it, no problem at all
- ...

As a tool it is aimed at non technical people, not by making it beginner friendly, but by making it developer hostile. And whenever you hit a wierd quirk in the editor you wish you could just go edit the source code (WHICH YOU CAN TOTALLY SEE SNIPPETS OF), but you are never allowed to touch it.
I am so very tempted to make a version control layer on top of it myself, scraping it via scripts and doing the reverse on upload, but it will be janky as fuck.

After a code review where I identified an odd way a request was being generated, I suggested to the developer to utilize the Strategy pattern.
Knowing that the Strategy pattern probably wouldn't make sense in the current context, I told him I would put an example together by the end of the day.

I throw something together, sent it to him.

Go to the restroom, come back and 'Bob' says..

Bob:"There is my hero. Justin said you saved the world again. What was it this time? World hunger? Global warming? Ha ha ha."

Frack off you condescending kiss ass. Why don't you take 5 minutes to listen and understand the problem Justin was having instead of making fun of him?
Yea, I heard you this morning laughing at his code, monday-morning quarterbacking a solution in which you have no idea whats going on.

Heard your days are numbers anyway. Good riddance.

How do you deal with a developer that constantly challenges your propositions in a rhetorical matter?

For example, say if we have a problem and I propose solution A (along with my reasons why), the developer would then shoot it down - not with another alternative solution or exploration path but instead a rhetorical question.

It has gotten *exhausting* working with this person because every interaction becomes almost a debate. This isn’t just particularly with development but even during casual discussions.

I’ve even tried asking “so what would you suggest?” in which they would answer with confidence in a rhetorical matter - but without any concrete decision making (but at the same time sounding like they did make one).

We work in a team and nobody has taken the reigns of leadership (he’s quiet most meetings), so I decided to take initiative and make the calls. All of a sudden, he has a voice that is mostly axed towards being argumentative than productive. It has come to a point where I’ve just stopped making propositions because I’ve become exhausted trying to defend myself and literally repeating something like 4-5 times, however this is a project that needs to be delivered and because we work closely together, I can’t just ignore him and do my own thing.

When you are asked a complicated linked list problem in frontend developer interview.

Hey guys, hope you all have a great day.

I am not a professional developer yet because I still didn't have my first client. My goal is to become a freelance Web Developer.

At me moment I working on my own website because I can't hope to find a client if I don't even exist on the Internet.

I already have some kind of prototype but the problem is that it looks really bad in my eyes because I'm anything but a designer.

So my question is if you know any resources where I can learn web design, trends, good practices, theories, anything really.

Hi developers.... so i just feel like posting this post

I'm a self-taught developer its been 6 years now and i managed to get myself a job this year at a tech startup and they actually developed this developer department just for me..... with the promise that if i manage to get this department up and running I'll get a higher position as the company grows

So it's been 4 months now and i think i'm doing exceptionally well as a developer since I'm the only developer in that organization..... and some how I feel like if i use my problem solving skills to work on other real world problems not just code and designing systems..... like bringing solutions to real none code related problems i could actually achieve more and make a big difference

but I'm actually learning a lot and hope i'll become more and do more within this organization and grab that top position role

Reasons to NOT be a dev sounds rather negative so I'd like to propose 3 things that you need to BE a dev as to frame it in a positive light:

- When a problem peaks your interest you want to solve it, you may even be obsessed by it.
- You enjoy learning, not necessarily enjoy school, just enjoy learning new things (even better if it's by your own means)
- Failure may get you down, but you learn and don't give up until you have exhausted all paths to success.

You may need other skills like math, logic and reasoning abilities, being able to handle deadlines, attention to detail, and cope with stress. I've seen people being crap at all of those and if they have the former 3 they, in time, will hone the others enough to make them a productive dev.

No need to be a 9-9-6 code monkey willing to be squeezed by Big Corp for massive profits and a low salary or a 1337 purist coder that only focuses on the crafting side of developing software. That may make you a great coder but not a well rounded developer or individual. Remember, you program machines but you are NOT one.

Definitely Jon Skeet. Not only is he #1 on stackoverflow. He is actively tackling the hardest problem of them all: Time zone.

Closely followed by Joel Spolsky. The founder of stack overflow. Feels like all his products (fogcreek, trello) revolutionizes developer productivity and addresses actual pain points

The joys of bring a Fullstack developer..

Sometimes beings junior Fullstack developer I find myself in tricky situations.

This past week I was invited to a meeting with all the front-end developers where we were presenting our software when a 500error popped up...( I was day dreaming looking out the window watching two birds hop around)Then I heard one developer ask what the problem was and another quickly replied "backend problem"... Still half asleep and deep in my new found interest in birds I blurted out "maybe the front-end is not sending the request properly".... Immediately the room fell silent... this sent a chill down my spine and I was brought back to reality, I looked round the room and everyone was staring at me like I insulted their mothers... I tried to make a joke of it but saying "Sorry I forgot this was a front-end meeting"... The lead architect who for some reason was also present then said "at least someone sees things differently"... And everyone laughed (although I'm not sure how sincere their laughs were).

Turns out: Pearson VUE is bad at communication. After I reserved the Microsoft certification exam, it was adjusted with my accommodations. So I didn't entirely die (only a little) and was allowed to have my life saving fidget 'toys' with me and just be myself with my stims.

So after all that hassle, I am now certified Azure developer associate. \o/

Looks good on paper, doesn't solve the problem of getting through the project interviews. (To normies, I seem ever so slightly off and the natural instinct is to perceive me as a liar.)

If you are a developer and you are proud of the work you contribute whilst remaining open minded, I applaud you. If you are a developer and you are overly proud of what you do, and you believe the work you contribute to a software project caries more value than the work another developer contributes, then go fuck yourself.

I am sick and tired of working on teams with people who are self-righteous. What you bring to the table is important, but it isn't the only thing brought to the table, so stop acting like what you brought to the table is the best thing on the fucking table.

What makes it worse is when someone disagrees with your work and you aren't willing to take any of it. You deny their opinion as if yours is vastly superior. YOU need to improve your teamwork skills, YOU need to stop being so arrogant and self-righteous, YOU are the problem.

Soo... Let me get this straight... My boss reeeeeeally wants me to reconfigure our database system to sync data between each of our 15 sites... Let me this about this...

Our database is an MS Access database originally written about 17 years ago. It was written as a standalone database that runs a unique instance for each of our sites.The person responsible for the database (still not the original developer) before I took over 6 years ago bragged about how they were "an 80s developer" (w...t...f!). Even with all of the fixes and additions (additions because... F&$#ing of course there are!) It's still basically held together by duct tape and spit.

Hmmm... Ok, still possible. What's the environment I'm working in... I have absolutely ZERO control of our workplace network... That's a whole other department. Due to the nature of the workplace (and it's sites) there is extreme limitation on network access.

Well... If I'm Reeeeeeally nice to the people in charge of the network, maaaaaybe they can give me access to a little server space.

A very long shot, but, doab.... Oh, the boss would really like this handled in the next couple months...

F$#k you! There is no way on God's (still) green earth that I... Alone... Can rewrite a legacy database... written across 4 or 5 different versions of FU$KING MS Access, and give 15 sites, with extremely limited networking, real time data sync in... Oh, a few months.

Now, I do not work with "computer people". I'm usually lucky when my coworkers remember their passwords (which, even if they don't, WHY tell ME! I don't run the network!)

And when I tell my boss basically what I just said... In a nice, pleasant way... They suggest I'm not giving the problem enough thought...

FU#K YOU IGNORANT ASS! Write me a ToDo list in MS Access (no, I'm not going to tell you where to start) in under an hour then, MAYBE, we can talk about... No... Just NO... Can't be done!

*Takes deep breath* so... Lovely weather we're having, right?

Just started as an intern as a web developer in a small company. I have about 4 semester of coding experience and was hoping to learn a lot new things. Well it turns out that the main developer who's responsible for building our product has no fucking clue what he's doing. Our biggest document has about 6k lines and it kills my 8 GB ram notebook. Instead of writing one nice function, solving the problem which is occurring frequently, he wrote the same fucking thing multiple times... In the same fucking document. That's just one of many things.
Well now my job is mostly trying to stay cool, while my notebook gets hot af and somehow keeping my code OCD bearable

A famous quote attributed to Jamie Zawinski:
"Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems."

I am living this nightmare. Joined a project where schmucks are parsing SQL using regular expressions. Talked to a friend, a compiler developer expert. He told me that regexes can't be used for checking if braces are matched. Pumping Lemma. Those fuckers should have used ANTLR or something. Anyways planning to leave this project.