*code doesn't work*

-Run three times, just to be sure
-Its NOT the code, must be the project. Full rebuild.
-Run a few more times after rebuild didn't fix it.
-Google the issue.
-Stackoverflow must be wrong. The code is JUST like their solution.
-Run a few more times, but with your lucky underpants
-Reboot. Must be an operating system thing.
-Tea break. Give the issue time and it will fix itself.
-Run a few more times. Still unfixed
-Contact customer support.
-Walmart said they can't help.
-Consider writing your own language without this OBVIOUS flaw
-Kickstarter for c++++
-Raise $50,000
-Start a family
-Contact customer support again
-Run a few more times
-Now banned from Walmart
-Oh shit, missing a semicolon

It happened.

I wrote "you're missing a tab in your python code" as an answer on StackOverflow.

I was downvoted AND told that I wasn't correct: it was missing 4 spaces and not a tab, according to the python guidelines.

Now, I haven't read them, but my Richard Hendrix fucking intensifies.

Fuck spaces. And if python guidelines talk about spaces, fuck python guidelines too!

I'm not an iOS expert, I just wanted to get Google ads on my iOS app so that I could make a few petty dollars at the expense of my users. Is that too much to ask?

I started by following Google's instructions: install cocoapods, copy and paste some swift code... Compile failed, app broke. Carefully retrace my steps. Nothing.

Stackoverflow (praise be with them) suggests upgrading Xcode. Go to app store and click to upgrade Xcode. No progress bar, no status updates, just that pissy little spinner for several minutes. I become impatient try a few more times. It ain't happening.

Stackoverflow (holy of holies, defender of the weak) points me to an alternate source for Xcode, on the app store dev console. 4GB and some time later, an attempt to unzip gives "unknown error". Genocide of sorts.

Stackoverflow (all that is pure, all that is kind, all... I think you get it) says upgrade your OS. I tried months ago but I had issues with that pissy little spinner. Persist. 5GB and a "heavy-year" of time later (sorry), it installs. Then Xcode installs. Then bar a few errors, the app compiles.

So after almost 24 hours, life resumes. The lesson.. respond to all obscure iOS errors by upgrading. If fully upgraded, calmly acquire a baseball bat and destroy your machine. Make sure you have a good book nearby in case of either event.

Thank you for reading my rant. Now if you'll excuse me, I have to pay Apple
$150 so that I may list my app in the app store.

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

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

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

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

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

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

This week I quit the corporate life in favour of a much smaller company (60 people in total) and i never felt so good.

After 3 years in 2 big corporations, I began to hate coding mainly because of:
- internal political games. It's like living inside House of Cards everyday.
- management and non-tech people choosing tech stacks. Angular 4 + Bootstrap 4 alpha version + AG-Grid + IE11. Ohhh yeah. Not.
- overtime (even if it was paid double). I never did a single minute of OT for fixing something that I caused. I spent days fixing things caused by others and implementing promises that other people made.
- meetings. I spend 50-60% of the time in pointless meetings (I tracked them in certain time intervals) but the workload is same like I was working 8 hours / day.
- working in encapsulated environments without access to internet or with limited access to internet (no GitHub, no StackOverflow etc.)
- continuously changing work scope. Everyday the management wants something new introduced in the current sprint/release and nobody accepts that they have to remove other things from the scope in order to proper implement everything.
- designers that think they are working for Apple and are arguing with things like "but it's just a button! why does it take 2 days to implement?"
- 20 apps installed additionally on my phone (Citrix Receiver, RSA Token, Mobile@Work Suite etc.) just to be able to read my email
- working with outdated IDEs and tools because they have to approve every new version of a software.
- making tickets for anything. Do you want a glass of water? Open a ticket and ask for it.
- KPIs. KPIs everywhere. You don't deserve anything because the KPIs were not accomplished.

The bad part of the above things is that they affect your day-to-day personality even if you don't see it. You become more like a rock with almost 0 feelings and interests.

This is my first written "rant". If anyone is interested, I will post different situations that will explain a lot of the above aspects.

Life lesson learned:

If your girlfriend asks you what SO means, it's "Significant Other",

NOT StackOverflow.

I'm 20, and I consider myself to be as junior as they come. I only started programming seriously in June 2016,and since then, I've been doing mainly Android Work, and making my own servers and backends(using AWS/Firebase nd stuff).
For the first time in life, I was approached by a recruiter for a company on linkedIn. They "stumbled upon" my Github profile and wanted to see if I was interested in an internship opportunity. This company is an early stage start up, by that I mean a dude with an idea calling himself the CEO and a guy who "runs a tech blog" and only knows college level C programming (explaination follows).

So they want me to make the app for their startup. and for that, I ws first asked to solve a couple problems to prove my competence and a "technical interview" followed.
They gave me 3 questions, all textbook, GCD of 2 numbers, binary search and Adding an element to the linked List, code to be written on a piece of paper. As the position was that of an Android Developer, I assumed that Java should be the language of choice. Assumed because when I asked, the 'tech blogger' said, yeah whatever.
But wait, that ain't all, as soon as I was done, Mr. Blogger threw a fit, saying I shouldn't assume and that I must write it in C. I kept my cool (I'm not the most patient person), and wrote the whole thing in C.
He read it, and asked me what I've written and then told me how wrong I was to write 2 extra lines instead of recursion for GCD. I explained that with numbers large enough, we run the risk of getting a stackoverflow and it's best to apply non recursive solution if possible. He just heard stackoverflow and accused me of cheating. I should have left right then, but I don't know why, I apologized and again, in detail explained what was happening to this fucktard. Once this was done, He asked me how, if I had to, I'd use this exact code in my Android App. I told him that Id rather write this in Java/Kotlin since those are the languages native to Android apps. I also said that I'd export these as a Library and use JNI for the task. (I don't actually know how, I figured I can study if I have to).
Here's his reply, "WTF! We don't want to make the app in Java, we will use C (Yeh, not C++, C). and Don't use these fancy TOOLS like JNI or Kotlin in front of me, make a proper application."
By this I was clear that this guy is not fit to be technical lead and that I should leave. I said, "Sir, I don't know how, if even possible, can we make an Android App purely in C. I am sorry, but this job is not for me".
I got up and was about to leave the room, when we said, "Yeah okay, I was just testing you".
Yeah right, the guy's face looked like a howling monkey when I said Library for C, and It has been easier for me to explain code to my 10 year old cousin that this dumbfuck.
He then proceeded to ask me about my availability, and I said that I can at max to 15-20 hours a week since my college schedule is pretty tight. I asked me to get him a prototype in 2 months and also offered me a full time job after I graduate. (That'd be 2 years from now). I said thank you for the offer, but I am still not sure of I am the right person for this job.
He then said, "Oh you will be when I tell you your monthly stipend."
I stopped for a second, because, money.
And then he proceeded to say 2 words which made me walk out without saying a single word.
"One Thousand".

I live in India, 1000 INR translates to roughly $15. I made 25 times that by doing nothing more than add a web view to an activity and render a company's responsive website in it so it looks like an app.

If this wasn't enough, the recruiter later had the audacity to blame me for it and tell me how lucky I am to even get an offer "so good".
Fuck inexperienced assholes trying shit they don't understand and thinking that the other guy is shitsworth.

Day 1 10:00 am
Login to email account (Zimbra)
Your password is incorrect (I entered it correctly, this was a permanent issue ,used to happen in the company with many employees)
Reset your password by logging into internal company portal.

11:00 am
Logged into company portal, somehow. 2 Mbps internet shared among 104 people, you can imagine the speed.
Reset email password
* your password has been sent to your email id*
Are you fucking kidding me? U have emailed me the password to the same email I can't log in to?
Where did the architecture designer get this top notch weed from?

Day 2
Asked HR to reset my password (using a colleague's email)

Day 3
No reply from HR yet

Day 4
I went to meet HR, she's on vacation. So they have 1 person managing the password reset, for 5000 people with no backup person. Cool.

Day 5
Your internal company password has expired. Check your email for link to create new password. This is some next level shit going on.

Day 6
I called up Internal IT team to generate a new email for me.
They asked me to raise a ticket.
I can't raise a ticket because the only way to do so, is through the portal.

Day 7
Nothing. Btw, personal email and all social networks were banned. You can't even open stackoverflow.
And this was a research lab, amazing huh?

Day 8
Loss of pay for 4 days since I can't login to company portal to fill timesheet.

Day 9
HR comes back. Resets my password.
I try to generate my new password for portal.
The password policy:
Password can't be same as last 10 passwords
Passwords expire every week
8 characters minimum, 2 upper case, 2 lower case, NO SPECIAL SYMBOL. WTF. How long do u think its gonna take to crack that?

Fuckers had a company wise policy to automatically lock PC every 1 min if not used. Who the fuck can keep on using it continuously! I'm reading an article, and bam ! Locked. 2 wrong entries and that's it, repeat all steps again. Fuckers really didn't want to let me do my job, just keep on logging in all day.

Dear, Random guy that I wrote you an answer on StackOverflow.

I spent 15 minutes GOOGLING the issue for you because you either were fucking lazy or don't know how to use Google.

I wrote an answer for you on your shitty question with -2 rep explaining how to solve the issue and you just replied thanks and didn't even bother to either upvote or accept my answer. Not only did I solve your question I did it to bloody help you and here you are with your attitude not accepting my answer, and replying with thanks that i feel like you didn't care for me writing your answer. You can bloody hell burn in hell. I hope there is a special place for you and people like you that magically go missing and never come back

It wasn't my curiosity that introduced me to programming. Actually, it was my mother.

It was about six years ago, when I'd told her I'd like to make video-games, like all kids do. She didn't just nod and go about her way. She found a free course that taught programming to kids my age and immediately enrolled me. Looking back, it was surely the best thing she'd done for me, because it gave me a purpose and a future to look forward to.

The course was interesting. We learned the basics of C++, then moved on to harder topics like algorithms and data types. But more and more, I was beginning to feel left behind. Like I didn't belong there. It didn't help that I only programmed on the course, with no practice back home.

I felt scared of the future. Thought I didn't have what it takes to become a programmer. I might have broken the last straw when I started playing truant and went to McDonald's to pass the time. Because every time I did go to the course, I felt stupid and anxious. So I simply skipped.

Time passed. I got more depressed, became more antisocial, my self-esteem took a nosedive. And when it comes to depression, people always seek an escape path.

I got my escape in fiction. Started reading books, tried writing stories, and it got to the point where I asked my mother if I could become a writer and not a programmer.

And guess what? She said, "Do what brings you happiness. This is your life."

It's funny, that such a silly line stopped and got me to think. Turned out, I didn't program for fun, for myself or for my career. I'd done it for my parents, for their expectations and I was scared that in failing, I'd become a loser in their eyes.

I dropped out of the programming course. Not because it sucked, but because I wasn't going there for myself, but for my parents. But I didn't quit programming. No, I watched countless tutorials, youtube videos, browsed StackOverflow, read some books, coded every day, and now I can say without hesitation, that I love programming. I'm hooked. And I don't want to stop.

If you've read this so far, I'm sorry for my rambling. I will now leave you with only one tip: If you decided to do something, do it for yourself. Forget about parents, expectations, career, future, time or money and do it only because you want to. Because nothing else matters. Only your happiness.

Hold your keyboard! Hold your mouse!

Sons of Java, of Python, my brothers,

I see in your eyes the same fear that would take the heart of me.

A day may come when the sense of programming language fails,

when we forsake our logic

and break all the laws of programming,

but it is not this day.

An hour of headache and shattered monitors,

when the age of Javascript rises,

but it is not this day!

This day we will find solutions on StackOverflow!!

By all that you hold dear on this good code,

I bid you stand,

Developers!!!

Here's the time an Amazon recruiter scheduled a call with me just to tell me I wouldn't be getting the job.

A few years ago, I left Uber after the seemingly non-stop public snafus they were getting themselves into (I have a lot of rants about Uber if anyone is interested, some of them mind-melting). I decided to take a two month break given that my financials looked decent for once and I was tired of 100 hour weeks.

During that time, I of course started perusing the typical job-seeking sites I had remembered from before. Somehow, from one of the profiles I set up, I caught the eye of an Amazon recruiter. They emailed me and I agreed to set up a date and time for an introductory chat.

They already had my CV. They already had my StackOverflow/Github information. This wasn't a technical interview, and the recruiter wasn't part of any of the tech teams. This is important information moving forward.

A few days later, I got the call from the recruiter. He introduced himself as the person from the emails, thanking my for my time, etc.. Things started out pleasant with the smalltalk and whatnot, but then the recruiter said "so I have some concerns about your resume".

Under one of the sections I had a list of things I was skilled with - one of which, regrettably, is PHP. Completely ignoring Java, Javascript, C# and C++ knowledge and all of the other achievements I have with those technologies, the recruiter really wanted to drill me about the PHP.

"Do you work a lot with PHP?"
"No, not anymore - from time to time I have to do something with it but it's not my main language anymore. I know it quite well, though."
"Oh okay well we aren't looking for any PHP roles right now, unfortunately."
"Okay, no problem."

Perhaps I could have said more, but from my end of things, I meant "I don't see a problem here, I don't write a lot of PHP and you don't need a lot of PHP".

After a pause that felt like an hour, the recruiter broke the silence and said "Okay well thanks for your time today, I'm sorry things didn't work out."

Bewildered, I asked which technology stack they were using on the team.

"Not PHP, unfortunately. Thank you for your time." and then an abrupt click.

The recruiter found me himself, looked at my resume (assumably), sought out to contact me, arranged a time for a call, and then called me, just to tell me I wouldn't get the position due to knowing PHP at some point in my career.

Years later, the whole interaction still shocks me. Somewhere in my drafts I have a long letter to the recruiter basically going over my entire career history explaining why his call was incredibly... well, fucking weird. Towards the end of writing it I realized it was more therapeutic for me to deal with whatever it was that just took place and that it probably wouldn't change my odds of working at Amazon.

So yeah. That's the story of the time Amazon set up a recruiting call just to tell me I wouldn't be working for them.

!firstRant

Can anyone relate to the fact that before you disturb your co-worker with an issue you should ATLEAST try fucking google?
Not to mention the documentation, stackoverflow, msdn, forums. Hell, once, I found the answer I needed on a freaking bakery forum.

Wtf is wrong with stackoverflow I asked a question I get it’s not easy to understand it to answer

But your instead trying to fix my grammar and punctuation! Wtf! It’s 100% readable

People on stackoverflow are obnoxious dicks

Let the student use their own laptops. Even buy them one instead of having computers on site that no one uses for coding but only for some multiple choice tests and to browse Facebook.

Teach them 10 finger typing. (Don't be too strict and allow for personal preferences.)

Teach them text navigation and editing shortcuts. They should be able to scroll per page, jump to the beginning or end of the line or jump word by word. (I am not talking vi bindings or emacs magic.) And no, key repeat is an antifeature.

Teach them VCS before their first group assignment. Let's be honest, VCS means git nowadays. Yet teach them git != GitHub.

Teach git through the command line. They are allowed to use a gui once they aren't afraid to resolve a merge conflict or to rebase their feature branch against master. Just committing and pushing is not enough.

Teach them test-driven development ASAP. You can even give them assignments with a codebase of failing tests and their job is to make them pass in the beginning. Later require them to write tests themselves.

Don't teach the language, teach concepts. (No, if else and for loops aren't concepts you god-damn amateur! That's just syntax!)

When teaching object oriented programming, I'd smack you if do inane examples with vehicles, cars, bikes and a Mercedes Benz. Or animal, cat and dog for that matter. (I came from a self-taught imperative background. Those examples obfuscate more than they help.) Also, inheritance is overrated in oop teachings.

Functional programming concepts should be taught earlier as its concepts of avoiding side effects and pure functions can benefit even oop code bases. (Also great way to introduce testing, as pure functions take certain inputs and produce one output.)

Focus on one language in the beginning, it need not be Java, but don't confuse students with Java, Python and Ruby in their first year. (Bonus point if the language supports both oop and functional programming.)

And for the love of gawd: let them have a strictly typed language. Why would you teach with JavaScript!?

Use industry standards. Notepad, atom and eclipse might be open source and free; yet JetBrains community editions still best them.

For grades, don't your dare demand for them to write code on paper. (Pseudocode is fine.)

Don't let your students play compiler in their heads. It's not their job to know exactly what exception will be thrown by your contrived example. That's the compilers job to complain about. Rather teach them how to find solutions to these errors.

Teach them advanced google searches.

Teach them how to write a issue for a library on GitHub and similar sites.

Teach them how to ask a good stackoverflow question :>

Fuck you StackOverflow! Why do you ban people who have a positive score? Shit, I'm raging right now. I have a positive fucking score! It is not because I asked a few questions that were not well received by your fucking elitist overrated frustrated community that I should be banned!
And fuck off I'm not a native english speaker, it is OBVIOUS that I won't be able to make perfect sentence in all contexts.

FUCK FUCK FUCK FUCK

Fuck off cancerous piece of shit on stackoverflow whose dick is an obvious inverse proposition to ego and incapablility to read.

I asked if there's "clean" way, of doing something. I provided my solution to the problem

Your answer and coments make it pretty obvious that you:
* don't really care about (code) quality
* value your reputation just as much as some teen on facebook sucking cook for likes or whatever they use now
* downvoted my question because you can't handle critique in the slightest
* You immediately replied with "but op said..." even though I am the fucking op and if I say _imo_ a fucking for-loop within function is less readable than 3 chained function-calls it and does not include the feature I asked for, it means you have to justify your answer and not get triggered and downvote my fucking question.

After I confronted him about this shit he just said "If you had studied the language for more than 10 minutes you would have known than you can't do that."

And if you had some a basic reading skill you could improve my workaround or tell me just that, instead of providing me with that useless information you vomited out just to get some ez SO reputation.

Piece of shit didn't even deny the anyyhing.

Shove a vibrator up your ass until it arrives at your skull and activate it. Maybe that will stimulate your brain or hopefully upgrade it.

I don't care how much "reputition" you may have "earned" on the internet. I am not afraid to call your bullshit or your sheer pathetic existence out.

People like this are are the reason SO gets so much hsge and even tough I got an improved version for my workaround (from an other user), I'm nowhere near happiness.

Note, the Useful-to-retarded-ratio is
1: 3

Never underestimate the power of developers on stackoverflow.

If you forget a single restriction they will find solutions that perfectly match your question but not your problem.

If your issue is not on StackOverflow and you can't find it on the web:

Go another way, you're probably doing something very wrong!

(I have solved many problems remembering this)

I'm currently rewriting perfectly clean and functioning Scala code in Java (because "Enterprise", yay). The amount of unnecessary boilerplate I have to add is insane. I'm not even talking big complicated code but two liners or the lack of simple things like a range from 5 to 10.

Why do I have to write
List<Position> occupiedPositions = placedEntities.stream()
.flatMap((pe) -> pe.occupiedPositions().stream())
.collect(Collectors.toList());
instead of simply
val occupiedPositions = placedEntities.flatMap(_.occupiedPositions)

Why on earth does `occupiedPositions.distinct` suddenly become a monstrosity like `occupiedPositions.stream().distinct().collect(Collectors.toList())` where the majority of code is pure boilerplate? And this is supposed to be the new and better Java8 api which people use as evidence that Java is now suddenly "functional" (yeah no, just no).

Why do APIs that annotate parameters with @Nullable throw NullPointerExceptions when I pass a null? Why does the compiler not help prevent such stupidity? Why do we use static typing PLUS those annotations and it still crashes at runtime like every damn dynamic, interpreted language out there? That's not unfortunate, it's a complete waste of time.

Why is a simple idea like a range from x to 10 (in scala literally `x to 10`) not by default included in Java? There's Guava's version of Range which does not have a helper for integer ranges (even though they are the most used ones). Then there's apache.commons version which _has_ a helper for integers, but is strangely not iterable (wtf I don't even...).

Speaking of Iterable: How difficult could it be to convert an abstract Iterable<T> into a concrete List<T>? In scala it's surprisingly `someIterable.toList`. I found nothing like that so I took to stackoverflow where I found a thread in which people suggested everything from writing your own ListUtils helper class, using Guava (which is a huge dependency!) to using the new Java8 features inline (which is still about three lines long). I didn't know this was such a hard problem in computer science, TIL.

How anyone can be productive in this abomination of a language is beyond me now, even though I've used it for many years while learning to code (back then I didn't know there were much better ways to do things). The only good part is that I have to endure this nonsense for only about 3 days longer then I'm free again!

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.

The moment when you find exactly your problem on Stackoverflow...

...just to realize its the same question you read about a year ago when you already had the problem but since it was minor and there was no solution so you ignored it up until now.

Followed by the feeling when you see that there was not even a comment added the whole year besides it was viewed 150 times.

Followed by the feeling when you find the solution all by yourself and finally write an answer to the question.

Just to realize that this was the only question from this guy on SO and his last login was two years ago. :-~

Well at least the annoying log message is gone and I learned something new.

I see many people being irritated when it comes to StackOverflow and If I were to be honest I thought the same a while ago. But I noticed that I was misjudging the main point of Stackoverflow. It's not a forum to help people with their programming problems. It's a huge self writing document to gather every programming related questions and answers under a single platform if possible. That's why they won't down vote you even if you ask a question that was obvious in a language's official document as long as it wasn't in Stackoverflow. That's why questions should also be formatted accordingly which is clear and also informative in itself. I understand why stackoverflow is such a harsh place to ask questions and most of the time I prefer looking things for my self instead of asking a question. And I edit and review most questions on stackoverflow because I enjoy it. That also made me realize that stackoverflow needs to be elitist to preserve it's current quality. Who would want to see unclear duplicate questions that veteran stackoverflow users need to answer over and over again right ?

Asking the right question is hard because we humans most of the time don't know what we don't know. And it makes it really tiring to format your question the way that is fitting for a document. In those times I prefer to ask my questions on a more relaxed and chat focused platform before writing my main question on stackoverflow.

So that was my opinion on stackoverflow and it's harsh environment. It's definetly a hard to get into community which I can't even say I'm really a part of it. But looking at stackoverflow as a document that's being written by ut's users, it's easier to understand it's elitist approach. I hope you had some enjoyment from reading it.

Franz is his name, he is our new programmer. He got task to made a calendar to display ongoing ads with javascript, and damn good he done it fast. Until today, he not coming because he got ill and i have to edit his calendar code because there's a change request.I look at his code and thinking how he read this code? no indentation, bracket everywhere, etc. Then I call him:

Me: Franz, can you explain your code to me?
Franz: Sure, but.. umm.. I forgot to bookmark the stackoverflow link.
Me: ...

I'm coming off a lengthy staff augmentation assignment awful enough that I feel like I need to be rehabilitated to convince myself that I even want to be a software developer.

They needed someone who does .NET. It turns out what they meant was someone to copy and paste massive amounts of code that their EA calls a "framework." Just copy and paste this entire repo, make a whole ton of tweaks that for whatever reason never make their way back into the "template," and then make a few edits for some specific functionality. And then repeat. And repeat. Over a dozen times.

The code is unbelievable. Everything is stacked into giant classes that inherit from each other. There's no dependency inversion. The classes have default constructors with a comment "for unit testing" and then the "real" code uses a different one.

It's full of projects, classes, and methods with weird names that don't do anything. The class and method names sound like they mean something but don't. So after a dozen times I tried to refactor, and the EA threw a hissy fit. Deleting dead code, reducing three levels of inheritance to a simple class, and renaming stuff to indicate what it does are all violations of "standards." I had to go back to the template and start over.

This guy actually recorded a video of himself giving developers instructions on how to copy and paste his awful code.

Then he randomly invents new "standards." A class that reads messages from a queue and processes them shouldn't process them anymore. It should read them and put them in another queue, and then we add more complication by reading from that queue. The reason? We might want to use the original queue for something else one day. I'm pretty sure rewriting working code to meet requirements no one has is as close as you can get to the opposite of Agile.

I fixed some major bugs during my refactor, and missed one the second time after I started over. So stuff actually broke in production because I took points off the board and "fixed" what worked to add back in dead code, variables that aren't used, etc.

In the process, I asked the EA how he wanted me to do this stuff, because I know that he makes up "standards" on the fly and whatever I do may or may not be what he was imagining. We had a tight deadline and I didn't really have time to guess, read his mind, get it wrong, and start over. So we scheduled an hour for him to show me what he wanted.

He said it would take fifteen minutes. He used the first fifteen insisting that he would not explain what he wanted, and besides he didn't remember how all of the code he wrote worked anyway so I would just have to spend more time studying his masterpiece and stepping through it in the debugger.

Being accountable to my team, I insisted that we needed to spend the scheduled hour on him actually explaining what he wanted. He started yelling and hung up. I had to explain to management that I could figure out how to make his "framework" work, but it would take longer and there was no guarantee that when it was done it would magically converge on whatever he was imagining. We totally blew that deadline.

When the .NET work was done, I got sucked into another part of the same project where they were writing massive 500 line SQL stored procedures that no one could understand. They would write a dozen before sending any to QA, then find out that there was a scenario or two not accounted for, and rewrite them all. And repeat. And repeat. Eventually it consisted of, one again, copying and pasting existing procedures into new ones.

At one point one dev asked me to help him test his procedure. I said sure, tell me the scenarios for which I needed to test. He didn't know. My question was the equivalent of asking, "Tell me what you think your code does," and he couldn't answer it. If the guy who wrote it doesn't know what it does right after he wrote it and you certainly can't tell by reading it, and there's dozens of these procedures, all the same but slightly different, how is anyone ever going to read them in a month or a year? What happens when someone needs to change them? What happens when someone finds another defect, and there are going to be a ton of them?

It's a nightmare. Why interview me with all sorts of questions about my dev skills if the plan is to have me copy and paste stuff and carefully avoid applying anything that I know?

The people are all nice except for their evil XEB (Xenophobe Expert Beginner) EA who has no business writing a line of code, ever, and certainly shouldn't be reviewing it.

I've tried to keep my sanity by answering stackoverflow questions once in a while and sometimes turning evil things I was forced to do into constructive blog posts to which I cannot link to preserve my anonymity. I feel like I've taken a six-month detour from software development to shovel crap. Never again. Lesson learned. Next time they're not interviewing me. I'm interviewing them. I'm a professional.

!rant

Trust no one.
The internet is not your friend, until you find stackoverflow and you get down voted.
That rm -rf / won't make you server faster.
System32 is needed.
Yes, that is a package manager, you don't need to write more ccode
Do not write commets on languages that only you speak, the team does not speak in latin.
Paint is the best engineering tool.
Keep a stress ball nearby.
Your client is always right, unless they mess with your coding skills.

True story.

I feel like there are more and more people who only THINK they can program, but in reality they barely can make the “Hello, world” program. Many of them come from all of these “online courses”, I’m not saying that from there come only the bad ones, but many of them are bad programmers, who just think that one or two courses is good enough.
You have to gain experience by doing actual work, not by doing pre-baked exercises. In real life most of things you have to solve with your imagination - Stackoverflow will only provide you some raw draw!

In the 1990s code editors on the Mac could insert the omitted function prototypes into a header file with one command; and even automatically keep the header declaration updated when you changed the source definition (name, parameters, etc)

Today in Xcode you have to copy and paste the stupid function header definition from the source code into the header file. What happens if you leave the "{" that got copied accidentally? OMFUCKING LORD, it triggers all sorts of erroneous errors in all the **source code** files where it is included instead of the header with the stray "{"

I started to question whether nor not I knew C, if gravity worked, if the sun would come up. I wasted a day of dicking around in StackOverflow trying to chase down all these insane error messages which make no sense in Xcode.

I just **happened** to see at the bottom of one of the source files, after all the erroneous error, a very important error:

"};" Expected

So I started deleting code from the bottom up in this source file, same error every time. Got to the point where the includes were all that was left.

FUCK YOU XCODE and the hacks that designed that horrendous piece of shit

Xcode is only free if your time is worth absolutely nothing.

Do these NPC devs even read the README of a project before spewing some dumbass stackoverflow like garbage in an issue thread?

Do your damn job. Being a good software engineer is not like TiKtOk or cHaTgPt where some "magical" answer or entertainment is spoon fed to you, do your absolute best to solve it yourself first, before causing more chaos out in the opensource world.

Me: Found solution on StackOverFlow, lets copy/paste code and try it out

*Clicks ctrl+v*
Computer: There's your value!
Me: Wait that's not what I copied
*notices that I copied from a different computer and expected it to paste on this one*

*cries in corner* T_T

I'm gonna decline the next time someone asks me "hop in chat with them" to discuss their stackoverflow problem.

I'd already given my two cents about the problem in question and I thought something was unclear about that so I say okay what the hell, made a chat room and invited him in.

Him: So I have this OTHER problem with [insert JS plugin]
Me: ... I don't know enough about it. I've used that specific plugin maybe once. The question I offered you my help with was PHP.
Him: Yeah but can you take a look really quick?
Me: I'd have to reread the documentation. I literally don't remember how to use it.
Him: No problem, here's the documentation. I want to do X, Y and Z.
Me: I don't think you can X without doing A and B first.
Him: I was told not to do A, so how can I do X, Y and Z?

Fucking hell I'm not gonna do your job for you. You know english. There is documentation available. Just read it and at least try things.

As a pretty solid Angular dev getting thrown a react project over the fence by his PM I can say:

FUCK REACT!

It is nigh impossible to write well structured, readable, well modularized code with it and not twist your mind in recursion from "lift state up" and "rendercycle downwards only"

Try writing a modular modal as a modern function component with interchangeable children (passeable to the component as it should be) that uses portals and returns the result of the passed children components.

Closest I found to it is:
c o d e s a n d b o x.io/s/7w6mq72l2q
(and its a fucking nightmare logic wise and readability wise)

And also I still wouldn't know right of the bat how to get the result from the passed child components with all the oneway binding CLUSTERFUCK.

And even if you manage to there is no chance to do it async as it should be.
You HAVE to write a lot of "HTML" tags in the DOM that practically should not be anywhere but in async functions.

In Angular this is a breeze and works like a charm.
Its not even much gray matter to it...

I can´t comprehend how companies decide to write real big web apps with it.

They must be a MESS to maintain.

For a small "four components that show a counter and fetch user images" - OK.
But fo a big webapp with a big team etc. etc.?

Asking stuff about it on Stackoverflow I got edited unsolicited as fuck and downvoted as fuck in an instant.
Nobody explained anything or even cared to look at my Stackblitz.
Unsolicited edit, downvote, closevote and of they go - no help provided whatsoever.
Its completely fine if you don't have time to help strangers - but then at least do not stomp on beginners like that.
I immediately regretted asking a toxic community like this something that I genuinely seem to not understand. Wasn't SO about helping people?
I deleted my post there and won't be coming back and doing something productive there anytime soon.

Out of respect for my clients budget I'm now doing it the ugly react way and forget about my software architecture standards but as soon as I can I will advise switching to Angular.

If you made it here: WOW
Thank you for giving me a vent to let off some steam :)

1. Focus on learning; earning should come secondary
2. If it doesn't add anything to your resume, it's probably not worth picking up
3. Do not re-invent the wheel. Explore third parties and libraries thoroughly. Use them as much as you can.
4. If you stuck at a problem for more than 2-3 hours: post on stackoverflow
5. Plan, create deadlines, and focus as if an executive chose you.
Lazy = failure!

Github 101 (many of these things pertain to other places, but Github is what I'll focus on)

- Even the best still get their shit closed - PRs, issues, whatever. It's a part of the process; learn from it and move on.

- Not every maintainer is nice. Not every maintainer wants X feature. Not every maintainer will give you the time of day. You will never change this, so don't take it personally.

- Asking questions is okay. The trackers aren't just for bug reports/feature requests/PRs. Some maintainers will point you toward StackOverflow but that's usually code for "I don't have time to help you", not "you did something wrong".

- If you open an issue (or ask a question) and it receives a response and then it's closed, don't be upset - that's just how that works. An open issue means something actionable can still happen. If your question has been answered or issue has been resolved, the issue being closed helps maintainers keep things un-cluttered. It's not a middle finger to the face.

- Further, on especially noisy or popular repositories, locking the issue might happen when it's closed. Again, while it might feel like it, it's not a middle finger. It just prevents certain types of wrongdoing from the less... courteous or common-sense-having users.

- Never assume anything about who you're talking to, ever. Even recently, I made this mistake when correcting someone about calling what I thought was "powerpc" just "power". I told them "hey, it's called powerpc by the way" and they (kindly) let me know it's "power" and why, and also that they're on the Power team. Needless to say, they had the authority in that situation. Some people aren't as nice, but the best way to avoid heated discussion is....

- ... don't assume malice. Often I've come across what I perceived to be a rude or pushy comment. Sometimes, it feels as though the person is demanding something. As a native English speaker, I naturally tried to read between the lines as English speakers love to tuck away hidden meanings and emotions into finely crafted sentences. However, in many cases, it turns out that the other person didn't speak English well enough at all and that the easiest and most accurate way for them to convey something was bluntly and directly in English (since, of course, that's the easiest way). Cultures differ, priorities differ, patience tolerances differ. We're all people after all - so don't assume someone is being mean or is trying to start a fight. Insinuating such might actually make things worse.

- Please, PLEASE, search issues first before you open a new one. Explaining why one of my packages will not be re-written as an ESM module is almost muscle memory at this point.

- If you put in the effort, so will I (as a maintainer). Oftentimes, when you're opening an issue on a repository, the owner hasn't looked at the code in a while. If you give them a lot of hints as to how to solve a problem or answer your question, you're going to make them super, duper happy. Provide stack traces, reproduction cases, links to the source code - even open a PR if you can. I can respond to issues and approve PRs from anywhere, but can't always investigate an issue on a computer as readily. This is especially true when filing bugs - if you don't help me solve it, it simply won't be solved.

- [warning: controversial] Emojis dillute your content. It's not often I see it, but sometimes I see someone use emojis every few words to "accent" the word before it. It's annoying, counterproductive, and makes you look like an idiot. It also makes me want to help you way less.

- Github's code search is awful. If you're really looking for something, clone (--depth=1) the repository into /tmp or something and [rip]grep it yourself. Believe me, it will save you time looking for things that clearly exist but don't show up in the search results (or is buried behind an ocean of test files).

- Thanking a maintainer goes a very long way in making connections, especially when you're interacting somewhat heavily with a repository. It almost never happens and having talked with several very famous OSSers about this in the past it really makes our week when it happens. If you ever feel as though you're being noisy or anxious about interacting with a repository, remember that ending your comment with a quick "btw thanks for a cool repo, it's really helpful" always sets things off on a Good Note.

- If you open an issue or a PR, don't close it if it doesn't receive attention. It's really annoying, causes ambiguity in licensing, and doesn't solve anything. It also makes you look overdramatic. OSS is by and large supported by peoples' free time. Life gets in the way a LOT, especially right now, so it's not unusual for an issue (or even a PR) to go untouched for a few weeks, months, or (in some cases) a year or so. If it's urgent, fork :)

I'll leave it at that. I hear about a lot of people too anxious to contribute or interact on Github, but it really isn't so bad!

1. Plan your work
2. Plan new skills to learn every year
3. Stackoverflow is your best friend
4. Don't be afraid to ask stupid questions...
5. ... but make sure not to ask too many of them
6. Don't get burned on one single topic, find other projects to work in parallel or even better work on side projects in your spare time

(long post is long)
This one is for the .net folks. After evaluating the technology top to bottom and even reimplementing several examples I commonly use for smoke testing new technology, I'm just going to call it:

Blazor is the next Silverlight.

It's just beyond the pale in terms of being architecturally flawed, and yet they're rushing it out as hard as possible to coincide with the .Net 5 rebranding silo extravaganza. We are officially entering round 3 of "sacrifice .Net on the altar of enterprise comfort." Get excited.

Since we've arrived here, I can only assume the Asp.net Ajax fiasco is far enough in the past that a new generation of devs doesn't recall its inherent catastrophic weaknesses. The architecture was this:

1. Create a component as a "WebUserControl"
2. Any time a bound DOM operation occurs from user interaction, send a payload back to the server
3. The server runs the code to process the event; it spits back more HTML

Some client-side js then dutifully updates the UI by unceremoniously stuffing the markup into an element's innerHTML property like so much sausage.

If you understand that, you've adequately understood how Blazor works. There's some optimization like signalR WebSockets for update streaming (the first and only time most blazor devs will ever use WebSockets, I even see developers claiming that they're "using SignalR, Idserver4, gRPC, etc." because the template seeds it for them. The hubris.), but that's the gist. The astute viewer will have noticed a few things here, including the disconnect between repaints, inability to blend update operations and transitions, and the potential for absolutely obliterative, connection-volatile, abusive transactional logic flying back and forth to the server. It's the bring out your dead approach to seeing how much of your IT budget is dedicated to paying for bandwidth and CPU time.

Blazor goes a step further in the server-side render scenario and sends every DOM event it binds to the server for processing. These include millisecond-scale events like scroll, which, at least according to GitHub issues, devs are quickly realizing requires debouncing, though they aren't quite sure how to accomplish that. Since this immediately becomes an issue with tickets saying things like, "scroll event crater server, Ugg need help! You said Blazorclub good. Ugg believe, Ugg wants reparations!" the team chooses a great answer to many problems for the wrong reasons:

gRPC

For those who aren't familiar, gRPC has a substantial amount of compression primarily courtesy of a rather excellent binary format developed by Google. Who needs the Quickie Mart, or indeed a sound markup delivery and view strategy when you can compress the shit out of the payload and ignore the problem. (Shhh, I hear you back there, no spoilers. What will happen when even that compression ceases to cut it, indeed). One might look at all this inductive-reasoning-as-development and ask themselves, "butwai?!" The reason is that the server-side story is just a way to buy time to flesh out the even more fundamentally broken browser-side story. To explain that, we need a little perspective.

The relationship between Microsoft and it's enterprise customers is your typical mutually abusive co-dependent relationship. Microsoft goes through phases of tacit disinterest, where it virtually ignores them. And rightly so, the enterprise customers tend to be weaksauce, mono-platform, mono-language types who come to work, collect a paycheck, and go home. They want to suckle on the teat of the vendor that enables them to get a plug and play experience for delivering their internal systems.

And that's fine. But it's also dull; it's the spouse that lets themselves go, it's the girlfriend in the distracted boyfriend meme. Those aren't the people who keep your platform relevant and competitive. For Microsoft, that crowd has always been the exploratory end of the developer community: alt.net, and more recently, the dotnet core community (StackOverflow 2020's most loved platform, for the haters). Alt.net seeded every competitive advantage the dotnet ecosystem has, and dotnet core capitalized on. Like DI? You're welcome. Are you enjoying MVC? Your gratitude is understood. Cool serializers, gRPC/protobuff, 1st class APIs, metadata-driven clients, code generation, micro ORMs, etc., etc., et al. Dear enterpriseur, you are fucking welcome.

Anyways, b2blazor. So, the front end (Blazor WebAssembly) story begins with the average enterprise FOMO. When enterprises get FOMO, they start to Karen/Kevin super hard, slinging around money, privilege, premiere support tickets, etc. until Microsoft, the distracted boyfriend, eventually turns back and says, "sorry babe, wut was that?" You know, shit like managers unironically looking at cloud reps and demanding to know if "you can handle our load!" Meanwhile, any actual engineer hides under the table facepalming and trying not to die from embarrassment.

We need an open-source alternative to stack overflow. They have fucking monopolizing pieces of ratshit admins there and lame ass bots.

I HAD A FUCKING 450 REP :/ and now i have "reached my question limit"

I mean its okay of you want to keep stackoverflow clean , but straight out rejecting the new queries should be against your god damn principles, if those mofos have any!

If it is so easy to downvote and delete a question for the mods, why can't they create a trash site called dump.stackoverflow.com ? whenever a question is not following their stupid guidelines , downvote it to oblivion. After a certain limit, that question goes to dump space where it will be automatically removed after 30 days. Atleast give us 30 fucking days to gather attention of audience !

And how does a question defines someone's character that you downright ban the person from asking new questions? Is there a phd that we should be doing in our mother's womb to get qualified as legitimate question author?

"No questions are stupid" is what we usually hear in our school/college life. And that's a stretch, i agree. Some questions are definitely stupid. But "Your questions are so stupid we are removing you from the site" is the worst possible way to deal with a question asker.

Bloody assholes.

Now, can anyone tell me that if am passing a parcelable list of objects in an intent before starting a new activity, how can i retrieve it in the new activity without getting any kotlin warnings?
The compiler is saying that the data coming via intent is that of list<Type!> aka list of platform type, so how to deal with this warning?

"And in a stunning turn of events, he got it to work!"

But seriously... I've literally been throwing shit at a wall and seeing what would stick.
Fucking DTOs and getting shit out of a database. I need better resources on how to do this properly!

Anyways, I found that just using 'object' and letting the compiler deal with the rest of the bullshit actually allowed my code to work and run. I'm still a little in shock.

I'm over here trying to keep things in a nice one-to-one because that's what my PM recommended... and instead I just get slammed by Type casting nonsense and more errors than I can begin to understand. And unfortunately, Stackoverflow is of no help because everyone's issues are very nuanced and unrelated to my problem... Maybe I'm the problem? 🤷

But here it is working without all that bullshit. I don't know man... This code base is not the rager I was expecting. I'm getting my ass kicked with code that doesn't fall in line with the book I'm learning from.

You know how they say, "forget everything you've read and learned"? I'm feeling that really hard right now.

Constantly fighting the urge to rip everything down and do it based on what my book is recommending, but then the logical natured side of me is like "you ain't got that kind of time to be unfucking someone's work, only to get caught in more trouble. Your ego is not worth it"

Anyways, it's fucking late here and I'm glad enough to not have to think about this issue anymore. Bye.

> be me
> be developing a react native app
>realize the iPhone X notch is clipping your content on the first/home screen of the app
>google says: simple fix
>find a built-in react native thing to add safe area padding
> refresh the app
> ohno.png
> the other screens with navigation bars already have built in padding
> TOOMUCHPADDING.jpeg
> remove safe area thingy
> finds a clever, not particularly hacky way to pad the home screen without showing the header bar by setting its height to 0 and the color to match the content background
> more-problems.app
> there’s a small 1–pixel light colored line separating the header from the content clearly breaking the otherwise continuous single color background
> google.sh
> wtf.txt
> stackoverflow.html
> no responses except something I’d already done
> keep experimenting
> tries basically everything to figure out where that line is coming from
>sets borders to thicccc and bright red
>no bottom border? Ok that’s not it
>opacity?
>forgetaboutit.mov
>try shifting the header position around by a few pixels? Maybe it’s misaligned with the white parent layer underneath?
> nope.jpg
>it’s past bedtime
>Sleep.jpg
>thenextday(today).zip
> what about the content? Is that misaligned?
> nope2.jpg
>Maybe its an iOS feature not a react thing?
> make a test Xcode project, completely native to test
> negative.dng (pun intended)
> more-furious-googling.mp3
> find a native iOS stackOverflow question with the same issue (1px line)
> realize your Xcode test wasn’t done properly.
>atleastimmakingprogress.iso
> start looking into the SO post
>it’s native so I have to find out how to do it in react-native
>invent a bunch of style parameters that don’t exist in the documentation to see if there’s an undocumented thing
>loadsaloadsaerrors.log
>googles for a react native version of the iOS only SO post
> somethingpromising.tar.gz
> *tries it*
> “Haha nope” -my code
> whataboutthisotherthing.bin
> KENSISHSBUCNEGWISBVSIDNRVSIDNFIRJRBDKFNFIDJFIFKFNR
> HOLY FUCK
> IT WORKED
> AFTER TWO FUCKING DAYS OF SHITTERY AND SHENANIGANS
>AND MANY STACKOVERFLOW EDITS TO A NOW VERY MESSY POST
>THEREISNOMOREBORDER(final).zip
>*screams of relief*

--- Visits stackoverflow for an answer
. You find the accepted answer amazing... Yep this is what I'm looking for. (You copied the code into your source)
.
.
. scrolled down a little bit
.
.
. You saw another answer with a higher upvote. Ooh lala, this is fucking cool. (You copied and replace your source again)
.
. scrolled down once again
.
. You noticed yet another answer which is the most recent and a lot shorter implementation of what you just copied. (No shit! You copied and replace your source yet another time)
.
. scrolled down for the last time maybe and it looks like the previous was the last.
. But then...
.
. you saw a comment with lots of upvotes even more than the accepted answer and this comment points to a link.
.
. You clicked the link with your mouth salivating waiting to see what holds at the other side of the world which amount this so much upvotes.
.
. And Tadaaaa 404 not found!
.
. You feel hunted by that mysterious link for the rest your life...

I was flash developer once, it was great when macromedia was around, then adobe acquired them, now flash is gone.

Years are passing and most of industry is the same as always. Trying to drag you into this rat race of learning new amazing technologies, amazing projects that are actually doing same job as 50 years ago but using more memory and cpu cycles. Because all has it’s roots in algorithms from previous centuries.

So youngsters loose your best life time, be innovative by doing nothing more then copy paste from stackoverflow and duck typing shitty code.
Be a slave and sit in the amazing office, that has everything but not your real life that meanwhile is sucked by corporate squeezer till your last breath.
Be piece of shit that can be kicked around.

Watch youtube, facebook, instagram or whatever social network that shows you pictures that are fooling your mind that you’re someone special and you need this stuff.
Then be ready to suck some dicks to earn money and buy stuff you don’t need, live where you don’t want and do what you don’t like. You piece of shit.

Well that’s what disappoints me from my tech stack.

Now chill out, turn off your electronic gadgets, go out and enjoy real world.

I honestly don't understand people who genuinely believe formal schooling will cover all the basics they need to know to do a real-life job, and still get barely passing grades on all relevant subjects.

I genuinely don't understand people who copy GitHub projects to pass classes, and graduate from a university with goddamn StackOverflow instead of a brain.

Whom I understand even less are people who don't do anything major-related on their spare time.

I mean, change your fucking major, do what you actually like, do things that actually light your nuts with passion.

Please don't waste my time pretending you are in it not just because it's potentially well-paid and "cool".

Please don't waste my time being my coworker.

Yes, I'm looking at you, trendy wanker with a CS degree and no personal projects.

P.S. Junior here. Yes, I'm full of hatred for all the "real programmers" in the industry out there. I hoped for a better experience.

P.S.S. I mean absolutely no offense to people using either GitHub or StackOverflow outside of the aforementioned context.

When you decide it's not worth of your time to go through lengthy code documentation and just run that stackoverflow snippet straight on production.. 🤠

It's a real nice feeling when you figure out the answer to your own stackoverflow question as you're typing it out.
Not gonna make myself look like an idiot this time! No-sir-ee.

TL;DR: Stop. Hating. On. Ads. Here are 5 reasons why:

1. "No one likes ads"
I love seeing *good* ads before I watch a YouTube video. Or I looked up videos that YT recommended because they sounded fun and they were fun:
- Coke - Hey Brother is an amazing and touching short film
- Fressnapf (="food bowl") had an incredibly enjoyable "things you didn't know about cats" video I clicked on purpose and it was good.
- I found JetBrains through ads (free for me, student perks. But tbh I use atom)
and I could name more.

2. What are the alternatives?
I know there are some non-profits and that's cool but you wanna be paid in your job, right? So ads are why Facebook (I know, Facebook isn't enjoyed here but), YouTube, stackoverflow, etc. Wikipedia asks for a few million dollars of donations each year because they don't run ads. Smaller businesses can't do that really. Hell, even codepen has a "sponsored" section. Imagine you would have to pay for all of those services.

3. "Manipulation"
isn't a bad thing unless you abuse it. I manipulate you when I say that I love codepen in the same way an ad does. No one forces you to use a product or watch an ad (you can look away and often times skip).

4. Adblock
What if everyone did that? Adblock blocks happened a while ago and the war between adblock and ad-senders is still ongoing. The moment you see an ad, you are using/watching etc something which the creators thought is worth making money off. If you don't think so, leave the site. I am an adblock user but if the site politely asks me to disable it and I enjoy the content - I will disable it with pleasure.

5. Targeted ads
Yes. The internet is a huge data-crawling piece of shit. But there are many more questionable or even dangerous ways of data-harvesting online. I am glad to see ads I like and not the ones my sister might like. Some services allow you to disable personalized ads. Or use vpn if you really want to.

Done and redone but it's been a long time coming and it's my turn : fuck you StackOverflow.

I've been a member for a few years, and I hate the elitist idiotic community. Some people are there to help, most of them are just there to wank on their reputation.

Whenever you ask a question that is tiny bit specific, you are almost certain to have a vote to close it because "it's too vague" -even though I spent 30mn writing it with comprehensive examples, clean formatting and other users understood it perfectly as demonstrated by their comments trying to help- or any other reason that scream "I didn't understand the question or don't have the answer therefore it's a bad question"

If you are "lucky", a power user will just mark it as duplicate of another question that barely uses the same stack as yours and has one keyword in common because this illiterate fuck couldn't bother to read the full question detailing why it's not a duplicate but, oh surprise, the question they referred yours too already has an accepted answer by themselves. Abusing their reputation-bestowed powers to reference themselves for some more reputation.

Now that I am over 1k in reputation and have all 3 colours of badges, it seems like it warrants a bit more attention from the swarm and it doesn't happen as often. Which is appalling in itself, basically if you don't have enough shinys, your are considered a worthless piece of crap barely tolerated to ask questions.

The fact that big reputation users have so much power and can absolutely not be held accountable for their abusive behaviour is a recipe for power abuse

Hey fastlane!

Great tool and all, but your documentation is at 🤡 levels, I need to read 20+ pages to get a full overview and understanding. So far I've had to read a dozen plus blogs and stackoverflow posts to find hidden flows (authentication first to do this, etc. etc. etc.)

Don't market your tool as "reducing complexity & saving time" and showing one-liners in the docs when in reality there are lots of hidden steps and NOT one-liners!!!!!!

This is why everyone complains it takes 1-2 days to just get a freaking pipeline working!!!!🤡

Aren't you, software engineer, ashamed of being employed by Apple? How can you work for a company that lives and shit on the heads of millions of fellow developers like a giant tech leech?
Assuming you can find a sounding excuse for yourself, pretending its market's fault and not your shitty greed that lets you work for a company with incredibly malicious product, sales, marketing and support policies, how can you not feel your coders-pride being melted under BILLIONS of complains for whatever shitty product you have delivered for them?
Be it a web service that runs on 1980 servers with still the same stack (cough cough itunesconnect, membercenter, bug tracker, etc etc etc etc) incompatible with vast majority of modern browsers around (google at least sticks a "beta" close to it for a few years, it could work for a few decades for you);
be it your historical incapacity to build web UI;
be it the complete lack of any resemblance of valid documentation and lets not even mention manuals (oh you say that the "status" variable is "the status of the object"? no shit sherlock, thank you and no, a wwdc video is not a manual, i don't wanna hear 3 hours of bullshit to know that stupid workaround to a stupid uikit api you designed) for any API you have developed;
be it the predatory tactics on smaller companies (yeah its capitalism baby, whatever) and bending 90 degrees with giants like Amazon;
be it the closeness (christ, even your bugtracker is closed and we had to come up with openradar to share problems that you would anyway ignore for decades);
be it a desktop ui api that is so old and unmaintained and so shitty, but so shitty, that you made that cancer of electron a de facto standard for mainstream software on macos;
be it a IDE that i am disgusted to even name, xcrap, that has literally millions of complains for the same millions of issues you dont even care to answer to or even less try to justify;
be it that you dont disclose your long term plans and then pretend us to production-test and workaround-fix your shitty non-production ready useless new OS features;
be it that a nervous breakdown on a stupid little guy on the other side of the planet that happens to have paid to you dozens of thousands of euros (in mandatory licences and hardware) to actually let you take an indecent cut out of his revenues cos there is no other choice in a monopoly regime, matter zero to you;
Assuming all of these and much more:
How can you sleep at night with all the screams of the devs you are exploiting whispering in you mind? Are all the money your earn worth?

** As someone already told you elsewhere, HAVE SOME FUCKING PRIDE, shitty people AND WRITE THE FUCKING DOCS AND FIX THE FUCKING BUGS you lazy motherfuckers, your are paid more than 99.99% of people on earth, move your fucking greasy little fingers on that fucking keyboard. **

PT2: why the fuck did you remove the ESC key from your shitty keyboards you fuckshits? is it cos autocomplete is slower than me searching the correct name of a function on stackoverflow and hence ESC key is useless? at least your hardware colleagues had the decency of admitting their error and rolling back some of the uncountable "questionable "hardware design choices (cough cough ...magic mouse... cough golden charging cables not compatible with your own devices.. cough )?

Stackoverflow #1
Me posting question about how to prevent error.
User1: You answered your question. Its because of the error.
Me: I know. And want it gone.
User1: Proposes working yet somehow horrible workaround.
Me: Yes, that works, already did that. But i want to know why it happens.
User: Your question says you want a solution and it is one.
Me: One that doesn't solve the problem.
User2: Just give up. Don't try to find a better one.

Stackoverflow 2:
UserQ: Question how to...?
Me: Use this and that.
UserR: That is not an answer, so i downvoted and requested review.

I don't know a second community that is anti-encouraging like SO.

I HATE SPRING JPA HIBERNATE AND EVERYTHING RELATED TO FUCKING JAVA.

Everything behaves like it was created with a human as an afterthought, so it torments people and target audience are masochists. This whole ecosystem is an abomination of the software world.

Every fucking error has a thousand possible solutions for every single person AND NOT A SINGLE ONE WORKS!!!

The stupid thing will just keep throwing its internal problems in a stack DUMP DIARRHEA that you have to sort through to find anything remotely useful! I DON’T give a fuck about your stupid internal implementation, just tell me what the fuck you want!

And you have to play the guess game and find the right combination of their stupid little configurations to make it barely work. I couldn’t believe reading stackoverflow, people are just poking at it hoping it will work. And I’m literally stuck and can’t fix the damn thing no mater what I do, and I’m abandoning it.

I won’t touch this pice of shit with a twenty meter pole ever again! Last time I was this frustrated was the stupid java ee. Nothing in the software world has frustrated me this much. How does one even come up with this…
I’m done… I’m just done…

1) Learning little to nothing useful in formal post-secondary and wasting tons of time and money just to have pain and suffering.

"Let's talk about hardware disc sectors divisions in the database course, rather than most of you might find useful for industry."

"Lemme grade based on regurgitating my exact definitions of things, later I'll talk about historical failed network protocols, that have little to no relevance/importance because they fucking lost and we don't use them. Practical networking information? Nah."

"Back in the day we used to put a cup of water on top of our desktops, and if it started to shake a lot that's how you'd know your operating system was working real hard and 'thrashing' "

"Is like differentiation but is like cat looking at crystal ball"

"Not all husbands beat their wives, but statistically...." (this one was confusing and awkward to the point that the memory is mostly dropped)

Streams & lambdas in java, were a few slides in a powerpoint & not really tested. Turns out industry loves 'em.

2) Landed my first student job and get shoved on an old legacy project nobody wants to touch. Am isolated and not being taught or helped much, do poorly. Boss gets pissed at me and is unpleasant to work with and get help from. Gets to the point where I start to wonder if he starts to try and create a show of how much of a nuisance I am. He meddle with some logo I'm fixing, getting fussy about individual pixels and shades, and makes a big deal of knowing how to use GIMP and how he's sitting with me micromanaging. Monthly one on one's were uncomfortable and had him metaphorically jerking off about his lifestory career wise.

But I think I learned in code monkey industry, you gotta be capable of learning and making things happen with effectively no help at all. It's hard as fuck though.

3) Everytime I meet an asshole who knows more and accomplish than I do (that's a lot of people) with higher TC than me (also a lot of people). I despair as I realize I might sound like that without realizing it.

4) Everytime I encounter one of my glaring gaps in my knowledge and I'm ashamed of the fact I have plenty of them. Cargo cult programming.

5) I can't do leetcode hards. Sometimes I suck at white board questions I haven't seen anything like before and anything similar to them before.

6) I also suck at some of the trivia questions in interviews. (Gosh I think I'd look that up in a search engine)

7) Mentorship is nigh non-existent. Gosh I'd love to be taught stuff so I'd know how to make technical design/architecture decisions and knowing tradeoffs between tech stack. So I can go beyond being a codemonkey.

8) Gave up and took an ok job outside of America rather than continuing to grind then try to interview into a high tier American company. Doubtful I'd ever manage to break in now, and TC would be sweet but am unsure if the rest would work out.

9) Assholes and trolls on stackoverflow, it's quite hard to ask questions sometimes it feels and now get closed, marked as dupe, or downvoted without explanation.

If your problem has not yet been answered on StackOverflow, your probably doing something horribly wrong.
Consider a new approach.

God I fucking hate macs.
I got a mac at work. I tried to install ubuntu, with rather questionable results (unfortunately, I expected that) - so I tried to get mac work for me the way I like a system to work. I needed to download slack, simple enough, right? Ha, you wish. It's gotta be done through Apple store, so I went to create an Apple ID inside the Apple Store form. And, well, it just errored out on the submission. Great start. I went then to the settings and created an account there, great success, went back to Apple Store. Unfortunately being logged in at the system level doesn't mean you are logged in to the store. So, I went to log in to the store, simple enough, right? No, nothing's simple with Apple. After logging in I got a message that the Apple ID has not yet been used with Apple Store and that I need to review the account's setting. So, I click the "review" button and... I'm presented with a log in form. Yep, a perfect log in loop. I can't log in because I can't review the account but I can't review the account because I can't log in. Fun :)

You can't just go to the web admin panel for your account to review it for Apple Store, that would too be too easy. After a bit of searching I've found an answer on StackOverflow. You need to log in to iTunes. Through a fucking MUSIC APP. To install a free application from the store you need to log in to a music app. Yes, we're all mad here.

Then, after finding out that to be able to use side buttons on my mouse I need an app that I need to manually restart every time I restart the machine and that I need to have an app to fucking transfer files from an android I need another fucking app, because reading a storage of a linux-based system would be too standards compliant - something in me broke. I found out that installing windows on a mac is officially supported.

Supported doesn't mean that it's easy. I tried to install it trying different solutions from SO, but each time I would get an error that Windows couldn't modify the boot partition. Turns out that even wiping the drive and reinstalling OSX doesn't remove residual files on a boot partition and Windows installer is not allowed to modify them. It took me hunting into some shady looking site to actually find this answer. I have no fucking idea how long it all took me, but, finally, great success, Windows, WSL, side buttons working, I can even install slack from an installer. I just wish I could have those hours of my life back.

I was facing another if those problems (not bugs) that have the good solution barely outside if your reach.
I decided to pull my Ace in the sleeve and ask on stackoverflow. As I was half way through my well written question, where I had to illustrate stuff in great detail, and express clearly what is required, I realized how to solve it.

If I had written the question like many of the people who complain that SO is full of pricks who just downvote, nobody would have understood it, and I wouldn't have solved it myself. I would have been ignored and maybe even downvoted.

Write down your requirements explicitly, unambiguously, and you solve half of the problem by that. Do that on SO and you will never complain again.

Python async is a total, unapologetic shitshow. It’s as if the design goal was explicitly to invalidate the maximum number of thoughtful stackoverflow QAs possible. Pro tip: make you sure to memorize the release dates of every minor version of python from 3.5-3.10, so that you know which stackoverflow answers are not relevant in any way to your codebase.

Okay so for all of you who think that you can't do shit without stackoverflow. I'll tell you this, fuck SO. There's this ancient technique of programmers of old probably just about 20-25 years ago called RTFM. Why bother copy pasting some one else's spaghetti(that you might not fully understand) when you can write your own better code! (said in good faith). When something is behaving strange or you don't know what something requires just hit the docs or manual and read about the api because it is describes not only what it wants and needs but also what it does. So try this because it might have more information that you need than stack overflow might tell you

Programming has taught me
1. Importance of patience, friends and family and yeh StackOverflow too...
2. Importance of small contributions towards dev community.
3. How smaller things can make big changes.
4. Helping others and getting help if you get stuck.
5. Anyone can code, but very few can build robust solutions. Project not just coding but it needs preparation and planning too.
6. Importance of reading documentations, writing test cases, debugger programs.
7. You can learn things even if you have no idea about it. It just takes your interest.

Idk but i think i have the inability to ask a question on stackoverflow. Whenever i come across a specific problem my first instinct isn't to ask stack. It's to research, research and research. Then i go ahead to ask to those iknowsomuch pricks.
Do i enjoy it? No, i do it because i fucking need to.
So, stop shoving the fucking rules or policies or whatever the fuck it is on my face and answer the damn question if you know it. If not, fuck off. I hate it when they mark it as duplicate. Like are you actually serious. I've gone through the whole fucking internet including stack, searched the damn problem in different keywords, tried all the solutions for the related questions and problems and that's what you come up with. Label it as a duplicate or not descriptive enough. Oh just seriously fuck off with your "oh i have some admin capabilities let me use it on random shit". These are the people where they have no authority on anyone or led anyone or any team in their shitty lives yet act like a dickhead when someone in need of help comes to them. Oh you piece of shit, just fuck off. You miserable cunt.

I am a junior / new grad and I am working at my first job out of school. The software team is very small (around 5 people) and we maintain a very large project. Since the project is so large, each member of the team is responsible for a specific part of the project.

Other members on the team work on embedded and low level programming. I am responsible for only the web interface to the project.

I recently just figured a solution for a problem that I had been exclusively working on for almost 2 months.

I tried asking for help from other members of my team when I was working in this problem. However, most of them told me that they do not have the time to become familiar with the my codebase inorder to help.

As a junior, what am I supposed to do in this situation? I know I could’ve asked a question on stackoverflow but I thought that if members of my team helped me, it’d be a beneficial mentorship experience.

What are your thoughts?

I do not understand why you guys complains about Stackoverflow or even Arch linux forum. (There's a plenty of rant about those topic)

Those are just amazing, and of course, they will send you to the doc or downvote if you don't even do your job properly. I mean docs, google, other answer, wiki, tutorial, idk. There a plenty of resources where you actually can understand where's your problem. If after this you still don't have your answer, then ok ask it to the community because that why they exist.

But they aren't here just for repeating the answer that already exist and create double post, etc. Stackoverflow is one of the best source when you search on google because it's actually moderated nicely and guys won't hesitate to downvote you.

So if you got downvoted (Like I got sometime) then just think why was yours question/answer bad instead of just being angry against the community.

Ps: It's my first rant, but I was reading you guys since 1 year.

Use Maven, they said... it's better, they said... you don't have to manage dependencies yourself, they said...

...only now I've spent three days in hell trying to figure out why Maven keeps insisting on sticking INCOMPATIBLE JARs in my WAR that causes a breakage when deployed. No matter what I do it still sticks stuff in the WAR that shouldn't be there!

Like, I'm not a lazy cunt, I can manage my own dependencies! I know what's supposed to be there, oh, and by the way, everything fucking works when I build with Ant instead and I'm in full control of what winds up in the WAR.

So, basically, instead of the "hassle" of having to download JARs myself, I've now got the hassle of dealing with Maven trying to be more clever than me.

I know which I'd rather have, especially right now. ARGH!

You know, any time someone says "this is an industry-standard and that's why you should use it" my first thought is "hmm, which of these buildings is tallest and will ensure a quick death when I inevitably jump off of it?" MOST ESPECIALLY when the company just decides X is what everyone is going to switch to, regardless of what they're using now and regardless of how many YEARS it's been that way and working perfectly. Nope, doesn't matter, just get onboard the freight train, and if your productivity takes a hit, if you start missing deadlines dealing with shit you didn't have to deal with when using the "worse" tools, well, I guess that doesn't fucking matter, does it?!

And that's not even talking about the fact that the Maven build takes almost four minutes, which is just about 4x as long as the Ant build it replaced, each and every fucking time I make a change.

Look, I'm sure there are solutions and I'm sure I'll find them next week because I always do... and I'm sure there's some tweaking we can do to improve the performance... and it's not like this is my first go-round with Maven, though it's probably the most complex project I've ever tried to do with it... by my fucking dear god this is a nightmare, and it's not a nightmare of my choosing.

I'm disgusted, tired and defeated, three things I never get when it comes to technology. Congratulations Maven, you're on the verge of breaking someone who doesn't get broken. Another day like the last three and I'm not gonna need Stackoverflow, I'm gonna need a bus schedule so I can figure out exactly when to step off the fucking sidewalk!

Two sites I visit the most now are devRant and Dev.to.

Sites I don’t visit anymore because of obvious reasons:

1. StackOverflow (bunch of pompous retards who think they know the answers to life and 1 + 1 = 2.

2. Programming subreddit (pretty much boring now tbh)

What other places do you fine people visit when not angry with your bosses or the rest of the world that isn’t the devRant community?

Rant!!!
Recently, there has been this issue on StackOverflow not been friendly to beginners. I don't fully agree with that. SO is strict and rightly so because if not that, we will be flooded with repeated questions and low value answers. As a programmer, I believe when I go to SO, I want an answer quickly and fast because most at times, I'm programming and the problem I have is preventing me from moving forward. To be flooded by repeated and low quality questions and answers wouldn't help anyone. Also, on most beginner programming tutorials, were people are advised to check sites like SO when they have problems, most of them tell their listeners or readers to check if the question has been asked before, before going ahead to ask. Even SO assists you when typing your question with similar questions just to make sure you don't ask repeated questions. I rarely downvote but I understand those who do. Also, there is this talk about 'inclusivity' and some relating it to gender. It looks like people tend to slap gender and race on everything these days. To make this clear, I'm not a white male so that one wouldn't say the system favors me so I don't see the problem. The fact SO collects data about developers and it comes out that, most of the partakers are males doesn't mean SO is favoring males. SO doesn't show your gender when you ask a question. It doesn't even show your gender in your profile so what's the issue here? It will be better to get to the root of why there are few females in computer engineering and solve it there rather than blaming a site because of data collected. To know where this rant is coming from, just search StackOverflow on twitter and read the recent tweets.

stackoverflow should just be called pythonoverflow

because that's all it is, scrub / lazy wannabe "programmers" asking basic python questions they could find the answer to in 5 minutes on google if they made even the smallest amount of effort

sorry i'm not sorry, i asked my first stackoverflow question 3-5 years after I started my career. it's not a helpdesk the moment you encounter an error with your code or have a question about it

Remembering of when I first learnt about the importance of version control.

There I was, working in Visual Studio, laptop unplugged; the laptop suddenly shuts down - battery dead. Not too worried, might just have to rewrite a few lines I had not saved. Restart the machine, open VS, the file I was working on now contains strange characters - totally damaged.

Google for help, find a question on stackoverflow with the same issue (comforting moment). The answer I get:

"First question, why wasn't your code on source control?"

Haproxy.

Backlog.

30_000.

Nooooo.... Why on earth do you do that.

And yeah....

Looking at the sysctl settings someone took a road trip to Google and stackoverflow and just copy pasted every mother fucking stupid bullshit bingo inside it.

Half of this doesn't apply as the kernel version doesn't even support it anymore (for good reasons) or makes sense as these settings have NOTHING not even REMOTELY to do with the servers hw setup.

If you have no fucking clue what you do, ram the keyboard up your arse till you enjoy it.

But stay the fuck away from administration and the fuck away from anything that carries responsibilities.

Joyful task today: unclogging old failing Haproxy setups while being busy with 3 other tasks.

And if you wanna know why they're failing and it needed to happen today... Weeeell....

They restarted. And today they decided to restart so fast people finally noticed it.

Cause yeah. They did that the last fucking years every few hours. Now every 5 minutes.

:@ :@ :@ :@ :@ :@

Hire are a few tips to up productivity on development which has worked for me:

1) Use a system of at least 16gb ram when writing codes that requires compilation to run.

2) Test your code at most 3 times within an hour. This will combat the bad habit of practically checking changes on every new block you write.

3) Use internet modem in place of mobile hotspot and keep mobile data switched off. This will combat interruptions from your IM contacts and temptations to check your WA status update when working.

4) Implementation before optimisation... This is really important. It's tempting to rewrite a whole block even when other task are pending. If it works just leave it as is and move on to the next bull to kill, you can come back later to optimise.

5) Understand that no language is the best. Sometimes folks claim that PHP is faster than python. Okay I say but let's place a bet and I'll write a python code 10 times faster than your PHP on holiday. Focus more on your skill-set than the language else you'd find yourself switching frameworks more than necessary.

6) Check for existing code before writing an implementation from scratch... I bet you 50 bucks to your 10 someone already wrote that.

7) If it fails the first and then the second time... Don't try the third, check on StackOverflow for similar challenge.

8) When working with testers always ask for reproducible steps... Don't just start fixing bugs because sometimes their explanation looks like a bug when other times it's not and you can end up fixing what's never there.

9) If you're a tester always ask for explanations from the dev before calling a bug... It will save both your time and everybody's.

10) Don't be adamant to switching IDE... VSCode is much productive than Notepad++. Just give it a try an see for yourself.

My 10 cents.

rant on stackoverflow

For god's sake, newbies understand what we are saying. Don't just blindly write whatever the fuck comes to your mind.
Someone just wrote a website link in the answer and he is not even trying to understand that its an answer so include the solution not just the link.

IDIOTS!!!

For the little experience I had with developing a simple Android app (that may or may not see the light of day), I find that of you want to wing it on the go on your first app ever you're gonna have a bad time.

Any android-related doc will make you have even more questions. it's like they're teasing you with a piece of candy and then you have to bow to the gods of googling and stackoverflow.

I refer to the ArcGIS, facebook (sign-in and requests), and even the android developer page does not answer everything a beginner needs to know.

Is it just me because I'm a n00b? Or did anyone else have the same experience? Will I ever get to the day where I can code an Android app without struggle?

I think promoting 'a quick lookup on Google' every single time you need to add something useful into your codebase is a bad mentality. It's the same problem with populating your code with Stackoverflow snippets.

I think this is not a good approach because your code will eventually rot and you won't have full control over your codebase in that you didn't write those parts and you don't fully know what's going on underneath. Then, you will forget about that code. A new feature request will come up and oh no, you will be wrestling with your old code because you just quickly inserted it in there, not fully knowing it under the hood. Hours will be lost on debugging.

I advocate much more the approach of really knowing the language and the solutions you're using, instead of just constantly hacking it with the excuse of "Oh, there's no time to learn everything", "You don't need to know the details" and "This is the real world".

No, this is not a good attitude. With the former approach, you will be much more able to safeguard your code and improve on it, rather than wrestling for hours with it. I think it's important to have as much ownership of your code as possible and depend as little on outside libraries as possible.

Fundamentals first, practicality second.

Guys I need to deploy a very simple authentication API service.

You register with a username (actually an ID with a determined format), a password and uuid. You login with your username and password and if credentials are correct you get back the uuid as a response (JSON or whatever the fuck).

If you forget your password, you can use your uuid (which is confidential, very long string) in some POST request to set a new password. If you forget your username, you use the uuid again in a GET request to get back your username.

I've been looking at a bunch of solutions online and I don't think they suit my purpose exactly and all require emails (Like Firebase, AUth0, etc.) So, let me get this straight: NO FUCKING EMAILS INVOLVED PLEASE.

The above are the EXACT requirements I need for my work (for a good cause too). I fucking hate 0-requirement exploratory research tasks and I'm plagued with those. Those requirements are the only way it should work. So again, NO EMAILS INVOLVED PLEASE.

Also, please note that I have never developed an API in my life. I feel like StackOverflow will be assholes about this so I am asking this here.

I know it is very easy to do and there are probably dozens of ways to do this. I just do not know how, documentations are vague and overwhelming (or I'm just a little stupid lately). Another thing is that I am not sure of how can I do this in the most secure way. Bonus if this can be dockerized.

I know I sound a little rude,so I am sorry. It is just my frustration and depressing times I am going through that's preventing from thinking straight.

Any good algo book for a guy who's managed to read C Primer Plus and Learning Python? With math really explained. He's bad in math.