Details
-
SkillsPython, Rust, TypeScript, AWS
-
LocationMG, Brazil
-
Github
Joined devRant on 5/28/2021
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 work for a company known for its unbelievable perks and benefits. Every time a job opens up, we get thousands of applications.
Candidates are becoming increasingly aggressive to stand out. Hundreds of them (literally) have purchased Facebook ads or LinkedIn promoted posts to get their information in front of current employees.
Others have taken to outright stalking our employees. I freelance occasionally and have a separate website for my freelance business. I receive dozens of calls and emails to my freelance number and email account daily from people who want to “chat about the open position.”
My husband — who has a different last name — runs a small retail shop. He’s had people come into his store and tell him that they did internet sleuthing and found out he was married to an employee of my company, and would he please pass on their resume?
I expect to get these messages on my LinkedIn or company email, but am I wrong in thinking that stalking me out and trying to contact me via personal contact info (or my husband) is way out of line?
Is there a way to sharply tell them that this is not okay? Normally, I just don’t respond, but I have to turn my phone off or it rings all day and it’s really annoying. Would it look weird to put a message on my freelance website that says do not contact me about Company X jobs?
My company is aware of this problem, and has said to forward the names of aggressive or alarming candidates their way to remove them from consideration, but it’s so common, I’m thinking this is a product of being told that if they just showed GUMPTION, they’d get the job. I feel bad for them, but it’s also creeping me out.16 -
So my last rant was regarding a piece of code I found while clearing up an app. Here's the newest edition... a recent migration I found... a class within a migration creating records, this is not what migrations are for haha you don't add data using migrations jeez help me.
8 -
How to open source 101:
1. Have GitHub repo
2. Install a stale-and-auto-close bot
3. Never respond to issues
4. Have a project so good it has no open issues
Why?!5 -
When you send your stuck coworker a stack-overflow link and he copies the code from the question instead of one of the answers8
-
Hello, I just want to let you know I'm working on a 15 year old product and it is currently in production.
It uses Angular.js and one of the earliest versions of React.js. I cannot use ES6, we don't have Babel, no JSX syntax, no CSS preprocessor. No webpack.
I must support browser since IE6 with an ES3 syntax. (luckily I got some some polyfills for an ES5 syntax)
When I build a component I have to call React.createClass and React.createElement.
The render() function is basically a nested pile of React.createElement.
There is no documentation for this product, no tests, no anything.
I had to reverse engineer it in order to understand how it works.
The code base uses mixed programming styles and naming conventions, plus thousands of little js files.
Oh and obviously no hot reload, every time I make a change I have to restart everything.
Please, send help.
I'm in danger.
Sincerely,
An underpaid developer
....
I'm not crying, you are crying...19 -
CTO hired mid-level full-stack developer for really complex product we’re building.
Here’s the funny part - he has 2 YEO building on top of freelance dev. code base’s on wordpress… Just fucking yesterday he told me, that Angular 10 framework is simillar to Jquery. Fucking dipshit, his code is so fucking bad it looks like italian sausage made out of spaghetti.
Not sure if I hate him more than ours truly cheapest CTO or him for being ridiculously incompetent and arrogant young asshole.
I’m in charge of him.
Help me.10 -
User:
I wish I could build an app like XYZ that is so cool.🥺🥺
XYZ Developer:
I wish I could build an SDK like Agora.io that is so cool.😣😣
Developer at Agora.io:
I wish I could build CDN like Akamai. That is so cool.🤔🤔
Developer at Akamai:
I wish I could have layed Internet as a concept. That is so cool.😢
Conclusion: Don't disparage yourself as a Developer. Sometimes, we should Appreciate what we have build rather than what we wish to build.
Be proud of the Product "X" you are building.
Just look around, you will find a person wishing to build a product like "X".🤗
#developer #motivation #developers #agora #motivation9 -
Not only Synology's REST API documentation is outdated, but I have to deal with this.
Let alone the fact that login in a GET request where username and password are passed as query string in URL.
8 -
Developer: We have a problem.
Manager: Remember, there are no such things as problems, only opportunities.
Developer: Well then, we have a DDoS opportunity.52 -
"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"
So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.
First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.
So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.
Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?
I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.
Did you run the code I gave you to do this update?
"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"
So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.
More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!
I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.
And this, my friends, is the part I will never forget.
"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."
You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!
"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."
I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.
So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.
You just cannot make this kind of stuff up.105 -
!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
