Details
-
AboutI use computers...
-
SkillsLow level and high level programming experience.
Joined devRant on 9/13/2024
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
-
Got scammed on devrant by sketchy cryptocoin recovery services? Like a total dumb ass you clicked a sketchy link? Did you suffer temporary retardation and believed a scammer?
You may be entitled to public humiliation! Contact our services (totally not sketchy AF) and get doxxed, reposted, and made to look like a complete fool! (Javascript devs excluded, they suffer enough just existing.)
1-800-dumb-fuk wtfuthinking@dumbass.git4 -
It just hit me. If you wanna achieve something great you have to dream big. If you aim for something humble, you'll just get lost in the endless land of diminishing returns where you take forever to make little progress
If you aim high, you are naturally inclined to do big strides since you feel that there is still so much left to be done
Just a thought I had working on my engine3 -
New developers(5-6 years experience) these days are so pathetic. They dont have any sense of code review. All they want is to put their opinion out without giving any thought.
I had a PR for review today which contains mock specification to match a regular expression and return the corresponding response
The regular expression I put was
104000(02|06|20|48)
Now, this guy comes and puts a comment that we could "simplify" as 104000\d{2}
I replied, the ending digits are not contiguous. The specific pair of digits have to match for these mocks.
Then this guy replied, then we could simplify as 104(0{4}(2|6)l0{3}(20|48)).
I said, I cannot understand how that is simplification. Why do we need such a complex regex to match something very straight forward.
And the guy replied, we should be writing proper regexes, otherwise we could just specify everything explicitly.
I was like WTF man. You try deciphering this next week without taking at least a minute to know which values are matched.
Anyhow, another senior person approved my PR, and I merged it.12 -
I want to kidnap Sony's design team and have them produce headphone designs that I reject or approve until they can tell me what's wrong with their jack port placement.6
-
So, when hovering on that element in the bottom task bar in Windows 11, it shows those two icons (wifi and sound) grouped together.
Left click anywhere on that button and it opens the same menu.
But if you right click, now it suddenly depends if your cursor was on the one or on the other icon. It opens different menus!
Great UX! Good job, MS!13 -
There have been a "person accident" on the train track. It is closed. According to the newspaper, they are not aware of the health status of the person.
Yeaah, you do not survive a train accident. The dude's a goner11 -
Time spent on devrant:
50% trolling
25% challenging people's worldview aka trolling
15% making witty remarks, and more trolling
10% looking through my notifications to see wtf @Wisecrack said
<1% posting "quality" content14 -
Took a week off just to stop working because I’m burnt off, can’t help opening slack, it’s like muscle memory.
FML14 -
Can we please stop with the multiverse crap? Please, just stop.
I watched Deadpool & Wolverine yesterday and what a shitshow.
Logan was an excellent send-off to Wolverine. An excellent one.
It showed that Marvel can actually make good movies.
Why did Marvel have to ruin it?
The issue with multiverse plotlines is that nothing is ever serious, there are no stakes, nothing matters.
Anyone who dies can come back. Anything that happens can be reversed.
Just. Fucking. Stop.
One of my favourite franchises, Mortal Kombat, got ruined with MK1 multiverse story.
Played the game for about 30 minutes then deleted it. What a disappointment.
From now on, if a movie features multiverse or time travel crap, I ain't watching.26 -
Today we interviewed a _very_ good Angular1 Dev, by chance we showed him the forked ngRouter module we use, after some debate he explained that we were using it incorrectly.. I asked if he'd used it before to which he responded:
"Yeah, I'm the guy who built it"
😅27 -
*Now that's what I call a Hacker*
MOTHER OF ALL AUTOMATIONS
This seems a long post. but you will definitely +1 the post after reading this.
xxx: OK, so, our build engineer has left for another company. The dude was literally living inside the terminal. You know, that type of a guy who loves Vim, creates diagrams in Dot and writes wiki-posts in Markdown... If something - anything - requires more than 90 seconds of his time, he writes a script to automate that.
xxx: So we're sitting here, looking through his, uhm, "legacy"
xxx: You're gonna love this
xxx: smack-my-bitch-up.sh - sends a text message "late at work" to his wife (apparently). Automatically picks reasons from an array of strings, randomly. Runs inside a cron-job. The job fires if there are active SSH-sessions on the server after 9pm with his login.
xxx: kumar-asshole.sh - scans the inbox for emails from "Kumar" (a DBA at our clients). Looks for keywords like "help", "trouble", "sorry" etc. If keywords are found - the script SSHes into the clients server and rolls back the staging database to the latest backup. Then sends a reply "no worries mate, be careful next time".
xxx: hangover.sh - another cron-job that is set to specific dates. Sends automated emails like "not feeling well/gonna work from home" etc. Adds a random "reason" from another predefined array of strings. Fires if there are no interactive sessions on the server at 8:45am.
xxx: (and the oscar goes to) fuckingcoffee.sh - this one waits exactly 17 seconds (!), then opens an SSH session to our coffee-machine (we had no frikin idea the coffee machine is on the network, runs linux and has SSHD up and running) and sends some weird gibberish to it. Looks binary. Turns out this thing starts brewing a mid-sized half-caf latte and waits another 24 (!) seconds before pouring it into a cup. The timing is exactly how long it takes to walk to the machine from the dudes desk.
xxx: holy sh*t I'm keeping those
Credit: http://bit.ly/1jcTuTT
The bash scripts weren't bogus, you can find his scripts on the this github URL:
https://github.com/narkoz/...53 -
!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 young guy I work with burst into tears today, I had no idea what happened so I tried to comfort him and ask what was up.
It appears his main client had gone nuts with him because they wanted him to make an internet toolbar (think Ask.com) and he politely informed them toolbars doesn't really exist anymore and it wouldn't work on things like modern browsers or mobile devices.
Being given a polite but honest opinion was obviously something the client wasn't used to and knowing the guy was a young and fairly inexperienced, they started throwing very personal insults and asking him exactly what he knows about things (a lot more than them).
So being the big, bold, handsome senior developer I am, I immediately phoned the client back and told them to either come speak to me face-to-face and apologise to him in person or we'd terminate there contract with immediate effect. They're coming down tomorrow...
So part my rant, part a rant on behalf of a young developer who did nothing wrong and was treated like shit, I think we've all been there.
We'll see how this goes! Who the hell wants a toolbar anyway?!399 -
So I needed a break from all the straight computer logic for days... so i figured i had 2 options, argue with chatGPT or go back to a dating app.
I chose the latter.
Im ocd with notifs... i NEED the bubble to be gone.
Found this gem...
"Hey beautiful Sara ;) my names is James king it very nice 2 meet u wow u look like a angel that fall from heaven 😘u mind me of a rose because how beautiful you are am how beautiful the rose is am I the best guy on badoo that u would ever talk with on badoo I actually look for Friendship and relationship ;) how are u today am wyd"
So... because im curious, esp when it comes to perplexing linguistics... im def gonna ask if English is his 1st language.
Normally i can tell within a sentence or 2... even tend to know their native tongue by then... this one has me stumped.
Anyone wanna guess if hes a native English speaker???
Maybe ill make a modest prize poolif there's a few entrants.
(he has plenty of pics so ill be able to legally find out in a few min... but ill wait til i dont get a response for a week)
Ill probably make a script to strip out the auto-messages... replying with an auto ofc... and the mundane crap that shows they definitely didnt go beyond the pics.11 -
was looking up some code, won't say which, trying to find something, won't say what, and, heck, I need to find out who wrote and maintains this awesome piece of art. After a couple hours of stalking done, yep, that's how good it was, I finally found the author and guess what? They died two years ago, 24 years old. Dead. Gone. A little more stalking and the punchline was: suicide.
FUCK, I don't even know them but it makes me real sad. It seems this' an actual issue in our line of work24