Please consider my questions StackOverflow 😭

If Chuck Norris asks a duplicate question on StackOverflow, the original question is closed as a duplicate.

My mentor/guider at my last internship.

He was great at guiding, only 1-2 years older than me, brought criticism in a constructive way (only had a very tiny thing once in half a year though) and although they were forced to use windows in a few production environments, when it came to handling very sensitive data and they asked me for an opinion before him and I answered that closed source software wasn't a good idea and they'd all go against me, this guy quit his nice-guy mode and went straight to dead-serious backing me up.
I remember a specific occurrence:
Programmers in room (under him technically): so linuxxx, why not just use windows servers for this data storage?
Me: because it's closed source, you know why I'd say that that's bad for handling sensitive data
Programmers: oh come on not that again...
Me: no but really look at it from my si.....
Programmers: no stop it. You're only an intern, don't act like you know a lot about thi....
Mentor: no you shut the fuck up. We. Are. Not. Using. Proprietary. Bullshit. For. Storing. Sensitive. Data.
Linuxxx seems to know a lot more about security and privacy than you guys so you fucking listen to what he has to say.
Windows is out of the fucking question here, am I clear?

Yeah that felt awesome.

Also that time when a mysql db in prod went bad and they didn't really know what to do. Didn't have much experience but knew how to run a repair.
He called me in and asked me to have a look.
Me: *fixed it in a few minutes* so how many visitors does this thing get, few hundred a day?
Him: few million.
Me: 😵 I'm only an intern! Why did you let me access this?!
Him: because you're the one with the most Linux knowledge here and I trust you to fix it or give a shout when you simply can't.

Lastly he asked me to help out with iptables rules. I wasn't of much help but it was fun to sit there debugging iptables shit with two seniors 😊

He always gave good feedback, knew my qualities and put them to good use and kept my motivation high.

Awesome guy!

Once upon a time in Devland, there were two best friends @Alice and @Michelle and they worked together at The DevCo company as developers.
After a tough day handling an @-ANGRY-CLIENT-, they thought that they had to go and @RantSomewhere and so they went to a café. At the café, they ranted about some stupid clients, and @theItalianGuy at the third floor of their office building who never picked up calls, and @thatJavaGuy from the second floor who, they thought, was @notarealDev, and the usual stuff about their work. Somewhere in between, @Alice thought it would be @funvengeance to @hack @theNSA; “@karma is coming to get them”, said @Michelle.
To do this, they knew they’d have to take help from none other than @Gandalf who lived in a nearby @cave. So, the next day, taking a leave from work, @Alice and @Michelle embarked on journey to meet @Gandalf. After about an hour’s drive, they reached @Gandalf’s @cave. @Michelle went ahead to knock on @Gandalf’s rusty cave door. Being a lazy @necromancer, he magically opened his door 2 minutes later. “Who is't dares to disturb me in mine own catch but a wink?” shouted a voice from the back; “We’re two developers from DevCo and we need your help in our mission to @hack @theNSA”, shouted @Michelle. After a few seconds, he replied, ”Hmm… N'rmally I wouldst sendeth thee to mine own cousin @Hagrid, but in thy case, I sayeth thee shouldst visiteth the detective who is't goeth by the nameth @S-Holmes”. @Alice replied back, “Thank you, Sir @Gandalf, we’ll get help from this @S-Holmes, I’ve heard that he’s an @exceptionalGuy”; “Mine own pleasure, Farewell!” said @Gandalf, and the door closed shut.
So, @Alice and @Michelle went back to their car, and that time @Alice raised a question, “How are we gonna find this @S-Holmes? We don’t have a phone number or anything so we could contact this guy.”
“We should call @thatJavaGuy from work, I’ve heard he is a man of resources, he must know how to contact @S-Holmes”, said @Michelle.
And it was true, after a call with @thatJavaGuy, they were able to obtain @S-Holmes’s phone number.
“Howdy, this is @S-Holmes, what can I diddily ding dong do you for?”
“Hi, I’m @Alice, I’m from DevCo and I was hoping that I could get your help in our mission.”
“What kind of mission?”, asked @S-Holmes.
“We want to @hack @theNSA.”, replied @Alice.
“Okay… I think I might be able to hel-diddly-elp you! There’s an old and abandoned laberino noodly-near @stacked Street. It was made in @1989 and since then, it houses a magical computeroo that can hel-diddly-elp you in your mission. So, you just have to connect the computeroo to the Internet and you can diddily ding dong do your programmeroo thing and then you'll have access to the the noodly-nsa diddily ding dong database!”, answered @S-Holmes.
S-Holmes continued, “But I shall warn you, there's a riddly-rumorino that the laberino was abandoned because of an @electric-ghost that lurks there, but I bel-diddly-elieve it is just a computeroo program that was diddily ding dong designed to try to @stop hackers from accessing the top secret stuff!".
“Okay, thanks for your help! I bet we can handle whatever this @electric-ghost thing is, so… Goodbye!”, replied @Alice.
“Goodbye!”, said @S-Holmes and that ended their conversation.
Luckily, the @stacked Street was just a couple of miles away from them, so they reached the lab quickly.
As they got close to the lab they saw something that really surprised them…
--------
To be continued in part two...
(Do you want a part two? :/)

My first ever story is a little special because it is kind of dev related at it has "cameos" by various devranters, as you might have noticed.
How many did you count?
More in Part Two.

Thank you for reading and please, any feedback is welcome. Did you like it?
I haven't really revised it once, it is straight out of the keyboard.
Should I drop the "@" ?
But then it would impossible to spot some of the devRanters .
Let me know.

PS
What should be the title?
1)Alice in DevLand?
2)Adventures of Alice and Friends: Hacking the NSA?
You decide..(or maybe I'll pick the second one :D)

Probably the most awkward feeling call happened to me just recently.

I was to interview a guy that's like 10 years older from me with 10y more experience in mostly unrelated tech. I was prepared to have some respect for the guy, and was a bit anxious, but that changed quickly.

The first fucking thing he says, on the fucking job Interview is essentially "I've worked in tech for 20 or so years, and I don't appreciate being tested" great start .. needless to say, I tried to reformulate all my prepared Interview questions so they sound as casual as I could while still trying to get him to tell me *anything*. Most of the time I just felt like "why are we even here dude, you clearly don't care about any of this"...

About 12 or so questions later It was finally clear that none of his experience is useful, and even the exp he has sounds like past companies kept him around as a number...

I want to try a few more edge cases, hoping to find anything we could work with, when he calls me out on it and says "Well now you're testing me, I don't like being tested" at which point I pretty much gave up on the dude and let my HR colleague talk.

Then out of nowhere the guy brings up his mortgage, and how he needs money, and how no one wants to give him a job, and that if we don't want him, we should just tell him now.

Then he starts asking how many people we're interviewing, which is obviously stuff we can't answer, I just said "normal amount" to dodge the question at first, but that just made him more closed off and he just silently remarked "so you can be picky..."

That was one of the most painful interviews I had so far. Me and ny colleague pretty much instantly agreed that he's not a good culture fit for us. Probably not a fit for any company really, not with that attitude.

PS: it was a video call, though he had his camera turned off at first, so it was only me with a camera for half the call. He turned it on just about as I had enough of him.

So, I'm using a new MacBook Air (running Sierra), and while I'm still getting used to it (especially the different Sublime hotkeys), overall it really is quite wonderful. I particularly love the magic touchpad and ease of scrolling/swiping between desktops.

However, I ran into an issue this morning that gave me pause: apparent file caching.

My webpack setup auto-compiles my project when files change, and I noticed something was causing errors -- not really surprising since I was in the middle of fixing the project last night. However, the error it displayed wasn't something I was expecting, and referenced a line I was positive I had removed several hours before calling it a night. Whatever, I was probably mistaken, so I went to remove it.

... It wasn't there.

I double checked that I was looking at the right file. Yep, src/styles/header.scss -- that's the correct file. Figuring webpack was acting up, I killed and restarted it.

Same error.

So whatever, maybe Sublime cached it. Rather unexpected, but possible, and I am on a mac now... so maybe. So, I closed the file and reopened it. The line wasn't there. I did this twice more. It STILL wasn't there. Maybe I'm going crazy...? I checked the file with cat. The line was there. I checked with vim. The line was still there.

OKAY. I've seen a lot of people with beef with Sublime, and I often defended it. but maybe they're actually right. maybe Sublime really isn't the way to go. :( So, I killed and reopened Sublime, and I checked the file again.

The line STILL ISN'T THERE.

Maybe I'm going crazy? I double, triple, quadruple checked the path. all correct.
Alright; let's try again and make sure I do it properly. I closed everything I had open in sublime (two projects), and quit. I reopened Sublime, navigated to the correct path, and reopened the file...

The offending line STILL wasn't there.

I'm angry at this point and just mash the keyboard. I save the resulting garbage, and cat the file again. No visible changes.

KAJSFLK STUPID PIECE OF <redacted>

okay, whatever. Reboots fix everything, right? So I reboot, and keep the option to re-open everything again ticked.

The terminal comes back up, along with half(?) my browsers, but Sublime doesn't. grrrrrrr.

so I cat the damn thing.

GUESS WHAT.
THE GARBAGE IS THERE.

Sublime was doing its job. BUT EVERYTHING ELSE FAILED.

(Oh Sublime, why did I ever question you? 💚)

... but seriously, what the fuck could have caused that? Was the OS caching the file for some programs, but not others? Now I'm questioning the macbook...

Stackoverflow is an awesome way to find answers to programming problems. It can also be a toxic place in my opinion. I quit posting questions a few years ago. Whenever I posted a question after searching everywhere for hours and trying to be as constructive and everything as possible and making sure it wasn't a duplicate question, it would still be closed as non constructive or down voted or something else. This is why I also dislike stackoverflow next to it being really helpful very often.

I'm so scared of the people on stackoverflow that my method for debugging a problem is to write up a question by which time I'm shocked into finding a solution. I'm just too scared of being ridiculed by some narcissistic dev (who obviously never makes any mistakes, ever) or, heaven forbid, having my question down voted and closed.

Mom: My printer won't start. Can you FIX it?
Me: Mom, I am a coder, I don't know jack about hardware.

A week later....

Mom: My printer won't start. Can you FIX it?
Me: This question is marked as duplicate and closed as off-topic. 🤖

Hangs up.

You know what I always hated about Stack Overflow?

When a newbie asks a question and really wants to learn something they get downvoted for 'we're not your teacher. Go learn it somewhere else'

When someone else asks a question and just expects Stack Overflow to magically produce working code for him they also get downvoted for 'we're not a code generator'

When someone finally asks a 'good question' but mentions in the last line it's homework they also get downvoted for 'We won't do your homework'

They also don't tolerate fun or opinions.

I never actually participated in Stack Overflow because to me it felt that whatever I asked, it would get closed for god knows why. And when I actually answered questions, and wanted to help someone, I would get downvoted for 'don't make someone else homework' or 'don't waste your time if they're not willing to put effort in it'

I still always 'used' Stack Overflow but read-only thanks to Google.

Anyone else feels/felt the same way?

Another incident which made a Security Researcher cry
[ NOTE : Check profile to read older incidents ]
-----------------------------------------------------------
So this all started when I was at my home (bunked the office that day xD) and I got a call from a..... Let's call him Fella as I always do . So here we go . And yeah , our Fella is a SysAdmin .
-----------------------------------------------------------
Fella - Hey man sup!
Me - Good going mate , bunked the office , weather's nice , gonna spend time with my girl today . So what's goinon?
Fella - Bruh my network sharing folders ain't working no more .
Me - Did you changed or modified anything?
Fella - Nope
Me - Okay , gimme your login creds lemme check .
Fella - Check your inbox *texts me the credentials*

*I logged in and what I'm seeing is that server runs on Windows2008R2 , checked the event logs , everything's fine and all of a sudden what I found is fucking embarrassing , this wise man closed SMB service*
Me - Did you closed SMB service?
Fella - Yeah
Me - You know what it does?
Fella - Yeah it's a protocol , I turned it off to protect the server from Wannacry .
Me - Fuckerrrr!!!!! Asshole dumbass you fuckin piece of Dodo's shit!! SMB is the service responsible for files and network sharing!!!
Fella - But....I just wanted protection
Me - 😭😭😭

*A long conversation continues with a lot of specially made words to decrease the rate of frustration which I used already*

Fella - Okay I'm turning it on .
Me - Go on....... Asshole
Fella - It worked! Thanks a lot bro
Me - Just leave me and my soul away from evil and hang up .

*Now the question is , who the hell gives them the post of SysAdmin? While thinking this question , I almost thought of committing suicide​ but then my girl came with coffee and my rubber duck*

My little pleasure of today.

I asked a question on Stack Overflow.
It was closed with reason: "off-topic" "tip-of-the-iceberg" question.
I followed the link to the explanation of why it was closed.

There was a discussion in metaSO, about closing or not those kind of questions.
It seems somebody "won" the discussion arguing that was the right thing to do....

I DOWNVOTED HIM.

now I feel much better.

Spent a lot of time designing a proper HTTP (dare I even say RESTful) API for our - what is until now a closed system, using a little-known/badly-supported message-over-websocket protocol to do RPC-style communications - supposedly enterprise-grade product.

I make the API spec go through several rounds of review with the rest of the dev team and customers/partners alike. After a few iterations, everybody agrees that the spec will meet the necessary requirements.

I start implementing according to spec. Because this is the first time we're actually building proper HTTP handling into the product, but we of course have to make it work at least somewhat with the RPC-style codebase, it's mostly foundational work. But still, I manage to get some initial endpoints fully implemented and working as per the spec we agreed. The first PR is created, reviews are positive, the direction is clear and what's there already works.

At this point in time, I leave on my honeymoon for two weeks. Naturally, I assume that the remaining endpoints will be completed following the outlines/example of the endpoints which I built. When I come back, the team mentions that the implementation is completed and I believe all is well.

The feature is deployed selectively to some alpha customers to start validation testing before the big rollout. It's been like that for a good month, until a few days ago when I get a question related to a PoC integration which they can't seem to get to work.

I start investigating and notice that the API hasn't been implemented according to the previously agreed upon spec at all. Not only did the team manage to implement the missing functionality in strange and some even broken ways, they also managed to refactor my previously working endpoints into being non-compliant.

Now, I'm a flexible guy. It's not because something isn't done exactly as I've imagined it that it's automatically bad. However, I know from experience that designing a good/clear/future-proof API is a tricky exercise. I've put a lot of time and effort into deliberate design decisions that made up the spec that we all reviewed repeatedly and agreed upon. The current implementation might also be fine, but I now have to go over each endpoint again and reason about whether the implementation still fulfills the requirements (both soft and hard) that we set out to meet.

I'm met with resistance, pushback and disbelief from product management and dev co-workers alike when I raise the concern that the API might actually not be production-ready (while I'm frantically rewriting my integration tests and figuring out how the actual implementation works in comparison to what was spec'ed).

Oh, and did I mention that product management wants to release this by end-of-week?!

Every time I search something on Stack Overflow, I get excited when it's word for word the issue I'm having. Giddy with excitement, I click the question and scroll down.

Every damn time "Question was closed due to being off-topic".

Even when it's totally on topic!

Anyone get this or do I have the worst luck on the planet?

Stackoverflow status quo:

A question was upvoted 122 times --> Closed as too broad.

Stackoverflow...asking for a framework to do X.

Question gets closed by 20++ nitpickers because "... asking us to recommend or find a book, tool, software library, tutorial or other off-site resource are off-topic"

Scroll down 1 inch to find really useful answer.

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!

I was setting up a small home server running CentOS to my closet and was fighting with a USB Wifi adapter that wouldn't stay "awake". Googled the error messages and nothing...

Decided to about it on the CentOS forums and mentioned (MENTIONED, WASNT THE POINT) CWP (CentOS WebPanel) in my question, an admin came, COMMENTED A LINK TO A FORUM POST THAT TOLD "CWP IS NO WAY LINKED TO CENTOS" AND CLOSED THE QUESTION!
FUUUCKKKKK, i wanted to hit something sooo hard. The admin basically turned my point from A to X.

"This is ridiculous, why don't the docs explain this? This is absurd, it seems like thousands of people should be having this issue. Why do maintainers fucking not get it? Why write software if you don't intend for anyone else to use it?"

versus

"Hey, could you explain X to me? I'm having trouble understanding it."
"Sure, here: ..."
"Thanks - maybe we could add it to the docs, that's the first place I looked."
"Absolutely, good idea."
<closed in a8b7cb8d>

Which one was easier, folks? It's not this difficult. 100% going to help you if you ask - to me, at least, there's no such thing as a stupid question (seriously, I'll answer the most inane questions 100 times over if I need to). However, there's definitely a stupid comment, and unfortunately they seem to be the majority I receive on Github.

I made the mistake of stepping into the lift when I already saw our branch manager walking down the opposite hallway, joined by some guy in full suit and tie who's clearly just been interviewed. So of course they get into the lift as well and as the doors closed, manager asked me

"Well, is it worthwhile working here?"

Shit. Way to put me on the spot in front of an applicant. I just stuttered "Yeah... sure..?" and went silent for the rest of the ride. Like what the fuck kinda question is that, noone would work there if it wasn't. Why would you ask me of all people, their only working student at the time, doing different work on different projects for different pay than any actual employee?

Every fucking day I'm asked some fucking stupid question that could have been easily figured if this fucker took 2 mins to look.

"Hey why isn't the issue closed with your commit message? Is it because the CI fail?"

No you dipshit. It's because it hasn't been merged into the master branch. And no the CI didn't fail. If you took 20 seconds to actually look into the pull request you'll see it passed.

God why?

[DISCLAIMER : Potential Troll Topic here] I am self taught python and js (not considering myself as a real developer as I don't push much on github and work in a complete other field than anything related to CS right now) and would be interested to learn another language, with another paradigm. So, as I love you all, I would be interested In your highlights as I am currently considering either C, C++, Rust or Go.

with C, I know I could interface it with python. With C++ (despite Linus considering it evil) I know I could interface it with Node. I don't know currently what to do with Go, but some people seem really enthusiastic about it (not really relevant I know) and Rust seems like the C of today, with a bunch of new cool kid stuff. My main goal, after all, is to learn something new, to have another sight on programming. Either understanding more about hardware or learning another way of coding (like different from oop).

I know it sounds like a troll, but I promise it's not, just a serious genuine question (hopefully it won't be closed here like on SO)

So what do you think devranters ?

Being eternally grateful to all of you, I wish you a good night.

Here comes lots of random pieces of advice...

Ain't no shortcuts.

Be prepared, becoming a good programmer (there are lots of shitty programmers, not so many good ones) takes lots of pain, frustration, and failure. It's going to suck for awhile. There will be false starts. At some point you will question whether you are cut out for it or not. Embrace the struggle -- if you aren't failing, you aren't learning.

Remember that in 2021 being a programmer is just as much (maybe even moreso) about picking up new things on the fly as it is about your crystalized knowledge. I don't want someone who has all the core features of some language memorized, I want someone who can learn new things quickly. Everything is open book all the time. I have to look up pretty basic stuff all the time, it's just that it takes me like twelve seconds to look it up and digest it.

Build, build, build, build, build. At least while you are learning, you should always be working on a project. Don't worry about how big the project is, small is fine.

Remember that programming is a tool, not the end goal in and of itself. Nobody gives a shit how good a carpenter is at using some specialized saw, they care about what the carpenter can build with that specialized saw.

Plan your build. This is a VERY important part of the process that newer devs/programmers like to skip. You are always free to change the plan, but you should have a plan going on. Don't store your plan in your head. If you plan exists only in your head you are doing it wrong. Write that shit down! If you create a solid development process, the cognitive overhead for any project goes way down.

Don't fall into the trap of comparing yourself to others, especially to the experts you are learning from. They are good because they have done the thing that you are struggling with at least a thousand times.

Don't fall into the trap of comparing yourself today to yourself yesterday. This will make it seem like you haven't learned anything and aren't on the move. Compare yourself to yourself last week, last month, last year.

Have experienced programmers review your code. Don't be afraid to ask, most of us really really enjoy this (if it makes you feel any better about the "inconvenience", it will take a mid-level waaaaay less time to review your code that it took for you to write it, and a senior dev even less time than that). You will hate it, it will suck having someone seem like they are just ripping your code apart, but it will make you so much better so much faster than just relying on your own internal knowledge.

When you start to be able to put the pieces together, stay humble. I've seen countless devs with a year of experience start to get a big head and talk like they know shit. Don't keep your mouth closed, but as a newer dev if you are talking noise instead of asking questions there is no way I will think you are ready to have the Jr./Associate/Whatever removed from your title.

Don't ever. Ever. Ever. Criticize someone else's preferred tools. Tooling is so far down the list of what makes a good programmer. This is another thing newer devs have a tendency to do, thinking that their tool chain is the only way to do it. Definitely recommend to people alternatives to check out. A senior dev using Notepad++, a terminal window, and a compiler from 1977 is probably better than you are with the newest shiniest IDE.

Don't be a dick about terminology/vocabulary. Different words mean different things to different people in different organizations. If what you call GNU/Linux somebody else just calls Linux, let it go man! You understand what they mean, and if you don't it's your job to figure out what they mean, not tell them the right way to say it.

One analogy I like to make is that becoming a programmer is a lot like becoming a chef. You don't become a chef by following recipes (i.e. just following tutorials and walk-throughs). You become a chef by learning about different ingredients, learning about different cooking techniques, learning about different styles of cuisine, and (this is the important part), learning how to put together ingredients, techniques, and cuisines in ways that no one has ever showed you about before.

Hi everyone! (Specially pentesting masters!)
I got a question:
We all know the Nmap's abillity for detecting os using 1 open and 1 closed port,
Is there any way or method to detect os without any closed port ?(open ports exist)

Thanks alot 😃

Part 2 Of the StackOverFlow rant.

He still didn't accept my answer and commented something that even I don't know what the fuck he wants. Maybe you can fix your fucking grammar and it'd be easier to understand and solve your issue. 1 Hour later guess what he gets downvoted to -5, Gets his question Closed for Off-Topic and I end up being downvoted too. WTF. I answered his questions and instead, I'm getting downvoted because I answered on an "Off-Topic" Question. I seriously give up on Helping other people because no matter ho hard i try it ends up being a waste of time and you get nothing in return... Fuck the StackOverflow Community.

So the universe is determined to fuck with me for no other reason than the fact that I exist.

I managed to get 2 dates with 2 different girls (obviously) for next weekend.

And now, Australia is going into lockdown: No restaurants and shit.

So far, I am still laughing about the whole situation but now I am faced with either calling it off (which sucks because this lockdown can go for 6 months) or find another way to meet up.

I'm tagging this as a question to see if you guys have any ideas.

As for this fucked up universe... if the parallel MrCSharp is somehow watching me from the parallel universe that has a good 2020 going on at the moment, can you please like take me to your 2020.. that'd be fab.

Oh.. and my office is now fucking closed and forced to work from home. No more gym too..

god fucking damn it...

Is it just me or everytime I look up a question and I land on Microsoft Q&A site, theres never any accepted answers?

Rather you get, this thread is closed after all these non helpful answers from staff

Ok, all of us have seen the memes about how nasty Stack Overflow can be, this is why I usually try to find an existing SO post to read instead of making one. This time however, I found an error that I couldn't fix. A nasty C runtime error. I decided to ask a SO question for help, and awaited answers. I came back, and the question had been flagged to require more info, so I added more. I came back later, and someone told me I was doing it the hard way, and I should be using Visual Studio (I'm on Visual Studio Code), which ticks me off, because I don't want to use the hacky way around the problem, then this same person closed the question! They didn't even answer it, they just offered a simple workaround then closed without an answer. Man, SO sucks sometimes.

be me
> ask reasonable question on StackOverflow

“You fool. You think that you are funny to ask such a dumb, poorly worded question on a place such as this. You couldn't even be bothered to google it, as I found it promptly on gooooooooooo/goooooooooooooogle. So learn to google you lazy asswipe, we aren't here to do your job for you.”

[Question Closed]

> audibly sob for 1/2 an hour

I have a question bugging me for quite some time now.

How can you make a profit off of open source software?
I mean, if your company spends hundreds of hours developing a piece of software for commercial use, how can they argue releasing the code for free and risking piracy would be better than selling it 'closed'?
I'm genuinely interested in this.

BTW I'm referring to the open source purists who want everything to be open source. The occasional Byproduct of commercial software being released as open source is a different story.

Thank You StackOverflow.

After looking for 4 hours on internet and stackoverflow, searching whole documentation and blog pages, i didn't find a solution to an error I was getting in my Android app.
So I began and started writing the question on StackOverflow, phrasing it properly, to the point (so as to not get downvoted), providing all my files and code (so not to get closed or duplicate), formatting them properly, and explaining why my error was unique. On the last XML file I see something trying to call a function which wasn't declared.

So yeah, there you go.

But it's not over yet.
I saw it and got excited, corrected it and ran the code again. But accidentally ran it on the emulator and forgot my device wasn't connected anymore, and the emulator wasn't already loaded either. And my machine is old.

I don't know what to say anymore.

As a beginning designer I got a task: redesign of existing app... On the first call with developers I asked some questions for better understanding why the app looks the way it looks... How it works..... And I asked who is this app for...who will use it...who are the users..... And the devs were like.....3 minutes of silence..... And I was like...wtf? They don't even know who will use this stuff.... I immediately understood why the app looks the way it looks.. On almost every my question I obtained an answer like.... The database.... Some Backend programming stuff....and all the time I got some answer from devs like how should I code this or that... I changed every my question at least 5 Times, because I got all the time some absolutely strange answers - which had nothing to do with my questions... I felt like I run my head against a brick wall... Yeah.. Sometimes Its difficult to discuss problems with people, who are closed in their own World + when they show you zero understanding or zero effort to understand you...I felt like the collaboration with those people is some kind of punishment... 😂....but fortunately there are still a good people who shows some effort to understand you or to comunicate... Humanity is not lost. ☺️

To stay a dev (can do the role with my eyes closed) or take on the architecture role for this company that is sinking like the titanic.

Don’t bother with the hassle (don’t need more money tbh & don’t even know what the money is)?

Take the opportunity while it’s there and get it on my cv?

🤷‍♂️

#question

I used to love the hero treatment I got long ago in my previous company. Appreciations and what not for conducting events, contributing to open source. I think I burned out later. Later the hero treatment stopped there and I craved for it when I wasn't doing the stuff I used to do - basically I was previously keeping others happy I guess, instead of keeping myself happy. Contributing to open source or conducting events was not even part of the day job and was mostly considered outside the working hours and hence one had to stretch to do all that extra stuff. I over did stuff I guess and burned out

In my current company, I see heros and appreciations so much for contributing to open source though not all our roles are completely defined as open source roles and we instead have to work on closed source or yet to be open sourced stuff. My role is contributing a very tiiiiiny testing bit in an yet to be open sourced project, but a few other colleagues of mine work on closed source paid advanced version of the open source core project

Seeing all the hero treatment where I'm not the hero and seeing all the appreciation, I wonder how it doesn't seem right. Surely I'm jealous, lol. But I also felt the treatment also shows some sort of Special treatment for some people. It's "Special" and not exactly for all and only for open source contributors or people doing all the popularly so called as "cool" stuff. Fortunately for them their job role kinda mentions that I believe. And people working on closed source are now trying to contribute there. I'm stuck with some of my main day job work and dying in guilt for burning out, and not being able to contribute to open source and also kind of starting to hate open source for it's dark sides. Reminds me Batman dialogue "You either die a hero, or you live long enough to see yourself become the villain.". Open Source dark sides - of course the possibile dark sides of companies funding open source, the people behind the companies and also of course my company being one of them possibly, though if you ask anyone they say "Community comes first". That's full of lies is what I would say.

Inclusivity gets thrown out the window. Heroes get to talk. Heroes get worshipped. Others are not even noticed I think. I guess the only way to get noticed is to imitate the heroes

At some point I realized I'm envying or idolizing a crazy set of people, or like putting them on a pedestal. I'm trying to fix that in my head. But oh my, you should see all the treatment, the respect, etc. Surely some people just are there to do meh or grunt work or even good work or whatever without much appreciation, and then have to move on. No respect or consideration for opinions, thoughts usually. Some of them don't even have the time to care to check what people have to say. Top down hierarchy but they say it's flat hierarchy. They don't even wanna listen to some of us I think, that is during team meetings. Only very few care from what I have noticed

One good thing is I have to come to realize how much I'm like them in some behaviours and feeling damn guilty. I sometimes spend time thinking how to change myself for the long term. And how to avoid the toxic behaviors in the team and also control my anger and control my response to their behaviours. I'm also trying to understand where I'm climbing the ladder with my assumptions and also trying to see the "real" thing instead of assuming or being blind or imagining etc. But it has become so hard because idk if people are faking it, it's become very hard to always assume people are telling the truth 🙈 though it makes to assume or believe that by default. If people are okay with themselves lying, who am I question that huh

Please i have a question

I'm building an API with expressJs

Do i need to create a single database connection for all my query

Or should i rather open and close a connection for every query.

Which one is more efficient?

I'm currently using the first approach but the heroku clearDB addons is keep crashing Everytime saying connexion closed!

Please help
Thanks

Does anybody teach mobile development live? For example as code is being written they are providing audible commentary that is also captioned that is also downloadable after session is closed. A cool feature would be to have a q and a live and it picks up the commentary and/or question from the audience too, I think I just thought of another sound mobile app idea!

"asked 7 mins ago", "closed 4 mins ago" + "Update the question so it's on-topic for Stack Overflow." - edit, but hurry up before we close! This must be Stackoverflow's new welcoming culture then? (not my question, but somebody else's, closed for not being on topic, but could have happened to me as it did several times in the past)

Has anybody ever had a question closed on stack overflow? How long before a review usually happens?

Formatting code on stack overflow is a fuckin pain. One thing is off and the website is like WAIT WAIT WAIT WAIT. And then after all that time spending formatting it, to get your question closed for not being specific enough.