Details
-
SkillsC# .NET, Java, Lua
-
LocationGermany, Bavaria
Joined devRant on 12/12/2017
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I'm a strong believer in the triple-A unit-test pattern: Arrange, Act and Assert
Anyone else that uses this for their tests? Do you see any cons to using this approach to writing tests? Are you using an alternative?11 -
Divorced Ruby (only thing she has is her beauty)
Married Java(powerful but hard to cope up with)
In love with Python (Powerful and beautiful)
Have a crush on Kotlin (She is something else, sadly she is Java's friend)
In an Affair with C# (Like java but easier to deal with)
😂😂
#Love gone wrong 😝
(Just a joke try to see the humor in it. Don't get offended 😂. Thank you. )10 -
Here's a true story about a "fight" between me and my project manager...
I've been working as a Frontend developer for nearly two years, managed to acquire a decent amount of knowledge, in some cases well above the rest of my coworkers, and one day I got into a bit of a disagreement with my project manager.
Basically he wanted me to copy/paste some feature from another project (needless to say, that... "thing" has more bugs than an ant farm), and against his orders I started doing that feature from scratch, to build a solid foundation from the very start.
I had a lengthy deadline to deliver that feature, they were expecting me to take some time to fix some of the bugs as well, but my idea was to make it bug-free from the moment the feature was released. Both my method and the one I should be copying worked the exact same, but mine was superior in every way, had no bugs, was scalable and upgradeable with little effort, there was no reason not to accept it.
We use scrum as our work methodology, so we have daily meetings. In one of those, the project manager asked me how was the progress on that new feature, and I told him I was just polishing up the code and integrating it with the rest of the project, to make sure everything was working properly. I still had a full day left before the deadline set for that feature, and I was expecting to take about half an hour to finish up a couple lines of code and test everything, no issues so far...
But then he exploded, and demanded to know why wasn't I copying the code from the other project, to which I answered "because this way things will work better".
Right after he said that the feature was working on the other project, copying and pasting it should take a few minutes to do and maybe a couple of extra hours to fix any issues that might have appeared...
The problem here is, the other project was made by trainees, I honestly can't navigate through 3 pages without bumping into an average of 2 errors per page, I was placed into this new project because they know I do quality code, and they wanted this project to be properly made, unlike the previous one, so I was baffled when he said that he preferred me to copy code instead of doing "good" code...
My next reply was "just because something has been made and is working that doesn't mean that it has been properly made nor will work as it should, I could save a few hours copying code (except I wouldn't save any, it would take me more time to adapt the code than to do it from scratch) but then I'll be wasting weeks of work because of new bugs that will be reported over time, because trust me, they will appear... "
I told him this in a very calm manner, but everybody in the meeting room paused and started staring at me, not many dare challenge that specific project manager, and I had just done that...
After a few seconds of silence the PM finally said... "look, if you manage to finish your task inside the set deadline I'll forget we ever had this conversation, but I'll leave a note on my book, just in case..."
I finished that task in about 30 mins, as expected, still had 7 hours till deadline, and I completely forgot about that feature until now because it has never given any issues whatsoever, and is now being used for other projects as well.
It was one of my proudest/rage inducing moments in this project, and honestly, I think I have hit my PM with a very big white glove because some weeks after this event the CEO himself came to the whole team to congratulate us on the outstanding work being made so far, in a project that acted against the PM's orders 90% of the time.11 -
Casually Client Team Asked A Developer Team,
What is your favorite game?
**Blame Game**, One of the junior developer murmured. -
Yeeeeeeeee! My granddaughter yelled up to me, "Grandpa, I'm programming!" She was doing some kid code game thing. Ten years old. I can hope, can't I? 😁14
-
Networking Professor: Alright, how many of you disagree with the way Google collects and uses data?
*basically everyone in the lecture hall raises their hands*
Professor: Okay, now if you were offered a job at Google, how many of you would still take it?
*everyone raises their hands.*22 -
Best quotes from IT teacher:
- "C# is a language to program your IDE."
- "C# is a language for beginners, and is not really used in production."
- "We won't use Python to learn programming, because Python is a very old, slow and useless language, and is not really used anymore."
- "Yeah, your algorithm is fantastic, but you wrote 'The answer is: ' instead of 'Answer: ', so it's just a B."
- One of my classmates was bored and opened Notepad++, and when the teacher saw it, she said "I have been teaching programming for years, but I've never seen this program, what do you use it for?"
I feel so lucky that I have started learning programming years before at home, I just couldn't start if I had to learn this way.37 -
Client: Please remove the address inputs from the inquiry form. Our marketing strategist said that more people will fill out the form if there are less input fields.
Me: But you are required by law to include the address in the generated inquiry PDFs!
Client: Can you remove the fields and still include the address in the PDF somehow?
Me: No. How would the website know the users address without asking for it.
Client: Okay. Wait! Can we change the form to just one large input where the user has to enter everything at once? That is even less inputs so more users would do it, right?
Me:...6 -
Drop brother off at a new years party, where he will be until sunrise partying with friends.
Me: Have fun!
Me: *drives back home, grabs laptop and opens up IntelliJ*
Me: Let the finger dance begin!
Have I mentioned I hate parties?4 -
My company contracted a 3rd party to do an internal system for us...
We only knew about it when it was almost done and we got the code... Oooooo boy.... What a fucking shit they did and got paid for...
They have a encryptPassword() and decryptPassword() functions...
What they do you may ask?
Well...
Encrypt: for loop that reverse the string and base64 it 5 times...
Decrypt: the opposite...
That's how they store passwords....
Our intern snapped at a company meeting when they where talking about maintaining it 😂😂22 -
A few days ago, I finally switched from Win 10 to Linux. Now, I see an open source world of customization, free of any bloatware or BSOD. And it feels great ❤️ ❤️ ❤️33
-
I was activating virtualenv in powershell when my younger brother came in.
Me: *all nervous* please don't think I'm hacking or trying to set off a bomb. (He always thinks I'm hacking and tells on me.)
Brother: *silent*
Me: *even more nervous* I don't want my laptop to get taken away. Don't tell on me and say I'm hacking, because I'm not.
Brother: Oh, I know you're not hacking this time.
Me: You do? *relieved.*
Brother: Yeah, because this time it's a blue background, not a black one.
Me: Oh, haha. So you're only scared of things such as these? *opens CMD and Git Bash* you know, just because it's dark themed, doesn't mean it's malicious. Besides it—
Brother: oooOooOh! You're hacking again! I'm telling on you!
*Note to self: Never use dark theme in front of the ignorant again.)43 -
click click...
*reload*
_________________
| |
| This will be wra|
| |
|_________________|
hm.....
ah...
*hits ctrl+s*
*smiling*
*reloads*
_________________
| |
| This will be wra|
| |
|_________________|
what the f..
..
..
hm....
hm....
aha
ctrl+alt+t
*confidentiality*
sudo sublime /opt/htdocs/learning_css/wrapping_text.html
********
o.O but my code ....it's here.....but why wasn't it showing....
*just to be safe*
ctrl+s
*reload*
_________________
| |
| This will be wra|
| |
|_________________|
meh..... what was I thinking
*wastes time restarting xampp*
*searches CSS everywhere*
*steals working code*
*eyes red as hell*
*it's 3 am*
*after 1hr*
*accidentally reloads*
_________________
| |
| This will be |
| wrapped |
|_________________|
o.O
*blinking in confusion*
what the .... how did it work....
I changed nothing.....
*realises*19 -
!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!221 -
A few weeks ago at infosec lab in college
Me: so I wrote the RSA code but it's in python I hope that's ok (prof usually gets butthurt if he feels students know something more than him)
Prof: yeah, that's fine. Is it working?
Me: yeah, *shows him the code and then runs it* here
Prof: why is it generating such big ciphertext?
Me: because I'm using big prime numbers...?
Prof: why are you using big prime numbers? I asked you to use 11, 13 or 17
Me: but that's when we're solving and calculating this manually, over here we can supply proper prime numbers...
Prof: no this is not good, it shouldn't create such big ciphertext
Me: *what in the shitting hell?* Ok....but the plaintext is also kinda big (plaintext:"this is a msg")
Prof: still, ciphertext shows more characters!
Me: *yeah no fucking shit, this isn't some mono/poly-alphabetic algorithm* ok...but I do not control the length of the ciphertext...? I only supply the prime numbers and this is what it gives me...? Also the code is working fine, i don't think there's any issue with the code but you can check it if there are any logic errors...
Prof: *stares at the screen like it just smacked his mom's ass* fine
Me: *FML*12