As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

Best office prank: I was pretty young and naaive. Senior dev comes to me and says that it would be hilarious to slide a note under the women's bathroom door saying, "I know what you're doing in there". He says that the woman in there will think it's hilarious too. We work with her, she's very funny and laid back, so I go along with it, expecting to get a laugh. A few minutes go by and a different older women enters my cube. She's got the note! She works on the other side of the building so I don't know her too well but I can tell from the look on her face that she's pissed. I'm frozen with fear as my career flashes before my eyes.
I apologise perfusely and try to explain but she's not having it. After a while she goes back to her office not having accepted that it wasn't meant for her and that it was just a joke gone wrong. I spend the next two days apologizing every chance I get, hoping she won't go to HR. She remains stone cold until late on the second day. She couldn't take it anymore as her mouth reluctantly begins to crack a smile. At that point she drops the serious expression on her face and busts out laughing.

It turns out that the three of them planned the whole thing and executed flawlessly. I've never felt so relieved to be the butt of a joke.

My "Coding Standards" for my dev team

1.) Every developer thinks or have thought their shit don't stink. If you think you have the best code, submit it to your peers for review. The results may surprise you.

2.) It doesn't matter if you've been working here for a day or ten years. Everyone's input is valuable. I don't care if you're the best damn programmer. If you ever pull rank or seniority on someone who is trying to help, even if it isn't necessarily valid or helpful, please have your resume ready to work elsewhere.

3.) Every language is great and every language sucks in their own ways. We don't have time for a measuring contest. The only time a language debate should arise is for the goal of finding the right one for the project at hand.

4.) Comment your code. We don't have time to investigate what the structure and purpose of your code is when we need to extend upon it.

5.) If you use someone else's work, give them the credit in your comments. Plagiarism will not be tolerated.

6.) If you use flash, you will be taken out back and shot. If you survive, you will be shot again.

7.) If you load jQuery for the sole purpose of writing a simple function, #6 applies.

8.) Unless it is an actual picture, there is little to no reason for not utilizing CSS. That's what it's there for.

9.) We don't support any version of Internet Explorer and Edge other than the latest versions, and only layout/alignment fixes will be bothered with.

10.) If you are struggling with a task, reach out. While you should be able to work independently, it doesn't make sense to waste your time and everyone else's to not seek assistance when needed.

11.) I'm serious about #6 and #7. Don't do it.

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.

Things I've learned throughout my 5 - 6 years as a programmer.
- StackOverflow is full of assholes.
- CMS's are for weaklings.
- The best feeling about waking up in the morning is figuring out how to solve that error in your code.
- You no longer think about normal people things. Your mind is full of code.
- You're practically a computer.
- ALWAYS backup and save your stuff or you WILL regret it. Enable autosave if possible.
- RIP your social life (if your friends don't know squat about programming)
- Darkness is better.
- Being a programmer is amazing.

Well, it happened. The stupidest request, no demand, I have ever, and most likely will ever receive...

Me: So what is it you're looking to do with your website.

Client: We're not showing up Facebook's home page. We need you to fix that. We have a budget of $10,000 to make this happen right now.

Me: As much as I'd love to take your money, that isn't something I can control. Every "home page" is profile-based, which technically isn't a homepage, but a "feed" that changes constantly. So say you create a profile on Facebook, only those you follow, and paid posts show up on your feed. What I can do however is use your budget to create and promote posts from your company page to show on users' feeds. If you're serious about marketing, we can start slow at $250/week, then work our way up or down based on results until your budget is exhausted, then re-evaluate the budget at that time. I can tailor a retainer for you based on the number of ads per week that you'd like to make.

Client: No, this is not what we're asking for at all.

Me: Okay...what is it you're looking for exactly? Run through this in as much detail as possible so I can get on the same page.

Client: We want to be on the main home page of facebook.com. We want our logo on that page when people sign up to make an account, linking to our website.

Me: That's simply not possible. That's Facebook's own home page. Nobody has a right to edit that other than Facebook itself.

Client: Bullshit. There's a Facebook developers section with APIs to edit and view Facebook's entire website. We would do it ourselves, but we signed up and don't understand how to change it in Chrome. That's why we need you and [referring client] said you were the best guy for our needs.

Me: That API has no control over Facebook's corporate data, including their own home page. That API designed ONLY for sections in which you are authorized to access or modify, such as your personal profile or created page for your business.

Client: We know that it can be done. If you don't do it, we'll find someone else who can.

Me: Well good luck with that, because the only way it would be remotely possible to do that WILL involve prison time, since that would be illegal. The only legal way to do it would be to buy Facebook, and they'll laugh you out of the building with that offer. But I'm done with this conversation because I have work to complete from clients that aren't delusional. Have a nice day! [hang up]

----

What. The. Fuck.

This is more just a note for younger and less experienced devs out there...

I've been doing this for around 25 years professionally, and about 15 years more generally beyond that. I've seen a lot and done a lot, many things most developers never will: built my own OS (nothing especially amazing, but still), created my own language and compiler for it, created multiple web frameworks and UI toolkits from scratch before those things were common like they are today. I've had eleven technical books published, along with some articles. I've done interviews and speaking engagements at various user groups, meetups and conferences. I've taught classes on programming. On the job, I'm the guy that others often come to when they have a difficult problem they are having trouble solving because I seem to them to usually have the answer, or at least a gut feel that gets them on the right track. To be blunt, I've probably forgotten more about CS than a lot of devs will ever know and it's all just a natural consequence of doing this for so long.

I don't say any of this to try and impress anyone, I really don't... I say it only so that there's some weight behind what I say next:

Almost every day I feel like I'm not good enough. Sometimes, I face a challenge that feels like it might be the one that finally breaks me. I often feel like I don't have a clue what to do next. My head bangs against the wall as much as anyone and I do my fair share of yelling and screaming out of frustration. I beat myself up for every little mistake, and I make plenty.

Imposter syndrome is very real and it never truly goes away no matter what successes you've had and you have to fight the urge to feel shame when things aren't going well because you're not alone in those feelings and they can destroy even the best of us. I suppose the Torvald's and Carmack's of the world possibly don't experience it, but us mere mortals do and we probably always will - at least, I'm still waiting for it to go away!

Remember that what we do is intrinsically hard. What we do is something not everyone can do, contrary to all the "anyone can code" things people do. In some ways, it's unnatural even! Therefore, we shouldn't expect to not face tough days, and being human, the stress of those days gets to us all and causes us to doubt ourselves in a very insidious way.

But, it's okay. You're not alone. Hang in there and go easy on yourself! You'll only ever truly fail if you give up.

Me: *Applies for entry level full-stack job*

Recruiter: "Sorry, I can't hire you because you don't have the years of experience we're looking for. We can take you on as an intern! Unpaid of course, while we train you."🙂

Clueless Me: "Sure, why not."

*second day into the internship*

Boss: "I have this really big project, and I want you to be the lead. I'm going to be very vague about what I want, so you'll constantly have to make changes to user stories, wireframes, & database designs until I'm satisfied. Don't ask me any questions for clarity, because I'm busy 🙂"

Silly Me: "okay"

Boss: "Also, can you train all the other interns? You're so lucky! You'll get to pick the best to join your team" 🙂

Stupid Me: "okay"

Boss: *emails me a spreadsheet of 80 Front-End interns (freshmen and sophomores)*
"Did you start building the app yet?" 🙂

Me (Dummy): "You haven't approved the final wireframes ye-"

Boss: "And for the other interns' training, what did you have in mind?" 🙂

Me (Dumbass): "I made a training guide, they're already followi-"

Boss: "My project manager for this other project left, guess he couldn't handle the pressure of a real job... HAHAHAHA! You're gonna take the lead of that project, too!"
*Adds me to the slack group* 😁

Me (Imbecile): "Wha-"

Boss: "And we've been having trouble with keeping track of everyone's code. Is there something we can do instead of slacking code snippets back and forth?" 🤔😮

Me (Fucking Imbecile): "Wait, you guys are working on a project and you don't have any form of version control? Maybe we should take a few steps back and plan thi-"

Boss: "Are you gonna take initiative or not!?" 😡

Me (Enlightened): "I quit." 😑

Former Boss: "Too bad... I was going to offer you a paid role tomorrow morning. Oh well!" 😔

Nobody:

Senior frontend Dev at my company: "microservices best thing ever"

Also him: "Relational databases gonna die"

Also him (talking to the DB team): "You're gonna dissapear, Mongo is the future"

Me: "Eh... Dude, Mongo is still a database.."

Him: "Microservices"

Send help...

There is this salesman right across from me that always brags about how rich his parents are and how lucky us tech guys are for having such an easy job. He told me one day that he was going to quit and make his own software company currently having no developing experience at all because "I've seen some of these developers. If those guys can do it, it'll be a breeze." I convinced him that the best language to learn in order to make your own websites/apps is Linux command line. Hilariously enough, the other 2 devs heard me say that and when Glenn the sales douche followed up with them one of them told him "Yeah, If you think you're really going to be quick with it then Linux will be your best bet, but if you have trouble just learn C++ instead and you'll still be able to make websites." Best of luck on your new Venture, you spoiled jizz stain.

<rant>
*Rules For Work*

1. Never give me work in the morning. Always wait until 4:00 and then bring it to me. The challenge of a deadline is refreshing.

2. If it's really a rush job, run in and interrupt me every 10 minutes to inquire how it's going. That helps. Even better, hover behind me, and advise me at every keystroke.

3. Always leave without telling anyone where you're going. It gives me a chance to be creative when someone asks where you are.

4. If my arms are full of papers, boxes, books, or supplies, don't open the door for me. I need to learn how to function as a paraplegic and opening doors with no arms is good training in case I should ever be injured and lose all use of my limbs.

5. If you give me more than one job to do, don't tell me which is priority. I am psychic.

6. Do your best to keep me late. I adore this office and really have nowhere to go or anything to do. I have no life beyond work.

7. If a job I do pleases you, keep it a secret. If that gets out, it could mean a promotion.

8. If you don't like my work, tell everyone. I like my name to be popular in conversations. I was born to be whipped.

9. If you have special instructions for a job, don't write them down. In fact, save them until the job is almost done. No use confusing me with useful information.

10. Never introduce me to the people you're with. I have no right to know anything. In the corporate food chain, I am plankton. When you refer to them later, my shrewd deductions will identify them.

11. Be nice to me only when the job I'm doing for you could really change your life and send you straight to manager's hell.

12. Tell me all your little problems. No one else has any and it's nice to know someone is less fortunate. I especially like the story about having to pay so many taxes on the bonus check you received for being such a good manager.

13. Wait until my yearly review and THEN tell me what my goals SHOULD have been. Give me a mediocre performance rating with a cost of living increase. I'm not here for the money anyway.

</rant>

This was at my previous and last internship. At previous ones i never got serious tasks so i was pretty used to that but one day my guider (lead backend programmer) called me over to help him out with a server issue (in all seriousness he said that i was probably the best Linux guy at that company at that moment). So i fixed it quickly and just out of curiousity i asked what kinda server it was and how many visitors it got monthly!

"it's a prod server and about one million at least i think"

I was just standing there for a minute and then asked why the hell he let me, an intern, work on that to which he replied: because you know what the fuck you're doing. I think I succeeded in hiding the tears of happiness that came up at that moment :) i fucking miss that place.

Living my best life, not too far from my computer, in the shade, with coffee 😁✌️hope you're all having a great day

Everyone that finds out you're an app dev: "So I have this multimillion $$$ idea!"

Me: "I'll do it for $100."

Everyone: "$100!? I'm giving you the chance to be part of the next best thing!"

Me: "Well I guess the 'next best thing' isn't even worth $100."

I literally don't even like telling people what I do 😒

I'm a little late to this, but that Python master/slave issue.. what the fuck is up with that?!

You say that you're offended by words.
=> Fuck off. If you want to serve social justice, help people in third-world countries that need your help.
=> Also, you do realize that the use of master/slave is just as much applicable to technology as client/server or host/guest are, right? It's a relationship between fucking machines or code blocks, not humans.

You say "why the outrage over this?"
=> Fuck off. Your SJW bullshit has no place in technology. It's a fucking word in fucking code!!!

You say that you're improving the Python project with this.
=> Fuck off. It breaks existing documentation and needlessly abstracts terminology that is used pretty much everywhere. What do you prefer, conciseness and a language to be easy to understand or for it to become all cushioned to soothe your frail feelings?

You know, there's something else that I wanted to talk about that's related to this. I have Asperger Syndrome, which on paper is a disability. In practice it's difficulty to socialize while having an above average IQ. That "disability" is what drove me into technology. When I see job listings actively prefer people with disabilities for social justice, you know what? That offends ME. Because I wouldn't want to be chosen as the best applicant just because it ticks social justice boxes. I want to be chosen as the best applicant because I outcompeted every other applicant with actual skill and fitness to do my job.

Also, when a company sells you a defective unit, would you be happy? Of course not. So why are you happy when they employ a defective? I am someone that would - on paper - be impeded by natural selection, because I am "handicapped". But I'm all for it. Humanity is what it is today - shit - partly because defectives have become widely accepted into society. Call me a bigot, but I'd rather be called that than to not raise concerns about this trend.

On the subject of handicaps, that's a term that's used in games, what for aiding the player that can't win against the regular opponent (which is usually just a fucking bot, wtf yo). I am handicapped, therefore YOU shouldn't use the word in a sense where it's totally reasonable to use it!! Says no one ever, me neither. Grow a fucking pair and realize that code isn't written with the intent to offend anyone. So why are you?

I ranted about this guy before who thought he was a security expert while hardly knowing what the word is probably. Today I met him again at a party.

Holy fucking shit, this guy.

"we use the best servers of the netherlands"
"we use a separate server for each website and finetune them"
"we always put clusters under servers, that way we have a fallback mechanism"
"companies mostly use bv ssl certificates"
"you're on call for a week? I'm full-time on call. Why I'm drinking alcohol then? Because fuck the clients hahaha"

😥🔫

My job requires us to use Mac. I've spent the week figuring how to get stuff done on it.

My best description of trying to code on mac is that it's kinda like having to extract your mangled penis from a blender before you bleed to death... Except you can't look directly at it, you have to wear a VR headset that's linked to a camera in the corner of the room.

And you can't use your hands directly you have to use an incredibly stylish and ergonomic looking steering wheel to control a robotic arm. The robotic arm has its own artificial intelligence and it desperately wants to help.

Unfortunately it doesn't understand anything about what you're trying to do and it keeps leaping to incorrect conclusions about what you want from it.

Everyone tells you it'll get better, but you're still in intense pain and your penis is still stuck in the blender.

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.

Me (5 days ago): A major, life-threatening hurricane is coming. I need to prepare. I know you have a need to launch so I will do my best to finish your project.

Client: Ok, stay safe.

Client (today): I know you're not done. You're late actually. To provoke you into further action, we went ahead and announced the launch and people will begin using the website now.

Me (at the store buying food for the next two week): What in the actual ... Here is your code. Finish it yourself. May God have mercy on your cold, dark soul.

1. Humans perform best if they have ownership over a slice of responsibility. Find roles and positions within the company which give you energy. Being "just another intern/junior" is unacceptable, you must strive to be head of photography, chief of data security, master of updating packages, whatever makes you want to jump out of bed in the morning. Management has only one metric to perform on, only one right to exist: Coaching people to find their optimal role. Productivity and growth will inevitably emerge if you do what you love. — Boss at current company

2. Don't jump to the newest technology just because it's popular or shiny. Don't cling to old technology just because it's proven. — Team lead at the Arianespace contractor I worked for.

4. "Developing a product you wouldn't like to use as an end user, is unsustainable. You can try to convince yourself and others that cancer is great for weight loss, but you're still gonna die if you don't try to cure it. You can keep ignoring the disease here to fill your wallet for a while, but it's worse for your health than smoking a pack of cigs a day." — my team supervisor, heavy smoker, and possibly the only sane person at Microsoft.

5. Never trust documentation, never trust comments, never trust untested code, never trust tests, never trust commit messages, never trust bug reports, never trust numbered lists or graphs without clearly labeled axes. You never know what is missing from them, what was redacted away. — Coworker at current company.

I turned 40 yesterday. Here are some lessons I've learned, without fluff or BS.

1) Stop waiting for exceptional things to just happen. They rarely do, and they can't be counted on. Greatness is cultivated; it's a gradual process and it won't come without effort.

2) Jealousy is a monster that destroys everything in it's path. It's absolutely useless, except to remind us there's a better way. We can't always control how we feel, but we can choose how we react to those feelings.

When I was younger, jealousy in relationships always led to shit turning out worse than it probably would have otherwise. Even when it was justified, even when a relationship was over, jealousy led me to burn bridges that I wished I hadn't.

3) College isn't for everyone, but you'll rarely be put square in the middle of so much potential experience. You'll meet people you probably wouldn't have otherwise, and as you eventually pursue your major, you'll get to know people who share your passions and dreams. Despite all the bullshit ways in which college sucks, it's still a pretty unique path on the way to adulthood. But on that note...

4) Learn to manage your money. It's way too easy to get into unsustainable debt. It only gets worse, and it makes everything harder. We don't always see the consequence of credit cards and loans when we're young, because the future seems so distant and undecided. But that debt isn't going anywhere... Try not to borrow money that you can't imagine yourself paying back now.

5) Floss every day, not just a couple times per week when you remember, or when you've got something stuck in your teeth. It matters, even if you're in your 20s and you've never had a cavity.

6) You'll always hear about living in the moment, seizing the day... It's tough to actually do. But there's something to be said for looking inward, and trying to recognize when too much of our attention is focused elsewhere. Constantly serving the future won't always pay off, at least not in the ways we think it will when we're young.

This sentiment doesn't have much value when it's put in abstract, existential terms, like it usually is. The best you can do is try to be aware of your own willingness and ability to be open to experiences. Think about ways in which you might be rejecting the here and now, even if it's as seemingly-benign as not going out with some friends because you just saw them, or you already went to that place they're going to. We won't recognize the good old days for what they were until they're already gone. The trick is having as many good days as possible.

7) Don't start smoking; you'll never quit as soon as you'll think you can. If you do start, make yourself quit after a couple years, no matter what. Keep your vices in check; drugs and alcohol in moderation. Use condoms, use birth control.

8) Don't make love wait. Tell your friends and family you love them often, and show them when you can. You're going to lose people, so it's important. Statistically, some of you will die young, yourselves.

When it comes to relationships, don't settle if you can't tell yourself you're in love, and totally believe it. Don't let complacency and familiarity get in the way of pursuing love. Don't be afraid to end relationships because they're comfortable, or because you've already invested so much into them.

Being young is a gift, and it won't last forever. You need to use that gift to experience all the love that you can, at least as a means to finding the person you really want to grow old with, if that's what you want. Regardless, you don't want to miss out on loving someone, and being loved, because of fear. Don't be reckless; just be honest with yourself.

9) Take care of your body. Neglecting it makes everything tougher. That doesn't mean you have to work out every day and eat like a nutritionist, but if you're overweight or you have health issues, do what you can to fix it. Losing weight isn't easy, but it's not as hard as people make it out to be. And it's one of the most important things you can do to invest in a healthy adulthood.

Don't put off nagging health issues because you think you'll be fine, or you don't think you'll be able to afford it, or you're scared of the outcome. There will always be options, until there aren't. Most people never get to the no-options part. Or, they get there because all the other options expired.

10) Few things will haunt you like regret. Making the wrong choice, for example, usually won't hurt as much. I guess you can regret making the wrong choice, but my deepest regrets come from inaction, complacency and indifference.

So how can we avoid regret? I don't know, lol. I don't think it's as simple as just commiting to choices... Choosing to do nothing is still a choice, after all. I think it's more about listening to your gut, as cliche as that sounds.

To thine own self be true, I guess. It's worth a shot, even if you fail. Almost anything is better than regret.

I need to hide myself, my computer, programming skills and computer knowledge from people. Then only, I will be safe..

Friend: Heeey, you're good with computers right?

Me: No! 😑

Friend: Come-on bro. I know you are.

Me: What do you want?

Friend: I want you to check and book flights for me for country X.

Me: Are you ok? How does this have anything to do with someone being good with computers and stuff?

Friend: Haha, see? You're good with computers. *starts laughing. Anyway, since you're good, you can find the best prices. I know you know how to search sites and how to find things online.

Me: WTF?!?!!! All, you have to do is type in your search. If you don't like the results, you simply refine it.

Friend: See, all this tech stuff I'm not really good at it.

Me: But you're good at searching for other things online, right? Do the same for your flights.

*Picks my laptop and walks away.
How can a young man not be able to search for flights online but knows how to use several gadgets. Nonsense.

OH MY GOD, MY TEACHER DOES NOT TEACH MY FAVORITE LANGUAGE!

I've seen a lot of rants about teachers who use an outdated language, or don't accept the preferred framework or library of the ranter, or even force students to use a technology or even worse an OS they don't prefer.

Whats with that attitude?

I absolutely encourage young people to learn technology in their free time and it absolutely helps at building a career and become good at programming. I don't think being around 18 and never having worked in a real job is the time to select "the most superior language and technology".

Actually, that time is never.

Technology is evolving all the time and different tech evolves in different paths for different purposes. Get rid of the idea, that there is a "best" and get rid of the idea, that you will always be able to work with what you think is best.

If you're really really really awesome, you can chose to do what you like most. Not awesome as in "i learned programming in my free time, now i'm better than my programming-for-beginners-course teacher" but awesome as in "start my own company and can afford to only take the jobs i feel like doing", that awesome. Most likely, you're not (yet).

In the real world, you will very likely sometimes be required to work with technology you don't prefer. Maybe with something you think is really bad. Probably, it's not that bad. More likely, you read it on the internet from someone whose self-image is based on on loving TechA and hating TechB. A lot of much hated technology is at least okay for it's intended use. Maybe not the most pleasant time you will ever have, but no reason to jump out of the window. Hey, and if you get used to it, you may even start to like it. At least, learn to retain some dignity when confronted with things you don't like.

You can still think that one thing is better than another, but if you make a huge drama out of it, you just make it harder for yourself. The best programmer is the one who get's shit done, not the one with the saltiest tears.

Had a client on the phone with an extremely heavy Turkish (I think so, not entirely sure) accent who was hardly understandable but I kept polite and tried really hard to understand his questions.

Didn't go so well and he started to get annoyed and rude as well and asked me why I kept asking him to repeat his questions.

Told him that due to his heavy accent I had some trouble understanding him but that we'd take it slow and that I was trying my best.

He didn't take that well and called me a fucking racist (or, a 'cancer racist (dutch: 'kanker racist') but this sounds nicer).

C: (remember, heavy accent) "Ben jij kanker racist ofzo?" (are you cancer racist or something?)

Me: sorry, kan je dat herhalen? Ik verstond je niet helemaal goed door het accent, excuses! (Sorry, could you repeat that? I didn't quite get that due to the heavy accent, apologies!)

*BOOOOOOOM*

Client exploded in my ear xD.

Totally worth it! I'm all for helping and tried my best but if you're going to disrespect me, fuck off.

Things I wish I could tell my 18 year old self.

1) Accept you will make mistakes.
2) Truly learn the language you are using.
3) Write idiomatic code for the language you are using.
4) Be upfront about not knowing something.
5) Don't let not knowing something stop you from learning it.
6) None of us knew X until we learned it.
7) Understand your strengths and weaknesses as a developer, play to them.
8) Be willing to try new things.
9) X language isn't ALWAYS the best choice, X paradigm isn't ALWAYS the best choice. Choose wisely.
10) You won't know everything, but you might know more than others.
11) Your ideas and ego don't matter more than ensuring the product works.
12) "Perfection is the enemy of the good [enough]" - Voltaire
13) "Perfection is not achieved when there's nothing more to add, but when there's nothing more to remove." - Einstein.
14) Conflicts happen, deal with it.
15) Develop a toolset and really learn them.
16) Try new tools, they may prove better than what you were using.
17) Don't manage your own memory unless you absolutely have to, you are probably not smarter than the collective intelligence of the team that built the various garbage collection methods.
18) People can be dicks, especially online.
19) If you are new and people are being dicks to you, did you skip past the irc message about etiquette? If you did, you're the dick in this situation.
20) It can be tough, but it is fun, so have fun!

Friend: So you're like a Developer right? Specifically using JavaScript?

Me: I mean...kinda? Pretty Noobish still...

Friend: But you could like show a buddy of mine some basics right?

Me (thinking to myself...the best way to test your knowledge is to teach it...): well...sure...

Friend: Great here is their info!

*Drives an hour away*
*sits down with this friend of a friend*
*busts out laptop*

Friend of friend: So how long have you been a Java Developer?

Me: -_- oh fuck...

*head desk*

So apparently devRant is a problem in my life. As those of you who've read any of my stuff here know I work at Victoria's Secret. So two of my friends come in just before I was ending my shift to see what the plans were for tonight. The usual - hit the club, crash at one of our houses.

Thing is, I was scrolling through devRant when they walked up. (the below is paraphrased)

Friend1: Ugh, you're still on that thing?

Friend2: Is she really? <looks over my shoulder>

Me: <eyeroll>

Friend2: I don't get it. <pokes me in the left tit> You barely post on Instagram and you don't tweet anymore. And you haven't commented on any of my posts in like days. Wtf bitch?

Disclaimer: Yes, we are those girls who talk like that and go clubbing and dress up and makeup and all that shit. Don't judge me because I don't give a fuck. Anyway...

Friend1: Seriously.

Me: Really? We're doing this? Because I haven't posted on fucking Instagram? I talk to you every day. I see you every other day. I like coding. I like tech. This place is awesome and the people are cool. If I want to see your ass or your outfit, I can just look at you. I don't need to be on Instagram 24/7.

Friend2: Jeez bitch. Need a tampon

<we all laugh>

Me: This is my thing. It doesn't mean we aren't friend and we won't chill, but my future is in development and technology. So deal hoes.

Friend1: Ugh you're such a nerd.

Friend2: <laughing>

Me: And you're both like totally vapid sluts. But I love you.

Friend2: Jelly

Friend1: Totes jelly. Girl you need some vitamin D

Me: I'm sayin'. But that doesn't mean I won't spend my free time coding.

Friend2: Ugh alright we don't give a fuck. Code or whatever. Just be ready at 11.

We all flip each other the bird and they leave. I guess if that's the level of acceptance I can get from my wonderful, gorgeous, annoying, amazing, asshole best friends, I'll take it. I am not changing my path.

Attended one of the best meetups ever. To give you an idea how awesome it was..

Speaker took the first ~20 minutes introducing himself.
His intro card deck kept referring to himself in the third person (he is the only employee in consulting 'company'). Ex. "Mr. Smith began his humble career .."

The powerpoint presentation began with him clicking each page, not executing the slideshow (ex. pressing F5).
Finally someone asked "Can you make slide bigger?"

S:"You can't read that?..um..sure...I guess .."
Starts fumbling around the zoom ...
Dev: "No, can you start the slideshow?"
S: "I don't know what you mean...there...I zoomed it, is that better? Now I can't see my notes..just sec.."
<fumbles again with the zoom>
Dev: "No, not zoom, start the slide show, press F5"
S: "Oh...you want me to F5 it...OK..."
<he *clicks* the slide show button>

Finally getting into code, trying to get out of powerpoint ...
S: "How do I get out of this fullscreen?.."
Dev: "Hit escape"
S:"No..um.."
<keeps trying to click on 'something'>
S:"I see visual studio, but its not on the big screen... "
<keeps click on 'something', no one is sure whats going on>
Dev: "Hit Escape to stop the slideshow"
<finally hits escape, then able to put Visual Studio on the big screen>
S: "Ahh...there, I figured it out."

Speaker had no end of making wild/random statements like:
".Net Core is the future of Microsoft, if you're using .Net 4.5...forget it, its not even supported anymore."
"When I was at Microsoft Build, I asked them why not put all the required .Net assemblies in one directory. Looks like with .Net Core, they listened to me" (he was serious)
"I don't use SQL Server Mgmt Studio. Its free and it sucks. I use <insert a very expensive SSMS clone>, its great, you guys should check it out", then proceeds to struggle to open a query window to write some SQL.
"When you use .Net Core and EntityFramework, you have to write your own stored procedures. If a developer can't write stored procedures, he shouldn't be in this business."

I was on the edge of my seat, hungry for the next crazy bat-shit thing to come out of his mouth. He did not disappoint. BEST MEETUP EVER!

A real interaction I just had...

Team Member: "Can you handle this ticket for a bug fix?"

Me: "Whats the problem?"

TM: "We aren't exactly sure..."

Me: "Ok, so can you show it to me?"

TM: "We can't get it to happen again, and when it does the machine freezes and we can't debug it..."

Me: "So, if I find a fix then how do we test to make sure it worked?"

TM: "I'm not sure..."

Then today,

Product Manager: "How's that bug fix going?"

Me: "Well, let's see. The problem still hasn't been defined. I have never been able to recreate the issue. I have a hacky fix in a PR..."

PM: "Great, so we can deploy today?!?"

Me: "No, because we have no way to reproduce or test this issue at all..."

PM: "Do you think your fix will work?"

Me: "Honestly, no. If you're asking for my opinion then you can have it. IMO this is NOT a bug fix but a change to how the system operates altogether. This system was built by someone who didn't know what they are doing. We have done our best with it but it is a house of cards. And now the solution is to replace a card at the bottom layer. It is likely that no matter what fix we do (even when we can fucking test it) that it will topple the house of cards..."

PM: ~Looking at me in disbelief~

Me: "If you ask me for my honest professional opinion then you will get it. Keep that in the future if that honest response was outside what you expected."

PM: "I will do that, thanks for your assessment"

Where do we go from here? God only knows.

Praise Joe Pesci

No work is going to be tolerable if you don't enjoy it. If you got into programming or IT or any industry simply for the money you can earn doing it, you're in for a BAD TIME.

I love computers, linux, programming, configuration, automation, and problem solving. So I love what I do. I am currently three weeks into 13 weeks of parental leave, and I have been having dreams about work at night.

The best piece of advice I can offer to someone who has trouble getting motivated is: make sure to like it first.

fellow from the team was asked to do the estimate by manager - he said 2 weeks

then manager asked what if we add one more developer - he said, again 2 weeks and maybe add day or two

I was asked same question without knowing that they already asked fellow from the team same question - I said around two weeks, maybe day or two more! XD

as manager was confused and not satisfied with the estimates, goes to our team leader with the same questions - team leader said - 2 and half weeks and if you add one more dev to it, 3 weeks minimum

we didn't know that all of us were asked as manager did that behind our backs, in the end manager learned lesson in greed as we got to stick to team leaders estimate!

also that was very rude of underestimating someone's ability, same manager did had personal bias and frequently mocked us, for example when we said that that we will implement ML for cropping images at the right place (ie. crop part of the image where the face is) on the backend. Response was something like: 'You guys will do the ML? Are you shitting me? You're not /insert FANG company/!'

best team win ever!

second best team win ever is when whole team left the company in matter of weeks

For my passionate coders out here, I have some tips I learned over the years in a business/IT environment.

1) Don't let stupid management force you into making decisions that will provide a bad product. Tell them your opinion and why you should do it that way. Never just go with their decision.
2)F@#k hackathons, you're basicly coding software for free, that the company might use. Want to probe yourself? Join a community and participate in their challenges.
3)No matter how good you are, haters are common.
4)Learn to have a good communication, some keywords are important to express yourself to other developers or customers. Try crazy things, don't be shy.
5)Never stand still, go hear at other companies what they offer, compare and choose your best fit. This leads me into point...
6)if you've been working for over a year and feel that you have participated enough in the companies growth, ask a raise, don't be afraid...you're wanted on the market, so either they negotiate a new contract or you find another job.

I'm sharing these with you as I made many mistakes regarding these points, I have coded for free or invested so much time in a company just to prove myself. But at the end I realize that my portfolio is enough to prove that I'm capable of doing the job. They don't like me? Or ask me stupid questions that I can google in 5 minutes. I'll just decline the job and get something better. Companies end up giving me nothing in return compared to the work I have put into it. At the end after some struggles you'll find a good fit and that's so important for your programming career. Burnouts happen quite often if you're just a coding puppy.

If some of you still have additional tips be sure to post them under here

You just came in today, being new in your position. I've been with the company for around 5 years, and you're the new guy. Look, I absolutely respect your skills. You're not a newbie coming out of uni, ok? You're a skilled sysadmin. But you asking me "what is your college?" and after me telling you I majored in linguistics, your answer "huh, that's why" and explaining why I'm wrong in my programming practices (which are taken from the Apache foundation) is utterly bullshit. Fuck off!

1) The fact that you have a BS in CS doesn't mean you know the best. I've worked as a programmer for some time. You were never paid to write a line of code.

2) Even if you were absolutely, positively, non-questionably right, you have no right to be condescending.

So, can you just shove your degree far up your ass? Because my friend, you're uppity as fuck just because you spent 4 years in college learning theory that you never applied in real world. I spent years learning my programming skills alone, after 9 to 5 work, during the evenings and fucking weekends. I don't need to prove myself to you, you fuckity fuck, I have proven myself to our employer over the last five fucking years.

Fuuuuuuuck!

Someone on a C++ learning and help discord wanted to know why the following was causing issues.

char * get_some_data() {
char buffer[1000];
init_buffer(&buffer[0]);
return &buffer[0];
}

I told them they were returning a pointer to a stack allocated memory region. They were confused, didn't know what I was talking about.

I pointed them to two pretty decently written and succinct articles, the first about stack vs. heap, and the second describing the theory of ownership and lifetimes. I instructed to give them a read, and to try to understand them as best as possible, and to ping me with any questions. Then I promised to explain their exact issue.

Silence for maybe five minutes. They disregard the articles, post other code saying "maybe it's because of this...". I quickly pointed them back at their original code (the above) and said this is 100% an issue you're facing. "Have you read the articles?"

"Nope" they said, "I just skimmed through them, can you tell me what's wrong with my code?"

Someone else chimed in and said "you need to just use malloc()." In a C++ room, no less.

I said "@OtherGuy please don't blindly instruct people to allocate memory on the heap if they do not understand what the heap is. They need to understand the concepts and the problems before learning how C++ approaches the solution."

I was quickly PM'd by one of the server's mods and told that I was being unhelpful and that I needed to reconsider my tone.

Fuck this industry. I'm getting so sick of it.

The best thing about a BOOLEAN is even if you're wrong, you're only off by a bit.

The best part of being an university student?

- Microsoft Imagine
- Office 365 for free
- GitHub Student Developer Pack
- JetBrains Product Pack for Students
- Spotify for only €4.99/month (instead of €9.99)
- Discounts for tech products

And if you're lucky also Adobe CC and AutoCAD.

The worst part?

- The university

Don't care if you're the best fucking dev in the world.
If you don't respect time, I don't respect you.

Dear "managers,"

Stealing credit for something you have not done is real theft.

When I come up with an idea and a detailed outline of how to build and deliver it, you do not get to say "oh I also had this idea." You did not. How could you? It uses tech you don't even know exists.

When I then proceed to build the whole thing on my own without any of your inputs (then again, you have no idea of how it works, what would you bring to the table), you don't get to parade my project in front of the board not even mentioning my name.

You see, it's not the first time you pull that off, you have taken full credit for every thing.

it's not just my wee feelings getting hurt for lack of recognition: it has real world consequences.

You get the promotion, you get the salary raise and you now live in a flat with a balcony and a view, while my wife and I share a studio as my salary has not budged.

You're a cunting thief, I hope your mom dies.

Best,

X

Admit when you're wrong and be willing to accept your ideas aren't always the best.

I find coding is the best way to alleviate boredom on a plane.

Not because I enjoy coding that much, but because there are two types of people:
1) Those who know what programming is and who will ALWAYS ask about it interested. (Conversation starter)
2) Those who don't know what it is and just assume you're hacking the plane!

The story of Netscape and Internet Explorer really proves the irony of fate! And how life will come back to bite you.

Back in the 90's you had to pay for browsers like Netscape (it was called a navigator but same thing) but after Microsoft released IE for free with your windows copy in 2002 it crushed Netscape and nobody used it anymore (the graph below).

But! Netscape wouldn't give up and before the company died after it made legal accusations against Microsoft and Bill Gates and made them pay for that they did, but Netscape was too far gone and already were falling apart they decided to make a self detonation (I guess that's what they thought being in that tight corner) and they released the code as open source which would later get taken by Mozilla and be the code base for Firefox.

Now look at how much better Firefox is and how nobody uses the shitty IE!

Kind of reminds me of the scene from watchmen where Rorshack was in prison and said the best sentence in the movie "I'm not locked in here with you. You're locked in here WITH ME!"

When you introduce your girlfriend to your Best friend and after some time they start dating each other and you are unaware of the situation but after sometime you get to know about their relationship , now you're really pissed and want to take revenge, then you remember that the girl's parents are strict af and you know that they won't tolerate that their daughter is in relationship
so, you tell her parents about her and
they decide to send her to a different school located in another city
The End

tl;dr
When two pointers are pointing to a same memory location then if any one of them deallocates the memory, the other pointer becomes a dangling pointer
:v

So there's a recent rant, about making a website work for IE.

I get it, you don't want to make it work for IE because you don't use IE.

But get this: you're not doing the site FOR YOU. You're doing it for the intended user, which is a lot of users that use all kinds of shit. If you don't want to do that, get the fuck out of web development, or from development overall. It's not for you.

I remember when I started my career, I had to make a web app that was intended to be used by, say, 100 people. As a developer I had the best tools for that - cool new 19" monitors, good GPU able to spit out a humongous resolution, and I designed that portal to look great. You know what my superior did then? He took away my 19" monitor and gave me a 14" monitor instead, saying that I became a spoiled brat that totally ignored the customer. I was angry at that, but immediately realized that he was completely right.

It doesn't matter! that it works on your machine. Who the fuck cares about your machine?

Does the software work for the intended user? If not, then you're a shitty developer.

I.
FUCKING.
*HATE*.
THIS.
KIND.
OF.
PEOPLE!!

I KNOW that you don't understand what you're doing or saying, THAT'S WHY I JUST TOLD YOU A VERY SHORT, SIMPLE, AND CLEAR SENTENCE TO SAY WORD-FOR-WORD TO THE OTHER GUY WHO, IF HE'S AT LEAST HALF-COMPETENT SHOULD IMMEDIATELY UNDERSTAND AND RESPOND WITH *FOUR* *WORD* *ANSWER* and instead of that you blabber on for 5 minutes how you don't know what to say to him and how to explain what we need (FUCKIN ADMIN LOGIN YOU BOTH WINEFLY-BRAINED MORONS!), and he blabbers for 5 minutes back something something bullshit someone else and then REMOTES INTO THE COMPUTER, AND DOES A SYSTEM REINSTALL OR REMOVES DUDE'S USER ACCOUNT OR SOME SHIT LIKE THAT BECAUSE MY SKYPE CALL WITH THE DUDE DROPS AND NEXT TIME DUDE IS CALLING ME HE'S CONFUSED ABOUT SYSTEM SETUP SCREENS!!!!!!

WHAT!!!!
THE!!!!!
SHIIIIIITTT!!!!

told him sorry but call the fucker who fucked it up for you, i'm not wasting two hours of my time just because some school "IT admin" thinks the best solution for user not knowing his admin login is to remotely trigger a reinstall or someshit on the machine.

Rant Init...

That moment you write some magnificent code and everyone is sleeping so you can't share it with anyone but you feel like the room should turn into an exciting musical where you win an award. (Best code can ONLY be written between the hours of 12am and 6am)

The next day, you try to explain to your significant other (user) how amazing this new genius way of doing that "thing" was, in hopes of sharing your excitement but all you get is a "you're such a dork" instead.

You may even try to share it with a coworker or fellow programmer but somehow they just don't see how exciting it is for you.

Rant completed...

Clearly Emojicode is the best programming language. If you disagree, you're wrong.

The best is to not even start it.
It is harder to stop, once you're doing it.
Like drugs, don't do drugs, kids.

A: Can you tell me your opinion about this? Please, be honest.
Me: Ok, I think you could do it in a different way, but let's talk about what you did and see how to make it better...
A: I don't think so, I think this is the best way to do it.
Me: Oh, OK.
A: Why are you always complaining about my job?
Me: Well, you just asked me, and I work on this too, so I thought...
A: I don't think you're collaborative enough with me!
Me [walking away]: Oh, OK...

I feel guilty when I spend time after work writing code, because there's that voice in the back of my head saying I should switch to leisure activities. "You've worked enough, don't sit all day, it's unhealthy".

Then I go for a walk or start planning something to cook. And there's still this weird feeling of guilt for not being productive enough, telling me I should learn a new programming language. "Work on your skills, you need to learn stuff to stay relevant in your field"

BRAIN, BE FUCKING CONTENT WITH WHAT I'M DOING FOR ONCE!

And stop fucking bullshitting me.

You're not trying to make me take a walk, you're not having my best interests at heart by making me learn or work.

I'm fucking on to you, you treacherous shitlitter of neurons. You're betraying me, and it happens every single fucking time I let my guard down.

I alt-tab out of my IDE, and within seconds you're there, impeding my intellect, making me click bookmarks to check the feculent streams spraying from the fingers of "friends" on Facebook.

I take a poop, and you just let me slide into a slowwitted state where I pick up my phone and stare at some crapfilled mire of memes.

You're the retarded digital-era id, wearing the disguise of a renaissance smart-ass ego, and you're dumping the fucking guilt on ME?

FUCK YOU AND YOUR MEMES, I'M GONNA BAKE A STEAK WITH MUSHROOM SAUCE AND WATCH PROGRAMMING VIDEOS WHILE DANCING.

NAKED.

(and maybe browse devRant later. I still love you, devRant)

Fellow Dev: the clients are requesting a gallery on their website with functioning modals.

Me: okay cool

So for the record, I'm new to front-end and I've got quite a lot to learn in JavaScript.

*I googled as much as I could and I made a proper functioning gallery in 2 full days of coding*

Him: okay, so this is great but they aren't really digging it.

Me: *sigh* yes, so what do they want?

Him: have you seen how an image opens in Google images? Like you click on one, the image opens while the rest of the content shifts down?

Me: um... Yeah?

Him: yeah, so they want that.

Me: ... *Scoops the web trying to figure out how Google does it*. Dude, I can't find anything close to it and I've still got a lot to learn. Idk how to do it.

Him: well, you're being paid for that. So, you better do it.

Me: 1000Rs ( approx. 14.58$ ) isn't called "being paid". Gimme a break here.

Him: You're a novice rn.

Me: why don't you do it?

Him: I'm your boss.

*Sigh* (he indeed is my boss)

Him: deal with it.

Me: FU........C.....*suddenly I realized how it's done* OH OH OH OH I just got it, I just got it!

(I actually make something like that)

*Lol yay*

That's just my best story of a fight. Lol.

Udemy courses are targeted at ABSOLUTE beginners. It's excruciating to pull through and finish the course "just because". And some of these courses are jam-packed with 30-60 hours just for them to appear legit, but the reality is the value you get could be packed to 3-5 hours.

You're better off just searching for or watching for the things that you need on Google or YouTube.

You'll learn more when building the actual stuff. Yes, it's good to go for the documentation. Just scratch the "Getting Started" section and then start building what you want to build already. Don't read the entire documentation from cover to cover for the sake of reading it. You won't retain everything anyway. Use it as a reference. You'll gain wisdom through tons of real-world experience. You will pick things up along the way.

Don't watch those tutorials with non-native English speakers or those with a bad accent as well. Native speakers explain things really well and deliver the message with clarity because they do what they do best: It's their language.

Trust me, I got caught up in this inefficient style a handful of times. Don't waste your time.

Some time ago I quit my job at a big corporation. Getting treated like a resource, a production line robot, just isn't for me.

My current job is way better. Small company, lots of freedom, getting to work on multiple projects, the result counts. But, as a small company, we also collaborate with big corporations. So I joined a team at one.

Watching my coworkers there, I'm reminded of robots again. Lunch break? 15 minutes tops. Just shovel some edibles into your face hole and back to work. Five minutes break between meetings? Open laptop, work work work. The concept of "needing rest" seems entirely foreign to them.

Yesterday our product owner "relayed some criticism" from other team members to me. Apparently, me going to the toilet in breaks is "suddenly disappearing". Or me not replying within 15 minutes in the chat is outrageous. And then he tried to berate me how I'm "his developer" and his team's tasks have top priority. So, according to the PO the problem is me and I should "get used to their mode of operation".

How about "no". I quit a fucking job because that "mode" is simply inhuman. After that feedback, you bet I'm taking my legally protected 30 minutes lunch break and any other break I can. Because fuck yourself, you're not going to burn me out. The best part, that team has smokers who "suddenly disappear" twice as much as I do, but apparently that's somehow a-ok.

I had to remind him that his project is just one of several I'm working on, so no, not "his dev". While that wasn't exactly a powerful comeback, it did shut him up. Still going to talk to my boss on Monday, at least to ensure that the PO can't talk shit about me behind my back.

Once, at school, last year, we had to present a C# project that, upon clicking a button, took words from a .txt file and showed them in an alphabetical listBox...

Since the file they gave us was so long that we had to wait a minute or so to get the listBox full, I implemented a progressBar which popped up on the button, and upon clicking it, the progressBar advanced for every word it loaded, until, upon finishing, it would have disappear leaving again the button, and the listBox would have been loaded.

Apparently, this choice alone – even if it had next to nothing to do with the exercise – was enough to give me a solid 9 out of 10, because our professors never explained us about progressBars and I used that completely on my own... I tend to do things like this in class, where I explore what my tools could give me.

So long story short, I ended up having the best vote in class for that, and I was so happy and motivated :D

Moral of the story: if you can, always try to learn something new about your tools and your programming language, on your own, because apparently it gives you advantage towards others, at least in school. Or even if you're not in school, it could still be something cool to learn that might be helpful in the future, for your projects or your job's projects.
The more you know, the better!

This happened a while back but thought it would be an interesting story.

So there is this guy, I'll call him Jack. Jack was a weirdo. He just graduated high school but thought of himself as very hot in terms of dev skills. He boasted lots of good programs, that are the best in industry, except they don't work (like the best proven file compressor, that just can't decompress anything because of some "bugs"). He also entered language holy wars quite actively, saying that Delphi is the best platform ever.

Aaanyway, a couple of years pass. Jack is now a student. Jack tries to make some money, so he talks to some guy, that offers him a "job" at the tax office, where he has to modernize the data infrastructure of the tax authorities. If you think this sounds very wrong, then you're 100% correct. But it gets better. After 2 months of work, the guy manages to do that. It's a simple CRUD application after all.

So everything works, but the guy who gave him this job refused to pay. He stalled and then just stopped answering the phone. Jack is now furious. So what he does, is publish the databases online, so everyone could see the income of every citizen. Authorities are in panic. They send the police to his door. They seize his computer and lock him up for a few days.

To sum it all up: Jack took up a job, without any contract, without any NDA, which is completely illegal in of itself, but he did that with the tax authority. And delivered the product before getting paid. And when he understood that he was owned, he published all online. He got bit back. The guy who gave him this job had no consequences for illegally hiring someone and not paying for their work.

Lesson: Don't be Jack

Not just another Windows rant:

*Disclaimer* : I'm a full time Linux user for dev work having switched from Windows a couple of years ago. Only open Windows for Photoshop (or games) or when I fuck up my Linux install (Arch user) because I get too adventurous (don't we all)

I have hated Windows 10 from day 1 for being a rebel. Automatic updates and generally so many bugs (specially the 100% disk usage on boot for idk how long) really sucked.

It's got ads now and it's generally much slower than probably a Windows 8 install..

The pathetic memory management and the overall slower interface really ticks me off. I'm trying to work and get access to web services and all I get is hangups.

Chrome is my go-to browser for everything and the experience is sub par. We all know it gobbles up RAM but even more on Windows.

My Linux install on the same computer flies with a heavy project open in Android Studio, 25+ tabs in Chrome and a 1080p video playing in the background.

Up until the creators update, UI bugs were a common sight. Things would just stop working if you clicked them multiple times.

But you know what I'm tired of more?

The ignorant pricks who bash it for being Windows. This OS isn't bad. Sure it's not Linux or MacOS but it stands strong.

You are just bashing it because it's not developer friendly and it's not. It never advertises itself like that.

It's a full fledged OS for everyone. It's not dev friendly but you can make it as much as possible but you're lazy.

People do use Windows to code. If you don't know that, you're ignorant. They also make a living by using Windows all day. How bout tha?

But it tries to make you feel comfortable with the recent bash integration and the plethora of tools that Microsoft builds.

IIS may not be Apache or Nginx but it gets the job done.

Azure uses Windows and it's one of best web services out there. It's freaking amazing with dead simple docs to get up and running with a web app in 10 minutes.

I saw many rants against VS but you know it's one of the best IDEs out there and it runs the best on Windows (for me, at least).

I'm pissed at you - you blind hater you.

Research and appreciate the things good qualities in something instead of trying to be the cool but ignorant dev who codes with Linux/Mac but doesn't know shit about the advantages they offer.

For my very first job interview, I joined a rather well known company (somewhere in the mid-ranges) as an intern-frontend developer. Everything was going okay-ish. I was asked some technical questions and I answered them to the best of my knowledge, and it was all good until he came to the javascript questions.

Interviewer: So, have you worked with any frontend frameworks?

Me: Yeah, I usually work with vanilla JS, but I've gotten into frameworks like Backbone and Ember.

Interviewer: I've never heard of those. Do you know AngularJS?

Me: I've dabbled aroudn with it, although I haven't gotten into it much. If you want me to use AngularJS, I can pick it up and get the ropes of it pretty quick.

Interviewer: So tell me.. what is AngularJS?

Me: It's a Javascript framework released by Google (explains what it is and how it differs from most popular JS frameworks, explains the components of Angular.. etc)

Interviewer: Well, you're wrong. It's an enhanced html for web-apps. ( or some bullshit he quoted off the front-page of the then angularjs.org homepage )

When you're not funny nor miserable enough to post a good rant but you're still trying your best to get more ++ so you can get free stickers but the requirements keeps ++

I need to up my game :(

Have you ever felt that you're being overrated by your employer ?

For our front end projects we use Cloud9 IDE

Now the business have around 100k+ files.

So Cloud9 is becoming slower and slower with every new project created.

So I was tasked to build a code editor where a new instance of that code editor will be created per project ( so, the new editor doesn't need to handle a huge file tree), so I "git clone" ACE editor and add to it GoldenLayout.js , FancyTree.js and some other plugins.

Now they think I'm a genius, and I'm like ... Eh? Should I tell them.. ? Will it backfire later ?

I kinda like the feeling.

What's the best thing to do in this case?

Client:
"Ok,. so your saying that its gonna take you 63 hrs to create a simplified CRM with basic functionality and auto fill docs or automated work flow docs as an added feature?"

My response (after already under-quoting and planning on cutting some corners because he has a smaller budget than normally necessary):
"It sounds simpler than it is. There are a lot of things I need to take into account that you wouldn't even think about.

For instance:

Making sure your emails don't go to the client's spam folder. This requires the sending domain to be verified via DNS settings. I have to ensure your email content passes a spam test (link to text ratio needs to be good). I assumed you'd want an email that has your logo and looks good. This means testing the design in Outlook to make sure it's not broken.

What if the email doesn't send due to an invalid email address, or bounces back? You'll need to be notified.

What if the client list for the week contains duplicates? You need them merged or ignored.

Generating a PDF from HTML can be tricky because the conversion isn't apples to apples so there are things I need to adjust to make them as close as possible.

Making a site completely mobile friendly (the tier 3 option) can be very time consuming as well. It's not about whether or not it fits on a mobile phone, it's about whether or not it's intuitive and useful. You're essentially getting a mobile app without paying for separate development of an app.

If I took everything into consideration and built this to be 100% bullet proof, it would cost tens of thousands.

I'm doing my best to leverage your needs with the probability of running into an issue. I'm not going waste my time/your money on something that will likely never happen."

writing library code is hard.

there are sooo many details that go into writing good libraries:

designing intuitive and powerful apis
deciding good api option defaults, disallowing or warning for illegal operations

knowing when to throw, knowing when to warn/log
handling edge cases
having good code coverage with tests that doesn't suck shit, while ensuring thry don't take a hundred years to run

making the code easy to read, to maintain, robust
and also not vulnerable, which is probably the most overlooked quality.

"too many classes, too little classes"

the functions do too much it's hard to follow them
or the functions are so well abstracted, that every function has 1 line of code, resulting in code that is even harder to understand or debug (have fun drowning in those immense stack traces)

don't forget to be disciplined about the documentation.

most of these things are
deeply affected by the ecosystem, the tools of the language you're writing this in:

like 5 years ago I hated coding in nodejs, because I didn't know about linters, and now we have tools like eslint or babel, so it's more passable now

but now dealing with webpack/babel configs and plugins can literally obliterate your asshole.

some languages don't even have a stable line by line debugger (hard pass for me)

then there's also the several phases of the project:

you first conceive the idea, the api, and try to implement it, write some md's of usage examples.

as you do that, you iterate on the api, you notice that it could better, so you redesign it. once, twice, thrice.

so at that point you're spending days, weeks on this side project, and your boss is like "what the fuck are you doing right now?"

then, you reach fuckinnnnng 0.1.0, with a "frozen" api, put it on github with a shitton of badges like the badge whore you are.

then you drop it on forums, and slack communities and irc, and what do you get?

half of the community wants to ban you for doing self promotion

the other half thinks either
a) your library api is shitty
b) has no real need for it
c) "why reinvent the wheel bruh"

that's one scenario,

the other scenario is the project starts to get traction.

people start to star it and shit.
but now you have one peoblem you didn't have before: humans.

all sorts of shit:

people treating you like shit as if they were premium users.

people posting majestically written issues with titles like "people help, me no work, here" with bodies like "HAAAAAAAAAALP".

and if you have the blessing to work in the current js ecosystem, issues like "this doesn't work with esm, unpkg, cdnjs, babel, webpack, parcel, buble, A BROWSER".
with some occasional lunatic complaining about IE 4 having a very weird, obscure bug.

not the best prospect either.

for 2019 I want to be the very best dev
that no one ever was
to code them all will be my test
debugging is my cause
I will travel across the net
searching wide on tor
each singleton to understand
the power of the code

devmons its you and me
you know its our destiny
devmons
you're my best friend
and our firewall will stand
Devmons!

Karma...you're the best.

An ex-team member was complaining to me about his manager reviewing his code. Shortened version of the convo:
Mgr: "Why didn't you use the new C# built-in extension methods?"
Dev: "No reason. I thought using the straight forward approach would be easier to maintain"

Ha!..you conceded, arrogant mother <bleep>er. How many times did I have to listen you berate other developers in code reviews for not using some random C# syntax sugar? Comments like "If you bothered to read the new C# 7.0 language specification like I did...you would have known not to use the string.Format anymore..."

Now you're pissed that the manager embarrassed you? How does it feel d-bag?

That's too evil...so I simply responded "I don't think Nick meant anything negative about your code, he's just trying to help."

Seeing him stir around all pissed off does make me giggle like a little schoolgirl.

One of the biggest barriers to the wide(r) scale adoption of functional programming languages like Haskell, F#, and Scala is how snooty and condescending your average FP developer is. And beginner-unfriendly.

Ask them a question about an intermediate topic (in my case, the Free monad) you're likely to get a whole torrent of category theoretic rubbish in return.

This is a common pattern I see when "experts" answer questions.

Now, it didn't bother me much because I've studied a fair amount of category theory and can usually follow such answers, but, for the sake of the general case, I'd like to shove these rules into the heads of everyone writing an answer to a question (not just FP):

1. If you can't illustrate a concept clearly without going into verbal diarrhoea with phrases like "monad homomorphism" and "just a monoid in the category of endofunctors" then you clearly haven't understood it properly (unless, of course, the answer absolutely requires it). An answer is not the place to show off your knowledge of a topic.

2. Please remember that everyone was a beginner at some point. Including you. Understand that some concepts can be extremely frustrating at first and yet incredibly simple after you grok them (eg. monads).

3. If the person asking the question is a beginner, using complex concepts in an answer just because it's a more "elegant" way to explain it doesn't really help them. They are more likely to get confused and drop the topic.

(Kudos to those people who give highly relevant, insightful, simple, and intuitive answers, you guys are the best).

Recruiter: "Take this culture survey. It's not a test. There are no right or wrong answers."

Me, internal voice: Then why give me a list of words to choose from that I think describe me best and another list of words to choose from that describe how I ought to behave at work? Clearly, there's a matchup you're trying to do here. So clearly there's going to be a wrong answer if I don't choose enough of the former to match the latter.

One thing I learnt after over two years of working as a programmer is that sometimes making your code DRY is less important than making your code readable, ESPECIALLY if you're working on a shared codebase. All those abstractions and metaprogramming may look good in your eyes, but might cause your teammates their coding time because they need to parse your mini-framework. So code wisely and choose the best approach that works FOR YOUR TEAM.

I'm cracking up...

"chatGPT will ruin the software interviewing industry!!!"

uh.... what does it tell you about our industry if a fucking ROBOT can "ruin" the interview

well, you're right. it tells you that only algorithmic robots do well and subsequently earn the top spots at software companies after interviewing.

creativity, grit, perspective, wisdom? that stuff is absolute bullshit!!! (and as a feeble human I can't figure that out in an interview anyway!!! better just have you solve leetcode problems ad naseum!!! that'll get us the best employee!!!)

god i hate the dumb fuck rat race. good thing i'm not in it anymore! peace out, girl scout✌️

After months and months of slaving away, I quit my start-up job and feel completely amazing- here's what happened:

Met a classmate in grad school and he talked about starting his own company and he had full funding and etc. After graduation, moved to the new city where the job was located.

There were all these promises of us being co-workers and working on cool things and many other promises made. Soon after starting the job, most of these promises we're just smoke and mirrors.

Started working day in day out. Worked from 8am-9pm most days and worked on weekends too. Treated me like a I was a dog, talked down to me, gave unrealistic deadlines, pressured me with attitude and threats of losing my job. Hell, they thought they were the smartest person to touch the earth basically- example being that they mixed jQuery with VueJS in our Django template.....who the F*** does that. Another thing being that they had issues with me soft deleting records since they wanted them completely hard deleted and we had gotten into a giant argument about that fml.

What led to me leaving the job was that I had gotten sick one of the weeks, and I still showed up to work. Each day I was gradually getting sicker and sicker. Still tried my best to get work done. Saturday morning I get the most passive aggressive and bitchy text from my co-worker. "if you don't complete blah blah blah by Monday, we are going to have issues. Then on Monday you will work on blah blah blah". They blew the fuse with me. They would always punish me for being sick or taking a vacation. I'm not a dog, not a machine, I'm a f****** person. Went into his office when the work week started and gave my resignation on the spot and felt like it was the best decision I've ever made.

Now I just feel like a giant toxic cloud has disappeared from my life. I did walk away with so much experience and knowledge but now I just feel extremely burnt out from programming. Is this what I even wanna do anymore?

Few lessons I learned along the way:
1. If it sounds too good to be true, it probably is
2. Free lunches aren't worth it
3. Unlimited PTO doesn't really mean unlimited- there's always stipulations
4. Start-up life isnt as cool as they say- don't take TV portrayals as the real thing
5. Your mental health is extremely important
6. It's okay to admit to yourself that you're burnt out
7. Take a break
8. STARTUPS ARE NOT FOR EVERYONE

This is just my experience and what I learned, so telling my story. Phew, feels so good to get that off my chest

The "guy who is good with computers" can't open a fucking .rar or start skype. Yeah sure dude, you're like the best at "computer stuff". Fucking morons.

For some reason the office I work for is paying for a designer to become a front end developer and she gets to take the classes one work time. Any time I want to further my career or pay I have to pay out of pocket and it can't interfere with work. Additionally I have to deal with her asking me every other day why I use Sublime over something else.

Basically I use Sublime because I spent too much time researching new things to try and learn yet another editor. If you wanna use brackets, cool, if you wanna use atom, cool, if you wanna use notepad, cool. I don't give a flying fuck what editor you use, you're writing CSS, I'm writing PHP, if you can count to 4 spaces, and not look at my code, I'm not going to scream at you.

She comes in each day and sits at her desk watching video after video on beginner HTML and CSS asking me mundane questions breaking my concentration at least once an hour.

I know we all started somewhere but Google was my best friend and should be yours as well.

First rant: but I'm so triggered and everyone needs a break from all the EU and PC rants.

It's time to defend JavaScript. That's right, the best frikin language in the universe.

Features:
incredible async code (await/async)
universal support on almost everything connected to the internet
runs on almost all platforms including natively
dynamically interpreted but also internally compiled (like Perl)
gave birth to JSON (you're welcome ppl who remember that the X in AJAX stood for XML)

All these people ranting about JS don't understand that JS isn't frikin magic. It does what it needs to do well.

If you're using it for compute-heavy machine learning, or to maintain a 100k LOC project without Typescript, then why'd you shoot yourself in the foot?

As a proud JS developer I gotta scroll through all these posts gushing over the other languages. Why does nobody rant about using Python for bitcoin mining or Erlang to create a media player?

Cuz if you use the wrong tool for the right job, it's of course gonna blow up in your face.

For example, there was a post claiming JS developers were "scared" of multithreading and only stick in their comfort zone. Like WTF when NodeJS came out everything was multithreaded. It took some brave developers to step out of the comfort zone to embrace the event loop.

For a web app, things like PHP and Node should only be doing light transforms between the database information and HTML anyways. You get one thread to handle the server because you're keeping other threads open to interface with databases and the filesystem. The Nexus.js dev ranting on all us JS devs and doesn't realize that nobody's actual web server is CPU bound because of writing HTML bodies, thats why we only use 1 thread. We use other worker threads to do the heavy lifting (yes there is a C++ bridge look it up)

Anyways TL;DR plz respect JS developers we're people too. ES7 is magic and please don't shit on ES3 or we'll start shitting on the Python 2-3 conversion (need to maintain an outdated binary just cuz people leave out ()'s in their print statements)

Or at least agree that VB.NET is an abomination and insult to the beauty that is TI-84 BASIC

If you're planning to be a new entrepreneur (like me) here's a few things to keep in mind:

1) it'll keep getting harder but it's all worth it. Do not quit mid way no matter how hard it gets.

2) stop asking everyone for advice, they'll either be assholes or you'll end up getting confused by too much contradicting advice.

3) regardless of point 2, people will still advise you on everything (ikr). Listen to them, and if you don't agree with it... Do not bother to correct them, never helps... Just ignore it

4) if some one is an asshole to you or someone shoots your idea down, don't get discouraged. Reflect on it and if it's irrelevant, forget it all. Do not try to be an asshole back, always take the higher road.

P.S I'm also still learning... Hope you all very best for your endeavours :)

The best decision I ever made was moving from a big company to a very small one.

I used to work for a large international consulting firm in the model development team. Everything moved so slowly, there were huge amounts of pointless meetings and other time-sinks, we were surrounded by people who were being paid a lot of money but added little or no value, and the general atmosphere of the company was quite depressing. We spent more time having to make PowerPoint presentations for senior management trying to explain why you can't just hire 100 devs and have a product 100 times faster than we actually did developing a product.

I took a bit of a risk and moved to become the fourth person (and second developer) at a niche software producer to take over product innovation and lead product development. Immediately I felt so much happier and realised how much the previous company had worn me down. Everyone works hard and efficiently because your individual output is so much more important to the success of the company and the work you put in comes back to you financially without being syphoned by layers of valueless management levels or time-wasters.

Having responsibility, seeing the impact of your own work and being rewarded accordingly is so important for your sense of well-being. I urge you all to try it if you're stuck in a big company that's wearing you down. And if you're considering moving from a small company to a big one: don't.

I THANK YOU SO MUCH! SO VERY FUCKING MUCH! YOU'RE THE BEST!
THANK YOU!

So you're gonna underpay me when you know damn well I'm the best dev you've had in at least the last year? Guess who's gonna learn DVORAK on a QWERTY

not sure if counts as a compliment, but the follwing exchange with my team lead programmer felt pretty good:

"... wait, where did you find this function you're using here?"

"i didn't, it was missing so i wrote it."

"but... oh, i didn't realize you're gonna need it, if i had, i'd have given you a different task... noooo, that's internal framework functionality, i write that stuff for you guys so that you can just use it, cause it's complicated... oh, god, no, where did you put, how did you imple... (right clicks, go to definiton)... oh, it's exactly where it's supposed to be... (skims the code)... and is written exactly as if i had written it.
(looks at me and smiles, then turns to the rest of the team), guys, that component i told you to wait with making because i first need to write that complicated utility function that you'll need to use? you can start working on it now, Midnight wrote that function for me. (turns back to me) Nice, quick learner. But next time, at least let me know first, yeah?"

(that was third day in a new job, corporate-sized system. the rest of the team had been working there on that system for the past 2 years.

(probably not a good form, kinda going over team lead's head, but tbh i didn't realize i'm not supposed to touch that code because "it's complicated", while doing my task i just realized i need a function similar to a family of already implemented ones, so i just followed their convention amd added it.)

tl;dr - best programming compliment is people being surprised/confused that i did something which they thought as a normal thing that they will have to do for me, because it's in their job description to be doing it for people on my position/with my job description)

Here's a real tip for people new to the industry.

It's one of those things that's been said over and over again but very few can really seem to employ. I suggest you learn it /well/.

You are not your code. Criticisms of your code, ideas, or your thought processes, is not a criticism of YOU. You absolutely cannot take criticisms of your work personally.

We are engineers. We strive to seek the best solution at all times.

If someone has found a problem with your code or with an idea or whatnot, it is coming from a place of "this is not the best solution", NOT "you're an idiot".

It's coming from a place of "I'm closing this PR because it is not a change I feel suits this project", NOT "I'm closing this PR because it's coming from a woman".

It's coming from a place of "This feature request is ridiculous/this bug is not actually a bug", NOT "you're a fucking idiot, fuck you".

It's coming from a place of "I've already had to address this in a number of issues before and it's eaten up a considerable amount of my time already", NOT "I don't even know you and this I don't have time for a nobody".

You do not get to be bitchy to maintainers because they denied your request. It's not a reflection of you at all. But if you're arguing with someone who has maintained a piece of code for almost a decade, and they're telling you something authoritative, believe them. They're probably smarter than you on this subject. They've probably thought about it more. They've probably seen their code used in many different places. They have more experience than you with that codebase in almost all cases.

Believe me, if we cared about who was behind all of the issues, pull requests, etc. we get, we'd get NOTHING done. Stop taking shit personally. It's a skill, not a defense mechanism. Nobody has the time to sugar coat every little thing.

Let's normalize directness and stop wasting time during technical discussions into opportunities for ego-stroking and circle-jerking and back-patting.

Best thing to do when you're having a bad day:

> Post a video on YouTube telling people that you're developing a machine learning algorithm for drones to identify obstacles.
> Show them a basic HTML code on your computer screen.
> Disable the comments

One of our senior dev enjoys berating the other devs because they don't check-in code according to his schedule (once a day, once an hour..he flip-flops a lot), then when they do, he 'reviews' their code, beating them up because of incomplete features, commented out code..petty..petty nonsense.
Ex. (this occurred couple of weeks ago).

Ralph: "The button click code in this event isn't complete"
Dev: "No, its not, the code in my development branch. You said it was best practice to check in code daily whether the code worked or not. I didn't finish the event last night and ..."
Ralph: "Exactly. Before you check any code into source control, it has to work and be 100% complete. What if someone moved that code into production? What happens if that code got deployed? I'm not even going talk about the lack of unit tests."
Dev: "Uh..well..the code is on the development channel, and I branched the project in my folder ...I didn't think it mattered.."
Ralph: "Ha ha...you see what happens when you don't think...listen..."
- blah blah blah for 10 minutes of hyperbole nonsense of source control check-in 'best practice'

This morning Ralph's computer's hard-drive crashed.
Ralph: "F-k! ..F-k! ... my f-king computer hard drive crashed!"
Me: "Ouch...did you loose anything important?"
Ralph: "A f-king week of code changes."
Me: "You checked everything into source control on Friday ...didn't you?"
Ralph: "F-k no!...I got busy...and...f-k!"
Me: "Look at the bright side, you'll have a good story to tell about the importance of daily check-ins"

Oh...if looks could kill. Karma...you're the best.

Advice to new coders? I got multiple, unrelated to each other.

1. Start with the FUCKING BASICS !! Invest some time with fundamentals, don't just directly jump on frameworks like React or Angular.

2. You and everyone else are always going to blame your technical skills if you're unable to land a job. But you have to realize that is not always the case. Your attitude and energy towards the interviewer plays a vital role too.

3. You're gonna have to take a hit to your salary expectations starting out. It's just the way this industry works.

4. Think of yourselves as a freelancer working for companies. Those who call themselves Employees get stagnant and dependent on their company pretty fast.

5. Your objective is either to learn or earn. If there is both, amazing job. If there is either it's good enough. If there is none, time to jump ship !!

6. HR is there to protect the company from you not the other way around. Be better at spotting crocodile tears.

7. Try to find a WFH job over a WFO job. If you have an urgency, then either works but keep applying to WFH jobs. It's the best thing.

8. Focus on what you're building instead of what you're building it with. Devs have a tendency to fight over what tech stack they should use instead of focussing on the larger picture.

9. You're gonna get overwhelmed at some point when you're gonna get terms thrown at you like XML, JSON, API, Figma, Git, SOAP, REST. Don't worry though you'll get there.

10. You should know how to google your solutions, like really. This is like 60% of the job.

I understand now! I keep getting ++ on rants I wrote forever ago, and I finally understand the formula to become devrant famous:

1. Pick something that is mildly annoying and at least mildly tech related. For best reception, it should be something widespread, uncustomizable (and or difficult to customize so nobody does), and just mildly annoying so it's not too over played.

2. Post a long form rant, using almost the entire character limit to make this one, insignificant annoyance into a much bigger issue than it is. This is how the mainstream media does it, this is what the people want!!!!!

3. Somehow find a way to shift the blame onto one of the following groups: Microsoft, apple, arch, arch fanboys, arch haters, users, management, the fundamental laws of physics that allow computers to function, or in a worst case scenario start a flamewar (emacs sucks; arch is the best operating system; micro$hit; it's just Linux, if they wanted to call an OS GNU, they would finish fucking Hurd; etc. It's almost too easy)

4. Sit back and wait. You're now internet famous in a tiny portion of the internet. Congratulations. You've made it.

Not exactly a dev related rant.

Do you ever get the feeling when you're not working, like today, that you're kinda wasting time (can't find a better way to describe)? I usually work on Sunday at home, running behind insane deadlines, trying to anticipate tasks. Today was different, I woke up to a fresh VS 2017 install, updated my .net core api to 2.0, learnt how to deploy to Azure, made a CI/CD pipeline and then spend some fun time with my 5 month baby. Argued with him when Azure didn't let me make a new subscription. Sat on the sidewalk with him doing absolutely nothing for a solid half hour, only looking the way he admired everything around him and stuff. Took the trash out, did the dishes, helped with the laundry. But yet I feel like tomorrow gonna be a rough day, where everything will blow up 'cause I didn't did anything work related.

I'm starting to think I lost the taste of enjoying myself, enjoying the people around me, my family, parents, friends. I've been spending too much time on autopilot. Wake up, smoke, work, eat, work, smoke, sleep. Repeat.

I do enjoy my job, a little less when it's not dev related, but I do anyway. We are a small company with big contracts and tight deadlines. Always struggling to give our best and advance further, but I can see I'm loosing something while giving 120% of attention to my job.

Anyway, just wanted to get this thing out of my chest. Thank you if you read this far.

It's starting again. I can feel it.

You had a decent job, but you had to think otherwise. Then you had to go to that coffee shop tell some people you're the fucking bee's knees, didn't you?

Well, you know that's how the band plays.

Yeah, but now you'll have to live up to the hype, my friend. And you know pretty well that the pocketknife on your belt won't cut it anymore.

I can always learn as I go...

Sure you can. Except this time stakes are higher. They'll be expecting you to deliver on all your bloody greatness. They'll be relying on you. Not only them, but also the person who chose to be with you. And you know you're not enough, for neither of them. Now you'll fuck it up and let all those people down.

But I could build things little by little, lay out a solid groundwork and build up from that. Just like that other time when...

Of course you can. But can you make beautiful sparkly things? Can you make them sexy?

No... But I can make them resilient. I can follow best practices and intelligent design patterns.

Right. Cause design patterns win contests and prizes. Sure.

Well, it'll make things work better. And then when someone else comes along...

They'll say your work smells and let everybody know how it should've been done, because they need to prove themselves. You know that's what people do.

But that's just not fair! Solid work is solid work!

And a fraud is still a fraud. And that's what you are.

Warning: pretty sad thoughts. If you're having a blast of a day, please skip. It's for your own good.

That feeling when you finish watching a piece of art. Be it a film or anime or anything. You're confused why you feel good, but at the same time you're hurt. You smile but the pain is still there when you reflect on the feelings and the experiences you had and you realise that none of it will ever happen again. No art or any of the past will happen again exactly the same way how you felt and experienced.

You think of the best friend you once had. Think of the girl you held hands with and time stopped. The first time you embraced her and knew you loved her more than anything, even if she didn't know your feelings. Think of your first kiss. Your first serious relationship. The last time you saw your parents, your wife, your children, family.

Now look at the perspective of the future and the past you: blissfully ignoring the certain end to all experiences until they all abruptly end reminding you of this and it hurts. Damn it hurts.

I will never be able to see me best friend again, nor will I ever be able to hold hands with her either. First time I kissed is now long gone. It's almost like you wish you were aware of how valuable and important the experience was and to not just throw it away like the last time and the several times before that. But the sad part is, you don't know which experience will make you realise how much you missed it.

But even if you do realise by placing yourself in the place of your future self, and you cherish the experience, you blame yourself because you could have either avoided it's end or did something better.

Like your break up: could it be fixed? Was it worth the little time you have on this plante?
Like your friends argument you had: could you have done better? Could you have stopped it?
Like your parent's death: could you have been a better son to your now overworked dying mum? Could you see how hard they tried even though you thought they were total dicks?

Now you realise that literally anything you do, you will have a problem with somewhere down the line. You're destined to be sad shattered and broken by every day that is tragedy.

But it's similar to art. After all, your life is a piece of art about how you died. Which is why you smile and enjoy the last second of the experience which you just had. That chest warming feeling will only last a little. You smile through pain, yet you realise its not the end.

Then again, its just my thoughts that i need to vent. Take it with a pinch of salt.

The most important skill you can have is doing things without shame.

Shamelessly stay in your bed all weekends watching PewDiePie, never brushing your teeth, eating Doritos from under your pillow and peeing into empty Mountain Dew bottle if you feel like doing it.

Shamelessly spend your vacation sitting in the toilet with a laptop browsing reddit.

Shamelessly cut your product in half and ship it if you don't feel like perfecting it.

Shamelessly admit that you don't know something when you messed something up at work.

If you are a millennial like me, chances are your gen x parents told you that you have to be perfect / really good to succeed and to be worthy.

You know what? Fuck your parents then. Fuck my parents as well. Admitting this behavior wrong and actually giving up on living like something is always watching is the best thing you can do to your mental health.

I'm lazy. I write "any" here and there when they force me to do typescript at work. When I need a sidebar, I go and copy-paste that jquery snippet. I write like one article a month at best and I really want to say "fuck it" if I just don't feel like it.

You can always give up on everything and it's perfectly fine. This doesn't make you any kind of looser or something. You're perfectly fine.

Too bad I'm only beginning to master that.

A man's best friend is a Martini when you realize the college semester begins again at your birthday, and you're turning 29 that month with a year left before graduation. Fuck college. FML.

Yes, I'm writing this after having 3 martinis. My code can't pawsibbly go wrong tonight. Being a little tipsy is awwwwweeesome. :D

Lots of talk about sexual equality in the dev community. Personally I work in a small team, equal mix of male and female. I can honestly say there was no bias towards hiring as I was the one who hired them all, I employed the people I work with because they were the best candidates.
Questions to you all - have you experienced bias in hiring? Have you seen 'positive discrimination' (hired because someone was female - not because they were the best person).
In the U.K. the media is saying there's a huge shortage of females in the sciences, I like to think there's a positive push to get more women into science, but what's the reality? What's you're experiences?

I'm in the process of changing jobs and at the point where I need to sign the contract with the new company.

The concern I have is that of work life balance. There is a clause that obviously speaks to overtime and renumeration thereof, etc. But, there is also a clause that mentions that their office hours extend to Saturday mornings.

Speak to my wife about it and all I get is "That's how it is in your industry. I know of my other programmer friends who work late and long hours, so the fact that you don't currently work overtime seems very rare."

I don't think it's rare nor should it be the normal to have to constantly work extra hours. This is not a thing of being lazy or not dedicated to your job, but rather that you put in the time that is required and that alone should be enough to show your "dedication" to the job. Personally I feel that if you're fucking there everyday, giving your best, and you leave at the end of the day, no questions asked, that it is good enough!

1. Learn to read and understand the errors and exception messages. While writing code you're going to be facing exceptions most of the time and the real cause of them is under a lot of generic error messages. That and a lot of patience and perseverance.

2. You're going to face clients and bosses that ask you to do a temporary "workaround" even though you know there is a best way to solve a problem even if it takes more time and effort. Don't "crash" against their ideas, try to find a mid-term between the fast and easy work around and the best solution and leave it open to improve it in the future. I have met a lot of developers that let the frustration stops them to be creative just because the approved development is not what they wanted to do.

That moment when you're dual booting to have Windows for gaming and Windows decides it would be nice to reboot and install updates, while you're gaming of course. Without any sort of visible notification. Any. And then it fails to install its updates, because updates are hard to install, you know? Sometimes its just not the way you'd like it, you know? It's probably best to revert everything, yes? It only takes an hour after all! An hour of the lovely “Windows was too dumb to update and now has to try to make itself work again” screen with its lovely moving dots. Oh and of course you'll have to sit there and watch it because Windows has to reboot at least twice during the process. And if you're not there to tell GRUB you want to boot into Windows again Linux won't boot properly because Windows keeps the filesystems write-protected. Just to be safe you'd let it complete its marvellous ways!

I wish this was the first time this happened. But it wasn't. Fuck Windows.

I fucking hate people that talk bad about things they know nothing about.

The best thing that I have learned is to always keep my mind open.

From "Linux sucks because there is no software" to "MacBooks are just for rich morons" to "All Microsoft tech is shit" to "CS degrees are just a bunch of useless math" to "Bing sucks".

Fuck, what do you know?? You never spent 5 minutes to try them or get informed about them. You have your shitty ideas and will keep having them because you don't care about the truth... You only care about your comfort zone.

Yes, Bing sucks. I tried it. Google shows me better results.
iPhone might suck. I don't know. Never had the opportunity to try one for long enough.

Whenever you're throwing shit at something, stop and ask yourself: do I know the whole story?

After a few weeks of being insanely busy, I decided to log onto Steam and maybe relax with a few people and play some games. I enjoy playing a few sandbox games and do freelance development for those games (Anywhere from a simple script to a full on server setup) on the side. It just so happened that I had an 'urgent' request from one of my old staff member from an old community I use to own. This staff member decided to run his own community after I sold mine off since I didn't have the passion anymore to deal with the community on a daily basis.

O: Owner (Former staff member/friend)
D: Other Dev

O: Hey, I need urgent help man! Got a few things developed for my server, and now the server won't stay stable and crashes randomly. I really need help, my developer can't figure it out.
Me: Uhm, sure. Just remember, if it's small I'll do it for free since you're an old friend, but if it's a bigger issue or needs a full recode or whatever, you're gonna have to pay. Another option is, I tell you what's wrong and you can have your developer fix it.
O: Sounds good, I'll give you owner access to everything so you can check it out.
Me: Sounds good

*An hour passes by*

O: Sorry it took so long, had to deal with some crap. *Insert credentials, etc*
Me: Ok, give me a few minutes to do some basic tests. What was that new feature or whatever you added?
O: *Explains long feature, and where it's located*
Me: *Begins to review the files* *Internal rage wondering what fucking developer could code such trash* *Tests a few methods, and watches CPU/RAM and an internal graph for usage*
Me: Who coded this module?
O: My developer.
Me: *Calm tone, with a mix of some anger* So, you know what, I'm just gonna do some simple math for ya. You're running 33 ticks a second for the server, with an average of about 40ish players. 33x60 = 1980 cycles a minute, now lets times that by the 40 players on average, you have 79,200 cycles per minute or nearly 4.8 fucking cycles an hour (If you maxed the server at 64 players, it's going to run an amazing fucking 7.6 million cycles an hour, like holy fuck). You're also running a MySQLite query every cycle while transferring useless data to the server, you're clusterfucking the server and overloading it for no fucking reason and that's why you're crashing it. Another question, who the fuck wrote the security of this? I can literally send commands to the server with this insecure method and delete all of your files... If you actually want your fucking server stable and secure, I'm gonna have to recode this entire module to reduce your developer's clusterfuck of 4.8 million cycles to about 400 every hour... it's gonna be $50.
D: *Angered* You're wrong, this is the best way to do it, I did stress testing! *Insert other defensive comments* You're just a shitty developer (This one got me)
Me: *Calm* You're calling me a shitty developer? You're the person that doesn't understand a timer, I get that you're new to this world, but reading the wiki or even using the game's forums would've ripped this code to shreds and you to shreds. You're not even a developer, cause most of this is so disorganized it looks like you copy and pasted it. *Get's angered here and starts some light screaming* You're wasting CPU usage, the game can't use more than 1 physical core, and after a quick test, you're stupid 'amazing' module is using about 40% of the CPU. You need to fucking realize the 40ish average players, use less than this... THEY SHOULD BE MORE INTENSIVE THAN YOUR CODE, NOT THE OPPOSITE.
O: Hey don't be rude to Venom, he's an amazing coder. You're still new, you don't know as much as him. Ok, I'll pay you the money to get it recoded.
Me: Sounds good. *Angered tone* Also you developer boy, learn to listen to feedback and maybe learn to improve your shitty code. Cause you'll never go anywhere if you don't even understand who bad this garbage is, and that you can't even use the fucking wiki for this game. The only fucking way you're gonna improve is to use some of my suggestions.
D: *Leaves call without saying anything*

TL;DR: Shitty developer ran some shitty XP system code for a game nearly 4.8 million times an hour (average) or just above 7.6 million times an hour (if maxed), plus running MySQLite when it could've been done within about like 400 an hour at max. Tried calling me a shitty developer, and got sorta yelled at while I was trying to keep calm.

Still pissed he tried calling me a shitty developer...

Aggressively eliminate from your life everything that causes the slightest mental distress. Replace everything that has to it even a hint of undesirable emotions.

I once read about a girl who left work to buy a plane ticket to Australia to get away from her abusive boyfriend, and started her life from scratch. Being in an abusive relationship myself, I envied her.

One million seconds is eleven days. One billion seconds is 31 years. If you have just one second to spend with a person, you won't run out of the population for 248 whole years. There is no such thing as an irreplaceable person, no matter if they're your father, mother, best friend, wife, or husband.

Pain and trauma won't really go away, but they won't get bigger. You, however, can. One day you will be dying, and realizing at that moment that you didn't live the life you wanted to live, while knowing it's too late now, is the scariest thing that can happen to a human being. As you fade away, the sense of time will slip, and whatever you're feeling will stretch to eternity. Make it an eternity of calm happiness, and not an eternity of doubt and sorrow.

Make sure that when this moment comes, you're ready and comfortable with the life you lived. At least be confident it was YOUR life, and not someone else's.

This goes to everyone, both mentally/physically ill and healthy, and to both neurotypical and on the spectrum.

TDD.

I'm a fan of writing tests right after you write every module. I actually think it's doable.

But I'm not a big fan of traditional TDD, which is defined as: first writing the tests, making them fail, writing code until tests don't fail.

My experience with traditional TDD when writing library code is that you start with this very naive idea of what is needed, so you write classes and functions and a lot of times they look like overly simplistic pseudocode.

So what do you do? You scratch that, you delete those classes/functions several times.

I think this discovery process that your code is naive is slowed the fuck down by doing TDD.

I'd rather write a theoretical API in a readme file, then write code, and then write the tests, you can even withhold writing the tests, but never leaving them for another day, just so that you don't waste time writing tests that you're going to scratch.

There's always a time constraint, and most of us can't afford bikeshedding.

Traditional TDD feels like an esoteric thing, it tries to make programming a series of steps, it actually sounds like an infommercial.
"FOLLOW THESE 3 SIMPLE STEPS AND WRITE THE BEST CODE EVER"

*At Family Dinner Party*

Aunt- "Oh you're on of those web code guys, that's so cool!"

Me- "Thanks! So what are you do-"

Aunt- "So I have the best idea for a website, we could me millions!"

Me- "Is the food ready..?"

I loved what Flash used to be. Most people thought it was proprietary stuff. The program was. It's language was not. And damn, did we have fun together! We rendered vector graphics from code and pushed perlin noise into bitmaps while the HTML guys were still struggling with rounded corners. Oh, those bezier curves we dreamed up out of thin lines of code!

Other people just couldn't see how beautiful you were. They hated you because you were popular, and ads were beginning to dominate the landscape. And lots of dildo's made ads by abusing your capabilities, straining you with their ugly code that didn't remove event listeners properly. I always did, because I loved you.

They made fun of you because you had to be compiled. Look what those cavemen are doing now, dear ActionScript 3.0. They are compiling Javascript and pushing it to production. They are all fools my dear, unworthy to read even a single line of your gracious typed syntax. We were faster then Java. More animated and fluid then CSS. We were even responsive if we needed to.

But... I have to move on. I don't know if you're still watching over me but I can't deny I've been trying to find some happiness. I think you would have wanted me to. C# is a sweet girl and I'm thankful for her, but I won't ever forget those short few years we had together. They were the absolute best.

Rest well my dear princess.

People who don't mind their business.

So a while back, in a casual conversation I mentioned to a customer that I maybe might *possibly* have some jewish ancestry, on my *fathers* side, like my grandparents. Distant ancestry. Like the sort of distance that leads to things like dumb polish jokes.

Anyway, this guy starts coming in on a regular basis and talking about jewish related things constantly and I just want to ring him up and be left alone.

He asks me "so aren't you supposed to be in synagogue or something? I thought you're people were really adamant about not working on the sabbath?"

I looked at him deadpan and said "Money is my religion. Have a nice day."

He laughed nervously "uh yeah, thats good, okay, gotta run."

Best part was he forgot his eleven cents in change.

Dear Microsoft,

you're fucking awesome , can't believe I'm saying this but I couldn't work without Visual Studio anymore.

The last year I had projects on all platforms out there and I've used dotnet for all of them.

Mr Nadella is the best thing that happened to you ever.

Visual Studio is free and like the rest of the tools it's only a matter of Time till you open source Vs.

Thank you !
Proud to be a corporate fanboy.

!dev

Why do I hate my extended family coming over for lunch and dinner you ask?

> kids, who will ruin the remote by pressing the keys so hard, I'll have to get a new remote.

> NO PEACE. I'll have to move from my comfort spot to another spot where, again kids, will come and ask if I have "GAMES" in my mobile or laptop

> and this happened after lunch while watching a movie which I never watched before, my imbecile cousin decides to spoil the entire movie just like that, like, FUCK YO, LIKE REALLY, I KNOW YOU'RE MY RELATIVE IN SOME WAY, BUT FUUUUUUCK YOUUUUUU, spoilers is one of the things I cannot stand.

> I really do not like to be annoyed again and again and again and again, so please stop asking me if I want to have lunch or dinner with everyone because I really HATE the talk during that time.

> I leave my laptop for one microsecond and they surround it like scavengers, I MEAN FOR FUCKS SAKE, GIVE ME MY PRIVACY, (I have my own room, but it's under renovation).

The best I could do was to put on headsets and pretend like I'm working while browsing LinkedIn.

> "Oh I see you have HD TV, but the picture is blurred" NO SHIT, SHERLOCK, It is due to I chose not to buy HD Pack because I live stream HD Channels and cable is a backup

The best beverage for when you're stuck working on an old project with weird code.

Dark-themed IDE + back-lit keyboard + coffee + headphones = best coding environment ^_^

Though there's always that one asshole who decides to talk to you Only when you're in the zone.

Mentors, take note. This is a best practice over here.

I've spent two days digging through obscure documentation trying to accomplish one of those tasks that is simple in word and complex in deed. Namely, I wanted to concatenate (not delete) near-duplicate values in Pandas before rendering the data into a graph. Two days beating my head against the wall.

One of my mentors (I'm an intern) heard about the issue, wrote in the proper line (a very specifically and archaically formatted command), and pushed it to repo without even asking for thanks. Works like a charm and he saved my rear end. What a guy.

Please, mentors, don't leave your interns hanging on problems where the only solution is shrouded in dubious documentation and magic syntax. Especially when there's a deadline involved. Let them struggle on logic flow and writing good code.

Be like this guy. You'll build the importance of teamwork and your intern will think you're a wizard.

When you're alone with your dev problems but still you have the best code partners anyway :D

What was your most disappointing moment as a software developer?

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

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

Subaru's Symmetrical AWD is the best thing in the world at the moment. Also, warning: !dev

Tl;dr: I'm getting another RPi3 thanks to awesome engineering.

Got a couple of inches of light snow here, and on my way home I came across a GMC Sierra dually stuck at the bottom of a moderately sized ditch. Naturally, I stopped by in my Forester and offered to tow it out.

With my 20ft tow rope stretched to its full length I was barely touching the road. He signalled that he was ready, and I gunned it. Slowly but surely the truck crawled out of the 6ft deep trench. She crested the hill with much applause (from me and the driver of the truck). As a thanks, he gave me $30.

Looks like I'm gonna get a new Raspberry Pi to play with. I think I'll turn this one into a countertop MAME arcade machine.

And for those of you wondering why I'm praising Symmetrical AWD as opposed to AWD in general, here's a quick lesson in drivetrains:
Most all wheel drive cars power the front wheels most of the time. This saves on fuel economy. The thing is, power is only transmitted to the rear wheels when the front wheels start to lose traction. At that point you're already screwed; only two wheels at any one time are putting useful power to the road.
Symmetrical AWD systems, like you'll find in all Subarus and most performance cars, distribute the vehicle's torque eaqually front-rear at all times. So instead of waiting until the front wheels start slipping, all of the wheels are powered right off the bat.

To make this more devvy: grrrr php, vim is best, I configured the tab key to enter four spaces, js has too many damn frameworks and they're still being pumped out faster than rabbits in a bunny farm.

So, someone is trying to catfish me in some social media.
And I can make a few guesses about who it might be. Or maybe I'm being paranoid and all the accounts contacting me randomly, are just spam bots.

But this isn't the first time. From a hateful ex, to someone I turned down because I had zero feelings for, to even random stalkers who found me online and thought that I was the best choice for obsessing over, I've seen different types of online ghosts.

Like... why is it that it takes so much for some people to be decent? Why can't you just say it to my face (aka directly), get your answer, and then fuck off? And if you're actually obsessing, it is not my problem. See a fucking therapist.

Anywho, aside from the wish to be able to occasionally deliver an online slap, and occasionally wishing that everyone on the internet had an ID to be found IRL, I would like for internet to be a less hateful/harassing/terrorizing/bullying/discriminating place. I like internet. I have so many awesome friends on the internet.

I just needed to rant about it so it doesn't weigh on my mind. Now I'm gonna go back to ignoring them and living my own life peacefully. I hope y'all have a good day. 🙂

<rant>
Don't fucking tell me to move business logic from the service to the controller. Don't fucking tell me it will enable an "event driven architecture." Don't fucking use Angular for this project if you're just gonna shit on best practices and write convoluted, messy, inconsistent code and force your coworkers to do the same!
</rant>

Elon musk has shown himself to be a terrible person, a worse manager and someone who hasn't a clue of what a code review is. A summarily fires so many people that he can't find someone to open the doors for his big in person meeting or the vet the badges. He offers 3 months termination pay or you can work 12 hours a day 7 days a week hardcore. But none of the payroll people are around anymore either. Critical subsystems have not a single engineer left to work on them. He's paranoid that employees will sabotage the software. But I think he's doing such a good job it would be impossible to tell that anyone else was helping him.
An engineer wrote a prescient seven page report listing problems ahead including user verification. So Elon twit-fired him.
Also entirely predictable is the stress that the world cup will put on the system beginning today, I believe. He doesn't "like" microservices.
I work for the psychiatrist once who barely needed to sleep. Maybe Elon can function with 12-hour days week in week out. But it's cool to think you're going to squeeze substantially more work out of people by doubling their hours. More likely you will more than double their errors and what will that do to you budget? 50 years ago IBM determined that the best way to improve programmer productivity was to give each one their own office.
I can't believe he's whining over spending 13 million dollars a year on food. That is so far from being a strategic item. Soapbox out.

Absolutely not dev-related.

Blah, blah, weird conversation and shit. I'm too tired and lazy to write this crap again, but let's do it.

The guy is a dev I randomly found on some chatting service, he was interesting to talk with until this conversation. I'll write this out of memory, so yeah.

Him: So by the way I wrote an app that you give your penis size to to get measurements and stuff about it.
Me, thinking it was dev humor: That's hilarious. Tell me more, I'm interested.
Him: So the idea behind all of this was to gather some big data style info about people's penis size and habits and all that stuff.
Me: Man that's awesome. Can I see the source?
Him: No, it's proprietary. You can buy a license though.
Me: You went that far for a joke?
Him: What joke?
Me: The whole software you just told me about.
Him: That's not a joke, I'm being very serious about it.
Me: Oh well. What did you get from the stats?
Him: I got some tips from people's habits! I never thought that shaving it could make it look bigger, but that's awesome!
Me: Do you really care about it that much?
Him: Studies have proven that size correlated with confidence. Since I started doing it, I've been more confident than ever!
Me: Great.
Him: I'm a bit disappointed to see that I'm in the lower percentiles though.
Me: Well of course you are.
Him: Why would you say that?
Me: Well since people with a big dick tend to go more willingly into the subject and might even buy a fucking app for it, of course you'd have the higher average in your stats.
Him: You're only saying that because you have a small cock.
Me: Why the fuck would you say that? You're the one that's concerned about it, not me.
Him: Go on, what's your size?
Me, because I don't care about discussing that stuff: *Tells him*
Him: [stats, comparisons and stuff]
Me: Well I never gave a fuck and your stats won't make me change my mind.
[ ... Some other shit about my size compared to his ... ]
Him: Would you want to work with me for the database maintenance?
Me: You must be joking?
Him: I'm serious.
Me: *Deletes account*

Seriously, fuck that guy. I rewrote that quickly so you only had the best, but it was a whole fucking conversation.

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 have a serious question.
I particularly address Italian ranters.

It's about time to decide what faculty/"subject" I should go to, and I'm uncertain between "Informatics" and "Informatic Engineering".

Does someone know what the differences between the two are, and, given that I want to do as much programming (and so practical stuff instead of theorical stuff) as possible, which of these two faculties should suit me best?

If you're not from Italy, but from other countries, of course that shouldn't stop you from posting a response, if you want to.
How do Universities work there?
Are they like ours, in Italy, or does it work differently?

Thanks for your patience. 💙

!rant
if you're someone who grades code, fuck you, you probably suck. Turned in a final project for this gis software construction class as a part of my master's degree (this class was fuck all easy, I had two weeks for each project, each of them took me two days). We had to pick the last project, so I submitted final project proposal that performs a two-sample KS test on some point data. Not complex, but it sounds fancy, project accepted. Easy money.

I write the thing and finish it, it works, but it doesn't have a visualization and that makes the results seem pretty lame, even though its fully functional. SO I GO OUT OF MY FUCKING WAY to add a matplotlib chart of the distribution. To do that, at the very bottom of the workflow, I define a function to chart it out because it made the code way more readable. Reminder, I didn't have to do this, it was extra work to make my code more functional.

Then, this motherfucker takes points off because I didn't define the function at the very beginning of the code... THE FUCK, DUDE? But, noobrants, it's "considered best prac--" nope, fuck you, okay? This class was so shit, not once was code style addressed in a lesson or put on any rubric - they didn't give a shit what it looked like - in fact, the whole class only used arcpy (and the csv mod once), they didn't teach us shit about anything except how to write geoprocessing scripts (in other words, how to read arcGIS docs about arcpy) and encouraged us to write in fucking pythonwin. And now, when the class is fucking over, you decide to just randomly toss this shit in, like it was a specific expectation this whole time? AND you do this when someone has gone out of their way to add functionality? Why punish someone who does extra work because that extra work isn't perfect? Literally, my grade would have been better without the visualization.

I'm not even mad at my grade - it was fine - I just hate inconsistency in grading practices and the random raising and lowering of expectations depending on how some grader's coffee tasted that morning. I also hate punishing people for doing more - it's this kind of shit that makes people A) wanna rip their eyeballs out, and B) never do anything more than the basic minimum expectation to avoid extra unwanted attention. If you want your coders to step up and actually put work in to make things the best they can be, yell at a grader to reward extra work and not punish it.

One of the best feelings is when you're reviewing PRs, leave a comment of an issue you're seeing & another developer supports & agrees your comment, so the original creator of the PR doesn't think you're making things up.

Subject: a rant for devRant

Hello,

Not entirely sure why or when exactly it happened, but after I joined mailing lists I have a pet peeve for people who don't use a proper subject line, or don't use email when I literally made a mail server for that purpose (some organizations really prefer calling apparently). Is it really that hard to summarize a message in one sentence? Hell half the time even the message itself is just a few sentences.

Also the greeting and salutation at the beginning and end of email messages. I find them so redundant. Has anyone ever gotten any meaningful information out of "Hello", "Greetings", "Dear", or something like that? Or "Best regards" or whatever. I get that it's just being polite but it's so meaningless! I really don't like using them anymore. Just a message block and who it came from, that's all it needs to me. Instead pour some effort into the damn subject, the title of whatever drivel you're putting out there! Or replying to an email *only* when the subject matter is still related! Or actually replying to the damn email if it's still that subject matter...

I probably sound like an old man, but seriously.. email isn't a hard concept once you "get it". Anyone can write a halfway decent letter, why isn't that the case for email?

Best regards,
Condor

It's great when you see your position being recruited for and after 2 months of scouting management still can't find someone better.

Hate me all you want I'm still the best you've got and apparently the best you're getting.

What are they going to do when I tell them I'm done after this project 😂🖕💯

So technical interview today but woke up (6am) and started thinking about it and it led to this rant about algorithms. This is probably going into a Medium post if I ever get around to finishing it but sort of just wanted to share the rant that literally just went off in my mind.

*The problem with Algorithms Technical Interviews Is They don't test Real skills*

Real world problems are complex and often cross domain combining experience in multiple areas. Often the best way is not obvious unless you're a polymath and familiar with different areas, paradigms, designs. And intuitively can understand, reason, and combine them.

I don't think this is something a specific algorithm problem is designed to show. And the problem is the optimal solution to some of these and to algorithm design itself is that unless you train for it or are an algorithm designer (practice and experience), you can only brute force it in the amount of time given.

And quite frankly the algorithms I think we rely on daily weren't thought of in 30 minutes. The designers did this stuff for a living, thought about these problems for days and several iterations… at least. A lot were mathematicians. The matrix algorithm that had a Big O of 7N required a flash of insight that only someone constantly looking and thinking about the equations could see.

TBA
-system design
-clean readable coding practices
...

TLDR: I could probably go on and on about this stuff for hours jumping from item/example/area to the next and back again... But I don't think you can test these (~20) years of experience in a 1 hr technical interview focused on algorithms...

Not doing it for the money alone unless you want to be depressed and wealthy.

Find the most inspiring work that pay your bills: when you're the best at what you love you will find a way to get paid for that (or something closely related).

On the micro level, I try to talk to / learn from coworkers a lot and take regular breaks.

Recently I receive a ton of mails from cool/hip/rockstar startups. They all run like this:

"We are a innovative Startup based on a [insert some random stuff or buzzword] blockchain! If you're a student with skills and experience in blockchain, machine learning and AI willing to change the world with our sick technology and make it a better place..."

The best thing about this: since they are a innovative Startup they expect you to work for free.

But who am I to judge something so brand-new and innovative. I contacted them to find out what these dank innovations are about.

They can't even explain what a blockchain is or the basics of ML and AI, they basically just want someone do it for free...

It's still ok since no one is gonna fall for this bait... this morning a friend of mine told me he got a new job... and he even can work from home...

I'm not even mad, I just feel sadness and sorrow specially for him, because he is a good dev and accepts big times underpay and now free work, because he thinks a day off in his CV will lead him to be unemployed 😭

Fucking hate it how people successfuly manipulate kids and youth to them to work 24/7 for minimum wage or even for free and some other douchebags trying to take advantage of this 😡

I have been commenting a lot recently on linux ranters who rant about windows for stupid reasons.
To all these people who think linux is better and they are smart(er) than windows users, i say:
We use windows in the company I work for. And if you are a linux user, you're just not welcome and your skills are just a waste for the company. And yes it is a successful company with 100s of millions of euros as net revenue.
Our users have windows machines and we offer topnotch Microsoft solutions for them.
When you ask me to switch to linux because of a problem i had in a Windows machine, it makes me feel that you are a stupid person who knows about linux and gives solutions based on his stupidity and on zero knowledge of the scenario.
Please be professional and think about the solution you are offering. It would be best if you did not offer any solution at all in fact.

Just now... Got a job to create patch files for a couple of jars, which may or may not have varying class files. In total, I have to decompile, check, add and synchronize about 30 class files in 6 jars with a new functionality (that I didn't write). 🙂

FUCK PRODUCTION! WHY CANT YOU MAINTAIN ONE MOTHERFUCKING JAR?

OH? YOU'RE SUPERSTITIOUS THAT ONE TINY, ANT-SHIT SIZED CHANGE IN ONE SIMPLE FUNCTIONALITY WILL FUCK UP *OUR* PRODUCT?

FUCK MANAGEMENT! YOU DON'T HAVE CONFIDENCE IN YOUR *OWN* PRODUCT!

OH? CUSTOMER COMES FIRST? HAVE THE BALLS TO DEFEND YOUR OWN FUCKING SELF AND PRODUCT TO THE CLIENT OR THEY'RE GONNA MAKE YOU YOUR BITCH AND TIE A GAGBALL DIPPED IN HOT SAUCE AROUND YOUR MOUTH! HOW.. THE FUCK.. DID YOU MISS THAT LOGIC??????

Best part, they want it by tomorrow, and they don't wanna test it. Guess who's gonna get slaughtered after a week? ME! 🙂

It's not that big of a deal, but it's kinda embarrassing since I was one of the best students in the class.

Took a web design (HTML, CSS & a tiny bit of JS) class. I never really struggled; more like polished everything I already knew to become a bit better.

In class working on an assignment. So we have a folder dedicated on a server just for this class. The folder is accessible as long as you're on the school internet or using the VPN. So I have an assignment there. I drop it onto my desktop, because i had worked on it since the last time I was at this computer.

I opened the project in VSCode and begin making changing things. I opened the HTML file wasn't updating. "That's odd" I thought. Cleared the cache, opened and closed the browser. Still nothing. I called the professor over to see if had any clue what was going on.

My dumbass self was editing the file that was on my desktop, but I had opened the HTML file from the server. I felt so stupid but we both just laughed it off and went on.

!Rant

The Eve V is a Community Developed Windows Tablet which will be released in Ocotober this year.

The best specs you can get is i7 6th Gen, 16 GB Ram and 500 GB SSD for around 1400$.

He wants 32 GB RAM in such a slim and small Tablet. Also wants a 7th Gen Intel CPU and 1 TB SSD in it. He's ready to pay 1000 $ more for his special edition.

The Eve V is already finished with tooling and they are wating for the screens to arrive. They already have all the other parts.

Dude you're crazy and that specs just for VM's? What are you running? 10x WinShitBox?

He's insulting everyone on the forum with a different opinion and says, retooling will be such easy.

That guy is a real douchebag and doesn't know shit. If you would build in different parts like this, you would need to remodel the whole tablet. You can stick your 1000$ in your ass, retooling would cost more than 10'000$

If it's so easy you shithead, then do it yourself and dont say it's possible and say to other people they should do! 😂😂

I've been working like a mad woman in a startup for 3+ years now. They feel like 10. Or at least the tech stacks we went through.
Never, ever join a startup, regardless of compensation, unless you know you can emotionally and mentally recover from that startup failing as if it is yours, not your bosses. Otherwise, it's just a shitty short experience.

My long experience is shitty, but man. I don't know.Those who built google, wanted to make a search engine. Did they know they're gonna be good? NO. This is the result of them being good. They now have that great product that succeeds and is able to become a self-referential piggy bank. You cannot be a self-referential piggy bank based on a fucking belief and idea, and a bunch of VCs who already put money in you. You know why? BECAUSE GUESS WHO IS THE ONE RESPONSIBLE FOR SUSTAINING YOUR START UP NOW?

The bloods and passions of youth, that join your startup, thinking they can make a difference, and you just undermine them constantly thinking that no engineer can make a difference if they can't ensure compliance with your dumb funding strategy.

Don't even get me started on the fact that most people who work for startups, rely on either laziness or passion. It's like a bunch of kids in art school, whose professor doesn't like anything they make, but they still kinda like it hoping one day they leave and become artists themselves. Then they discover that this shit professor actually taught them nothing about creativity in the real world, and what it takes to push something out.

And, it finally fucking hit me.

The reason startups will never work in this year, and beyond, AND TILL I SEE A CHANGE IN ATTITUDE IN 10 YEARS.....

The market won't fucking allow it with the current strategy tech companies are a fan of: hire a bunch of passionate devs who wanna learn a tool through doing our unique work. Doesn't matter. DIVERSITY. THE UNION IS THE PASSION. That's dumb as fuck.
Why?
Here:

- Passionate people do not have to use passion as an incentive, the passion was there, and them getting their idea made or money is the incentive
- If you hire a passionate person - even if they are the fucking best - you just made their passion a tool, in getting your PRs done and shit epics scoped AT BEST, and so the tools you're teaching them to use are getting away with doing less impactful, productive, creative work.

I AM SO DEPRESSED.

Hey devRant! It's been a long time, but I'm baaack! I know you missed me, but my life has been so eventful, and difficult, and so I am here for sympathy and recognition of my status among my fellow devRant community, because like, I'm basically a legend now, I'm sure you've all heard of me!

Did I mention I'm back!? I know right, it's mad, it's like the place hasn't been the same without me. What has changed? Man, I remember when devRant was a toddler colouring in my walls with crayon, man those were the days...

Oh, have any of you seen @OtherLongtimeUser about, are they still alive? Come on guy, we were like best buddies, and your existence validates my sense of self-worth in relation to my status on this here community. You about?

Anyway, life's been hard, I'm sure you're all desperate to hear about it... Looking forward to you asking me about it in the comments so that I can skirt around the answer for you whilst still trying to extract the maximum amount of sympathy. But yea, just tell me you've missed me, that'd be fantastic.

Also, I bet the banter on here isn't like it used to be. All you n00bs missed so much. But hey, did I mention, I'm baaaaack!? ✌

Let's talk about the cargo cult of N-factor authentication. It's not some magic security dust you can just sprinkle onto your app "for security purposes".

I once had a client who had a client who I did server maintenance for. Every month I was scheduled to go to the site, stick my fingerprint in their scanner, which would then display my recorded face prominently on their screens, have my name and purpose verified by the contact person, and only then would the guards let me in.

HAHA no of course not. On top of all of that, they ask for a company ID and will not let me in without one.

Because after all, I can easily forge my face, fingerprints, on-site client contact, appointment, and approval. But printing out and laminating a company ID is impossible.

---

With apologies to my "first best friend" in High School, I've forgotten which of the dozens of canonicalisations of which of your nicknames I've put in as my answer to your security question. I've also forgotten if I actually listed you as my first best friend, or my dog - which would actually be more accurate - and actually which dog, as there are times in my High School life that there were more tails than humans in the house.

I have not forgotten these out of spite, but simply because I have also forgotten which of the dozen services of this prominent bullshit computer company I actually signed up for way back in college, which itself has been more than a decade ago. That I actually apparently already signed up for the service before actually eludes me, because in fact, I have no love for their myriad products.

What I have NOT forgotten is my "end of the universe"-grade password, or email, or full legal name and the ability to demonstrate a clear line of continuity of my identity from wherever that was to now.

Because of previous security screwups in the past, this prominent bullshit company has forced its users to activate its second, third, and Nth factors. A possibly decade-old security question; a phone number long lost; whatever - before you can use your account.

Note: not "view sensitive data" about the account, like full name, billing address, and contact info. Not "change settings" of the account, such as changing account info, email, etc. Apparently all those are the lowest tier of security meant to be protected by mere "end of the universe"-grade passwords and a second factor such as email, which itself is likely to be sold by a company that also cargo cults N-factor auth. For REAL hard info, let's ask the guy who we just showed the address to "What street he lived in" and a couple others.

Explaining this to the company's support hotline is an exercise in...

"It's for your security."

"It's not. You're just locking me out of my account. I can show you a government ID corroborating all the other account info."

"But we can't, for security."

"It's not security. Get me your boss."

...

"It's for security."

Algorithm doing wonders

Not really Dev advice, but I appreciated it.
"Do your best to take responsibility for everything that happens to you. Even if it's not your fault."
"On the flip side, never apologize for something that isn't your fault. That includes other people's feelings. You're not in control of their emotions."

Just the fact that you wrote your simple single page "contact us" website in React shows that you have no idea what you're doing, nor do you have any idea what the actual benefits of React are and in what situations it actually shines. You're just jumping on the React bandwagon for the sake of saying "I wrote it in React," and your decision to use React for that simple website is going to effectively increase It's development time without adding any additional benefits.

Each framework has its advantages and disadvantages. It's worth it to pay attention to these advantages/disadvantage, and choose the best framework to fit your needs. Don't just use a particular framework because it's the hot new craze. Use a framework because it's the right choice from a technical standpoint, and presents you with advantages that fit your application needs.

I really don't get the frustration people have with debugging...
It's one of the most fun parts of programming for me.

I don't mean the missing semicolon (I use an ide cause I care about my time).

When all your seniors have spent hours on trying to find a bug and after a few days you're able to present a fix to them, that honestly is the best feeling, potentially better than "finishing" a product (let's be honest, it's never finished)

A medical doctor, a lawyer and a programmer debate whether it's best to have a wife or a girlfriend.

"Easy", the lawyer starts, "a girlfriend comes without any legal obligation, you can have a lot of fun together but when you get enough of her, you can just leave her without any trouble"

The physician objects: "That can only come from a man who never truly loved a woman. Your wife is not just someone who you have fun with, she is you bastion of calm, your ever-loyal partner, the completition yourself. Clearly, having a wife is better"

Both now look at the programmer who remained silent throughout the debate.

He cleans his throat and than says: "Both. You need both. You can tell you wife you're with your girlfriend and you can tell your girlfriend you are with your wife. And then, you can finally code in peace.

How do you teach non-technical coworkers to trust you're doing your work to the best of your ability? You know the type, they're used to having everything measured by simple numbers. Number big = good work. Number small = bad work or slacking off. The moment they run into something that doesn't work like this, their heads explode.

What's the best thing about a Boolean? Even if you're wrong, you're only off by a bit.

(Part 2/2?)

THE RAT-RACE ARC:

I get a mail 2 months into this fiasco telling me to register on their website and take up another test. I was already over with my emergency and was working my full-time default. (Fortunately I found another internship during this time which was one of the best initiatives I've worked with).

It asks me to register as a new user, take up the test and "share" my results. Not pushing it on insta/fb but legitimately share my test results link to my friends manually like a referral code. The more shares the more marks I'll get in the test. Why the test you ask. Of course to sign you up for the same Whatsapp trickery bullshit.

Luckily these nutcases didn't know they could be bypassed. I simply opened the link in incognito and logged in with my own account and that counted as a point. So I automated that shit.

Surprise surprise. The same fucking "Hello everyone" message into my mail. To my surprise I was relatively lucky to get ghosted after my attempt. This story is quite depressing in general cases. You're supposed to do this assignment shit for 2 months and then they ask for 2000 INR for a training period, past which you are paid between 1000/- and 7000/-. Though I didn't get the chance but I'm willing to bet you get 1000/- per month in a 2-MONTH INTERNSHIP. WTF.

You also have the other option of ranking first in their 3 consecutive competition that they hold. The theme is again to create chunks of their actual outsourced work.

WHY NOW:

The reason why this rant sparked is because I recently received an email with my results of the aptitude exam that I first took before the Whatsapp fiasco. I imagine they just pushed out a new update to their test thingy and forgot to set it's limit.

THE CORRECTION ARC:

I pushed this message to Internshala. They were kind enough to remove them from their website. I also shot down their Angel and Indeed listings. I sent a strongly worded email counting their con-artist operations and how I've alerted authorities (obviously a bluff but I was enjoying it). They most probably are not affected by this though. They might still be continuing their operations on their website.

I'm sharing the story here with the moral of:

Don't do jackshit if they're not compensating you for it

Always check for reviews before you start working at a place.

Be cautious of bulk messages (and the infamous HEY GUYS!! opening)

Don't do anything outside your work specification at least while doing an assignment.

You're free to question and inquire respectfully about the proceedings.

If you're good at your job you'll get good working place. No need to crush yourself with an oppressive job due to external restrictions.

And if you manage a company, please don't take advantage of helplessness.

There's no good ending to this tale as I have not received a follow-up. Though I want to see scumbags of their calibre shot down without remorse.

Good bye and thank you for listening.

If you really think about it, asking a person what their pronouns are, he/she/they etc., is basically sending a REST OPTIONS request. What a technically pure and proven thing to do.

You assume OPTIONS response of an API, you get "400 Fuck You". Or, if that API is nice, you can get "426 Get Out Of Your Cave", but that's the best you're gonna get.

I just don't get the WordPress hate or CMS hate in general. Using these is not perfect, but neither is _anyone's_ code. Get over that and be more productive for your client. Unless you're the best coder the world has ever seen, and you're _always_ available to push content for an organization of 90 or 900 or 9,000 people, nobody CARES about your "coding purity". They want a website that they can still operate if your ass gets hit by a bus. Don't like WP? Find a CMS that ticks most of the boxes for your client's needs. If you have the time, budget, and long-term inclination to provide bug fixes for it, write your own Awesomesauce Custom CMS(TM) and release it to the open source community so we can finally replace WordPress with the next best thing.

Otherwise, launch site, get check. Repeat until you can retire.

The worst part of being a dev? Working in teams.

And I don't mean that in the "I'm the best ninja code wizard in the whole world and you're all holding me back" kinda way. I'm thinking more in the lines of someone who has to deal with that kind of attitude on a daily basis. As someone who recently was put in a leading position in a dev team, this is by far one of the worst experiences that came with it.

Some examples?
- One dev completely changed the naming scheme for variables in a class he worked on for one. single. bug fix. His reason? He just didn't like it!
- Another one noticed that data he was supplied with was not in the specified format. Instead of flagging this with the project leads, he just rewrote his parser to fit the data. A couple of weeks later the supplier noticed the error, fixed the format and suddenly everyone wondered why the software failed processing the data.
- Or that one senior dev, that just refuses to accept changes because "it was always done like this and it worked" No, it didn't. That's why it was changed!

Once a dev team reaches a certain size, people need to realize that stuff like coding rules and process guidelines are not there to annoy them but to help the whole team work as efficient as possible. I don't care how good a programmer you are, if you can't check your ego you don't belong in any kind of team-oriented development project!

I tried to go for a job as a ReactJS junior dev.. I got my first interview and they liked my prototype.. but..

A week later they reply: "We decided not to go with you because we hired an expert in ReactJS".

Err.. really? You're hiring expert-level ReactJS developers for a junior position?! What the frig.
You want to know what I think? This whole "It's ok that you don't know everything, you'll learn on the job" thing is a hoax. No, the job market doesn't want novices. With every single interview, I'm met with: "but you're not an expert and we can't afford that".

This reminds me of the best advice my professor (seasoned expert in the field, real engineer with more than 20 years experience) once gave me:

"The job market doesn't have the time nor patience to mollycoddle you. When you enter it, you have to already know things to an expert degree because companies want value. They're hiring you because you have these skills and knowledge.
You have to already know what they ask before they ask it. You're required to know things by yesterday, so to speak. It is an exigent industry out there. This is why we bring you the foundations - so that you go further on your own and you can take on any problem"

What was/is your favourite learning experience?
The best teacher (besides google) for your language of choice?

Was it a book? a video series? an instructor? A person? A mentor? Your cat? Maybe dissecting someone else's code...?

Mine is laracasts.com You're welcome Jeffrey.

when your family comes to you to fix every problem with their computer and you're too tired of explaining what you actually do, so you put on your most professional look and hope for the best

The feature was to parse a set of fairly complex xml files following a legacy schema. Problem was, the way this was done previously did not conform to the schema so it was a guideline at best, which over the course of many years snowballed into an anarchy where clients would send in whatever and it was continuously updated per case as needed. They wanted to start enforcing their new schema while phasing out the old method.

The good news is that parsing and serialization is very testable, so I rounded up what I could find of example files and got to work. Around the same time I asked our client if they had any more examples of typical cases we need to deal with, and sure enough a couple of days later I receive a zip with hundreds of files. They also point out that I should just disregard the entire old set since they decided to outright cut support for it after all if it makes things simpler. Nice.

I finish the feature in a decent amount of time. All my local tests pass, and the CD tests pass when I push my branches. Once we push to our QA env though and the integration tests run, we get a pass rate of less than 10%.

I spend a couple of days trying to figure out what's going on, and eventually narrow it down to some wires being crossed with the new vs. old xml formats. I'm at a loss. I keep trying to chip away at it until I'm left with a minimal example, and I have one of those lean-back moments where you're just "I don't get it". My tests pass locally, but in the QA environment they fail on the same files.

We're now 3 people around my workstation including the system architect, and I'm demonstrating to the others how baffling and black magic this is. I postulate that maybe something is cached in my local environment and it's not actually testing the new files. I even deleted the old ones.

"Are you sure you deleted the right files?"

"Duh of course -- but let me check..."

One of the best feelings is when you're hip deep in code refactoing and you're delezing old code with your new and shiny code.

For the people working on small startups:

How do you keep updated on best practices, engineering, and all that when you're 24/7 focused on the startup (implementing, testing, fixing stuff)?

I feel like I love doing things the best way, but we always go with the "do fast, break fast" and it always feels like a mess because the engineering is done after a really small MVP is done (and after a long time usually).

I was hoping to be able to at least do a really small engineering part *before* starting anything new, but CEO always wants stuff done *yesterday*. But for this I think I should be reading more, and playing around with new patterns and all that, so at least I know out of the box what would be a good thing to start with and not having to change the entire project/script from scratch.

What do you consider the best method for long-term cold data storage? And why?

I was looking at some magnetic tapes, but the degradation of magnetic charge is worrying me. Lose a single bit and you're fucked.

Dvds - not sure, some of my old ones are no longer readable. Not sure why tho, they had been enclosed in a dark, room-temp place all the time

hdds -- still magnetic.

Ssds? Idk

...?

I'm not getting why you guys complain about being judged for "hacking" while using the terminal.

In my case I'd occasionally like to open a terminal in my lubuntu (or archlinux in my previous times where the laptop was running smooth and i had to learn everything about how an OS works and spending most of the time searching about errors to find more desperate people and no answers but the community's hopefully growing and it's the best distro if you're an experienced linux user but not in my case so i had to use lubuntu for now until mastering it) to trigger those around me and try to prove them wrong afterwards.

I'll hit the airport for fun when i have time.