Details
Joined devRant on 3/15/2023
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
-
It's an oldie, but 1 of my favs :
QA expert decides to go out and have some fun. He walk for a whle spots a random bar and gets inside. After a solid 10+ minutes just looking critically arrond he dicides to stay. Goes to the barplot and orders :
- One beer por favor!
- Here you go - says the barman and continues his job. The man drinks it up quickly and orders again :
- 3 more beers ahora mismo!
- Enjoy - says the barman while serving them.
a few moments later...
- Hey barman, last order and we can round the night up, what ya say?
- ok - simply replies the barman.
- -5 beers! -
Most of things I'm about to say are experienced by almost 99% of developers in Africa including my country so I'm going to make it a more general rant.
As an African developer, life is both exciting and frustrating at the same time. Some of the challenges that make life difficult for developers in Africa include:
1). Slow Internet Speed: The internet in Africa can be extremely slow and unreliable, making it frustrating to work on projects that require large file downloads. This is a serious challenge for freelance developers who work from home.
2). Unstable Electricity: Frequent power outages due to inadequate infrastructure, insufficient investment in energy production and distribution, and political instability makes it difficult for developers in Africa to work consistently. Most times I get frustrated because you can experience black out at anytime of the day which could last for hours to days automatically rendering you useless if you have no power backup generator at home.
3). Low Pay: While the opportunities for software developers in Africa are quite high, the salary is often disappointing. Many talented programmers end up seeking better opportunities overseas. In fact I quit my full-time job because of this reason.
4). Lack of Support for Tech Start-ups: There are few venture capital firms in Africa willing to invest in new ideas, which makes it difficult for tech start-ups to get off the ground. It's just sad, you can have an idea and just die with it.
So in summary, it's not a walk in the park to be a developer in Africa, but despite all of that I am glad to be a part of the African journey, having the opportunity to had work at a tech agency firm on various projects ranging from healthcare to finance, I find it rewarding to know that my work has contributed to a better future for my continent. 🤞6 -
And now, behold: a cat, warning: long loading time since I uploaded the entire fbx file. I'm gonna trim it later.
https://txstc55.github.io/cat/
2 -
"Debugging is similar to being a detective in a murder mystery when you are also the killer and are unsure of whether you are resolving the case or hiding your traces!!".
But seriously, why does debugging have to be so challenging at times? It appears as though the code is attempting to trick us in some way. And let's not even talk about those mysterious error messages that have no meaning at all. Is a bit more explanation necessary, code? Give us a break, please!2 -
Let's say you're working on a web application, and you notice that one of the pages is not displaying the correct data. You investigate further and realize that the data is being retrieved from an API endpoint, but for some reason, the API is returning the wrong data.
You start looking into the code that calls the API and notice that it's passing in the correct parameters, so you dig deeper into the API code itself. After hours of poring over the code, you finally discover that the bug is caused by a typo in the database query that the API is using to retrieve the data.
You fix the typo and think the problem is solved, but then you realize that the data is still not displaying correctly on the page. After even more investigation, you discover that the bug is actually being caused by a caching issue on the client side.
At this point, you're feeling incredibly frustrated and overwhelmed. You've spent hours trying to track down this bug, and it feels like every time you think you've found the root cause, another issue pops up. This is just one example of the many challenges that developers face on a daily basis.6 -
The people saying that ChatGPT will replace programmers are the same ones that thought as a kid that math was useless because you have calculators8
-
I hate sales people. I get physical urges of puking when i see or talk to them. Because no matter what you say all i hear is "give me your money"3
-
Few years ago as a junior android dev with couple years of self taught experience of working in startups I submitted a simple android app assignment for a junior android dev role. Assignment had only like 8 requirements so I followed them to the letter. That didn't end well.
App was simple just 3 screens. Login screen with username and password input fields, login button.
Had to call a login endpoint after login button was clicked, redirecting to home screen, calling items endpoint, displaying a list of items and when an item was clicked passing item data and redirect to item details screen.
Needless to say big swinging dick senior was not impressed. UI was not perfect, I forgot to display a loading animation when fetching data, didnt handle back button properly.
I agreed with some points but other comments were clearly just nitpicking: his preferred variable naming conventions, his opinions on architecture that was not up to his standard (official google arch at the time was not up to his standard).
He also was mad that app wasn't prepared for release to googleplay (another out of the ass requirement). Like I would prepare a 3 screen app for prod release that he will forget ever existed after 20min of his review.
Lots more of nitpicking, encapsulation this encapsulation that, omg now hes shocked that there are a few warnings after the project is built.
Regardless my self confidence was destroyed at that point and after few more negative experiences I dropped android dev alltogether for a couple years and switched to game dev.
After game dev ran its course I went back to android dev and found a supportive place where I could grow.
Looking back, they were actually hiring atleast a mid level for a junior position but I was grilled as a senior. The guy literally didnt wrote any single positive thing in that review about my code even tho my senior peers said my project was decent back then, its just that I didnt handle a few edge cases and that's all.
I looked up the guy in linkedin, turns out hes a uni dropout who posts all books that he red about software dev in his education section of his linkedin profile. Found a bunch of other narcissistic stuff on his profile. Guy was a fucking idiot. Even if I worked under him it would have probably sucked.
Learned some important lessons I guess. Always get a second, 3rd and 4th opinion and dont take criticism too seriously. Always check what kind of person is providing feedback.4 -
I like the open exclusive-ness trait that DevRant has.
It's technically open for anyone to join, but only a certain type of people will visit on a regular basis, giving this platform a sense of exclusivity.6 -
You are all beautiful people. Thank you for your unique mix of talents to make for a variety filled platform. I have come to appreciate different parts of the industry due to exposure on this site. It is great to joke around and just "be" here. No pressure, just banter and the occasional fighting. I think this is a good thing. I hope this place grows.
Remember, you are important and awesome in your own way.4
