GOD FUCKING DAMMIT MICROSOFT IT'S NOT THAT FUCKING HARD TO REMEMBER WHAT TIME ZONE I SET

😭😭😭😭😭😭

How thoroughly do you test when doing a code-review?

Node Version Manager? nevermind...

Here it is.

The CS final.

I reached this point in my life.

I hope I won’t forget the base case in recursion like last time and fuck up an entire question.

When you touchbase on all multiple languages but don't know any of them properly.

Focus on one. Focus on one. **talks to self**

Business logic:

Meeting starts at 9:45 AM. They only really wanna talk about the features they have on the horizon and how innovative and distruptive and rich we'll be. We spend 10, maybe 15 minutes talking about UI and details of the feaure. The meeting ends a few minutes before 12, so that's 2 hours of lunch (I wanna respect the schedules we had pre-covid to keep that rhythm). I start working again at 2 PM, but 15 minutes later, I get called again by one of the managers to hear more about this new great new idea they have.

So I work about 7-9 hours a day. But HR and management want to spend 3 of those hours. Suggestion: we'd improve our productivity by about 35% if we cut those daily meetings.

as a moral web developer, i always remember my abc’s

anything
but
chrome

seriously fuck google

Why I hate typescript. Bored during quarantine so thought I rant a little more about this.
1. Compilation time, typescript increases project compilation time from 1 second to 3-4 seconds, which is basically triple or quadruple the time if you don't know math.
2. You write a minimum of 30% more code.
3. Many libraries are not written in TS by default, which means you end up having to manually install a fuckton of @types/(pckg name) manually which is incredibly shit.
4. Typescript is an absolute pain in the ass when using dynamic libraries. Plus when it works, it usually ends up finding maybe 1-2 errors in your code MAX, completely not worth it.
5.JSDoc is 100 times better. (Still don't use it though).
6. I actually enjoy loosely typed languages, having your compiler being smart enough to tell what the type of your input is is much better than it assuming you're a fucking retard so it forces you to manually type everything.

P.S if you hate loosely typed languages, kindly resort to Angular, C#, Java or whatever and leave JS alone, cunt.

Have anyone created a git backup machine? Basically a machine in my network needs to be able to recieve git pushes from another computer.

React is tomorrow’s jquery

Work from home

Expectation:
- Free time from commute, more time for gaming

Reality:
- Free time from commute, more time for dev works

p.s. I'm more tired these days

Resolving merge conflicts feels like defusing a bomb.

Chatting on Slack with a junior dev:

[Junior Dev] How do I get that file from the server ?
[Me] ssh into it and then use scp

I see Junior across the room, literally saying "shshh..." at the computer.

Packed my stuff and quit that day.

If an enterprise software isn't hated, then it isn't known.

I am really stressed out. I am an unpaid intern. I need the stress ball. Can I get 300+1's ?

Two types of days:
Sit down and say imma be productive and then just end up scrolling through unrelated articles for 3 hours.
And, Sit down and say imma just do something quickly before going out and then end up restructuring whole parts and being up till 6am.

Me: Hi, how can i help you today?
User: Hi IT, I can't enter to my computer, i put my password and it says it's incorrect.
Me: Ok, hold me a few.

(10 seconds without do anything)
Me: Try again.
User: It worked! Thanks!!

Runtime runtime = Runtime.getRuntime();

You can't get more Java than this.

"So, tell us a bit about yourself.."

0, and sometimes 1

How to hide your important files from people without making Hidden folders 

1. Go to Desktop and create a new folder
2. Name the folder Internet Explorer
3. Change the folder icon to Internet Explorer
4. Keep it in a corner of the desktop

Now, no one will open internet explorer :D

If you haven't voted for devRant yet go on and do it! Here's the link http://thenextweb.com/scale/vote/...

If we ever colonize Mars or if we even go further I am already feeling sorry for the poor bloke that will have to work on DateTime library.

!rant

After over 20 years as a Software Engineer, Architect, and Manager, I want to pass along some unsolicited advice to junior developers either because I grew through it, or I've had to deal with developers who behaved poorly:

1) Your ego will hurt you FAR more than your junior coding skills. Nobody expects you to be the best early in your career, so don't act like you are.

2) Working independently is a must. It's okay to ask questions, but ask sparingly. Remember, mid and senior level guys need to focus just as much as you do, so before interrupting them, exhaust your resources (Google, Stack Overflow, books, etc..)

3) Working code != good code. You are an author. Write your code so that it can be read. Accept criticism that may seem trivial such as renaming a variable or method. If someone is suggesting it, it's because they didn't know what it did without further investigation.

4) Ask for peer reviews and LISTEN to the critique. Even after 20+ years, I send my code to more junior developers and often get good corrections sent back. (remember the ego thing from tip #1?) Even if they have no critiques for me, sometimes they will see a technique I used and learn from that. Peer reviews are win-win-win.

5) When in doubt, do NOT BS your way out. Refer to someone who knows, or offer to get back to them. Often times, persons other than engineers will take what you said as gospel. If that later turns out to be wrong, a bunch of people will have to get involved to clean up the expectations.

6) Slow down in order to speed up. Always start a task by thinking about the very high level use cases, then slowly work through your logic to achieve that. Rushing to complete, even for senior engineers, usually means less-than-ideal code that somebody will have to maintain.

7) Write documentation, always! Even if your company doesn't take documentation seriously, other engineers will remember how well documented your code is, and they will appreciate you for it/think of you next time that sweet job opens up.

8) Good code is important, but good impressions are better. I have code that is the most embarrassing crap ever still in production to this day. People don't think of me as "that shitty developer who wrote that ugly ass code that one time a decade ago," They think of me as "that developer who was fun to work with and busted his ass." Because of that, I've never been unemployed for more than a day. It's critical to have a good network and good references.

9) Don't shy away from the unknown. It's easy to hope somebody else picks up that task that you don't understand, but you wont learn it if they do. The daunting, unknown tasks are the most rewarding to complete (and trust me, other devs will notice.)

10) Learning is up to you. I can't tell you the number of engineers I passed on hiring because their answer to what they know about PHP7 was: "Nothing. I haven't learned it yet because my current company is still using PHP5." This is YOUR craft. It's not up to your employer to keep you relevant in the job market, it's up to YOU. You don't always need to be a pro at the latest and greatest, but at least read the changelog. Stay abreast of current technology, security threats, etc...

These are just a few quick tips from my experience. Others may chime in with theirs, and some may dispute mine. I wish you all fruitful careers!

This is what eclipse windowbuilder just told me

When the client is happy!

It's always so funny when a person starts using multiprocessing in Python, because if there's "multi", obviously THIS is the thing that should free the person from a headache of having GUI frozen. You know, because it does "multiple" ehm... stuff..... at once....... yeah. And it's popular, it must work for me too! Oh how often I see this. :D

Stupidly enough that's not entirely a user's fault, but Python's as naming things with "multi" doesn't end up well basically with anything. I bet if there was such thing as multipointer in C half of the beginners would be totally fucked and the other one would just break their machines beyond repair with a joy.

Yet... reading the damn documentation should be a requirement before using threading or multiprocessing to prevent the confusion, because there's this funny difference between multiple threads and multiple processes which will haunt you unless you see what's what and use it correctly.

$number = 3000/365*365-3000
echo $number

Output:
4,54747350886E-13

No, Just No. I really like you PHP but thats supposed to be zero. I don't got time for your Tantrum's. I got work to do!

PS: Does anyone know why this happens? Solved it by rounding on 10 decimals but prefer it would just answer 0 instead of me having to force it back.

its 2016, and they still believe that office skillz are enough for CS101..

boy u have to allocate memory in runtime without leaks by end of semester, not just make a text bold with a fancy font..

The beauty of DevRant is that you don't need to assign people as "friend" in order to express thoughts and share them with like-minded awesome people.