Details
Joined devRant on 4/15/2017
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
You know what? I'm fucking done with people telling me that open source alternatives to popular/proprietary suck by default.
Something does NOT suck by default just because it's FUCKING open source.
Have you got any fucking clue where we'd be right now if open source software didn't exist?!
Let me just remind you that about 80 percent of the worlds' servers run Linux. Open-FUCKING-source.
How the fuck are we supposed to innovate without open sourceness? Yes indeed, that would be about fucking impossible.
Although I've got to admit that some open source software programs don't work 100 well (in comparison to alternatives), what are you expecting? People put their free time into that shit and they've got to make money as well.
"well how are programmers supposed to feed their families if they only write open source software?"
Fuck right off. Of course we all need an income to survive. Hell, I need that as fucking well. But there's more to it than just work. Some people consider open source/working on open source software a hobby/passion. That doesn't even remotely mean thaty they don't work/don't need some kind of income.
If it wasn't for open source, we'd be nowhere (technologially seeing) right now.36 -
So I just finished an unpaid! Internship at a local tech company.
At the final meeting my boss said that he wants to keep me in the company. But my "skill level" is not high enough to pay me just now, and if I would stay as an unpaid intern for some months, we could talk about being paid.
After I refused, he was mad at me for "abandoning the team" and "hurting the company"
I hope other company's will be better. :/20 -
I don't understand why so many people fight this war of tabs vs spaces. My colleagues elegantly solved the problem just not using indentation at all36
-
Tip of the day:
If you want to keep your E-Mails private from Google, but need a Google Account:
1. Register an E-Mail at tuta.io
2. Use your newly created E-Mail by registering here: https://accounts.google.com/SignUpW...
Enjoy! -
Indie game devs: I have a couple of questions for you guys, sorry for my naivity and the subjectivity of some of the questions.
Is it as fun as it sounds?
Do you work as a team?
What tech/language do you use?
What platform/os do you produce games for?
Is your primary income from making games?
Im asking because I would like to get into it, but want to get a realistic view of what it's like.
Thanks guys. Please also take this chance to post your work.4 -
I delivered a small C# program long time ago.
Unit tests, integrations tests, functional tests, all passing (users even happy).
Colleague of mine approached me.
C: "I finally fixed the program"
M: "Which program?"
C: "Product X"
M: "What was wrong with it?"
C: "Nothing, but now it runs on Python"
M: "..."
C: "Yeah, we lost a few features, but it's Python!"
M: "Aren't you busy with other things?"
C: "That can wait"
M: "..."
M: "..."17 -
Me: *desperately trying to finish a webpage before 5pm deadline*
Girlfriend: Why are you always so focused on your computer? You never pay attention to me.
Me: You know I have to work. Besides, you'll always be number 1 in my heart
Girlfriend: Aww that was cute. Okay I'll let you finish working
Me to me: ...arrays start at 0. *continues typing*
Disclaimer: this was stolen from /r/programmerhumor and I have no girlfriend13 -
today at programming class...
professor: today we will be teaching you about vim and using the terminal and ssh. those who are smart enough to know these may leave the class, but be sure to sign the attendance sheet.
me: *starts packing and stands up and walks up to the front to sign*
me: *turns around*
EVERYBODY WAS LOOKING AT ME. i was the one only who stood up and the professor was also looking at me like "wtf this doesnt happen everyday". and so i walked out of there and im so proud of myself lmfao58 -
Github stats:
coworker 1: 3,535k ++ 987k --
coworker 2: 1,563k ++ 735k --
etc.
me: 453k ++ 7,848k --
I guess this confirms my job at the company as "Backend Crap Remover".7 -
So this fucking happened today.
Me: *sees support ticket coming in about some kind of login issue*
Me: *opens issue*
"Hello, I can't seem to login. There's an error"
Me: *sighs and thinks "at least give me that FUCKING error message then." *kindly replies with asking if they could send me the error message*
"Here it is. I don't understand what is going wrong
and what I have to do"
Me: *looks at error message*
"Invalid customer ID. Please make sure that your ID is correct. You can find it in the activation email we sent you when you registered".
😐 😶 😦
Me: *thinking okay what the fuck, are you fucking retarded or something?*
Me: *kindly replies: "It seems that you are not using the correct customer ID. You might want to look for it in the activation email we sent you!"*
"Oh okay thanks, how did you figure that out?"
Me: 😵 😐 😶 😭 🔫
Seriously what the actual fucking fuck.27 -
preface: I'm fucking exhausted and angry.
Why does everyone assume I know how to do frontend?
Why am I always the design girl?
Why?
You hire me to do backend. STOP GIVING ME FRONTEND DESIGN CRAP. I HATE IT.
AND STOP GODDAMN YELLING AT ME FOR NOT MAKING SOMETHING RESPONSIVE.
I DON'T KNOW HOW.
yes i can learn, but I CAN'T FUCKING PICK UP A SKILL LIKE THAT IN A DAY. Also, I fucking hate it.
STICK IT UP YOUR (min-width: 1400px) ASS.
But seriously, I've spent 13 hours today figuring out completely new things (webpack, susy, express.js, cloudinary, responsive best practices, more webpack) because the boss is in panic-mode (his preferred state) and wants this project released last monday.
guess what? it isn't done.
because i still don't know how to do everything. and ofc there's nobody to ask because there never fucking is.
Seriously, boss-man. hire a fucking designer, and stop being an illiterate sales goon while you're at it. ffs.53 -
Interviewer: Welcome, Mr X. Thanks for dropping by. We like to keep our interviews informal. And even though I have all the power here, and you are nothing but a cretin, let’s pretend we are going to have fun here.
Mr X: Sure, man, whatever.
I: Let’s start with the technical stuff, shall we? Do you know what a linked list is?
X: (Tells what it is).
I: Great. Can you tell me where linked lists are used?
X:: Sure. In interview questions.
I: What?
X: The only time linked lists come up is in interview questions.
I:: That’s not true. They have lots of real world applications. Like, like…. (fumbles)
X:: Like to implement memory allocation in operating systems. But you don’t sell operating systems, do you?
I:: Well… moving on. Do you know what the Big O notation is?
X: Sure. It’s another thing used only in interviews.
I: What?! Not true at all. What if you want to sort a billion records a minute, like Google has to?
X: But you are not Google, are you? You are hiring me to work with 5 year old PHP code, and most of the tasks will be hacking HTML/CSS. Why don’t you ask me something I will actually be doing?
I: (Getting a bit frustrated) Fine. How would you do FooBar in version X of PHP?
X: I would, er, Google that.
I: And how do you call library ABC in PHP?
X: Google?
I: (shocked) OMG. You mean you don’t remember all the 97 million PHP functions, and have to actually Google stuff? What if the Internet goes down?
X: Does it? We’re in the 1st world, aren’t we?
I: Tut, tut. Kids these days. Anyway,looking at your resume, we need at least 7 years of ReactJS. You don’t have that.
X: That’s great, because React came out last year.
I: Excuses, excuses. Let’s ask some lateral thinking questions. How would you go about finding how many piano tuners there are in San Francisco?
X: 37.
I: What?!
X: 37. I googled before coming here. Also Googled other puzzle questions. You can fit 7,895,345 balls in a Boeing 747. Manholes covers are round because that is the shape that won’t fall in. You ask the guard what the other guard would say. You then take the fox across the bridge first, and eat the chicken. As for how to move Mount Fuji, you tell it a sad story.
I: Ooooooooookkkkkaaaayyyyyyy. Right, tell me a bit about yourself.
X: Everything is there in the resume.
I: I mean other than that. What sort of a person are you? What are your hobbies?
X: Japanese culture.
I: Interesting. What specifically?
X: Hentai.
I: What’s hentai?
X: It’s an televised art form.
I: Ok. Now, can you give me an example of a time when you were really challenged?
X: Well, just the other day, a few pennies from my pocket fell behind the sofa. Took me an hour to take them out. Boy was it challenging.
I: I meant technical challenge.
X: I once spent 10 hours installing Windows 10 on a Mac.
I: Why did you do that?
X: I had nothing better to do.
I: Why did you decide to apply to us?
X: The voices in my head told me.
I: What?
X: You advertised a job, so I applied.
I: And why do you want to change your job?
X: Money, baby!
I: (shocked)
X: I mean, I am looking for more lateral changes in a fast moving cloud connected social media agile web 2.0 company.
I: Great. That’s the answer we were looking for. What do you feel about constant overtime?
X: I don’t know. What do you feel about overtime pay?
I: What is your biggest weakness?
X: Kryptonite. Also, ice cream.
I: What are your salary expectations?
X: A million dollars a year, three months paid vacation on the beach, stock options, the lot. Failing that, whatever you have.
I: Great. Any questions for me?
X: No.
I: No? You are supposed to ask me a question, to impress me with your knowledge. I’ll ask you one. Where do you see yourself in 5 years?
X: Doing your job, minus the stupid questions.
I: Get out. Don’t call us, we’ll call you.
All Credit to:
http://pythonforengineers.com/the-p...89 -
Have you ever wondered we programmers have so many strong communities.... Stackoverflow, devRant, Reditt, etc...
No other profession has such communities... Why? Why?
Because, we haven't built one for them.... 😂😁62 -
Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.54 -
!rant
After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:
1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.
2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)
3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.
4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.
5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.
6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.
7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.
8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.
9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)
10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...
These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!229










