Details
-
AboutWeb Dev
-
SkillsPHP, JavaScript, HTML, CSS
-
LocationNairobi, Kenya
Joined devRant on 7/7/2016
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
-
*buys VPN*
*Installs VPN*
*Opens VPN*
*Sets VPN to france*
*Start receiving french ads*
Sure why not lol7 -
I work at a small company that uses very outdated coding approaches for their solutions.
About a year ago I went through our main application to improve performance and found quite a few areas that I could tackle such as using a dictionary data structure in place of (many) foreach loops that required to pull out a single object.
That specific change yielded a lot of improvement (you can only imagine) and the other developers wanted to learn the ways of dictionaries (because it was so revolutionary and new to them). I showed them many examples so that they could better understand this data structure.
Fast forward to a few months later, saw one of my coworker's code and noticed that they were using a dictionary... And iterating through each kvp similar to a foreach..... Wtf?!
P.S. that person's salary is much higher than mine :(
First time rant. Thanks for listening!10 -
Once upon a time, there was a coder named Dude. He started working at a company that told him they were innovative and that their code was glorious. This was a lie. He murdered everyone.
The End.7 -
Modern web developer Stater pack
1.Mac with 100 stickers on it
2.Love linux but never used it
3.Border 0px
4.Border radius 2.7px
5.sketch+adobe22 -
:-)
I think that "family guy" is telling me That is time to close netflix and read something......5 -
Best way to avoid procrastinating: the sooner it gets done, the sooner I no longer have to think about doing it. When I have a bunch of shit to do, I start with the things I like the least, and save the more enjoyable things for last.5
-
A repo on GitHub I'm maintaining has grown with 200k downloads / month since I started working on it a year ago. My recipe? I added an npm badge in the readme showing downloads / month and I responded to every issue and reviewed every PR. Now there's so much issues and PRs coming in that we had to add an extra maintainer, feels great! Teamwork, fuck yeah!
Not every PR got merged of course, but every single one of them got reviewed. Just being a good and friendly developer, giving back to the community that has given me so much. Some tips for you maintainers out there. If you have a popular project and no time there's always someone else who's willing to spend time on it, ask around and you will surely find someone else.6 -
Found my most ridiculous function ever, back from when I was first learning.
async Task Delay(int time)
{
await Task.Delay(time)
}1 -
If all you have is a hammer, everything looks like a nail!
This was something which my tech lead used to tell me when I was so obsessed with nosql databases a few years back. I would try to find problems to solve that has a use case for nosql databases or even try to convince me(I didn’t realise it back then) that I need to use nosql db for this new idea that I have, without really thinking deep enough whether the data in question is better represented using an sql schema or not.
Now, leading a team of young developers, I come across similar suggestions from few of my team members who just discovered this new and shiny tech and want to use it in production projects.
While I am not against new and shiny, it’s not a good practice to jump right in to it without exploring it deep enough or considering all the shortcomings. The most important question to ask is, whether some of the problems you are trying to solve can be solved with the current stack.
Modifying your stack requires more than just a week’s experience of playing around with the getting started guide and stack overflow replies. This is something which need to be carefully considered after taking inputs from the people who would be supporting it, that include operations, sysadmins and teams that are gonna interface with your stack indirectly.
I am not talking about delaying adoption by waiting for long list of approvals to get some thing that would bring immediate value, but a carefully orchestrated plan for why and how to migrate to a new stack.
Just because one of the tech giants made a move to a new stack and wrote about it in their engineering blog doesn’t mean that you need to make a switch in the same direction. Take a moment to analyse the possible reasons that motivated them to do it, ask yourself if your organisation is struggling with the exact same problems, observe how others facing the same issue are addressing it, and then make an informed decision.
Collect enough data to support your proposal.
Ask yourself again if you are the one holding the hammer.
If the answer is no, forge ahead!9 -
This happened in my first internship I was working for a small company. They had a knack of redefining policies at short notices.
The had this shitty time tracking site which was hosted internally.
We were working on client location for 25/30 days so we didn't have access to the time tracking site. And there comes a memo that everybody has to fill the time tracking or their salary will not be credited.
So when we reach office we hear this "News". We thought they would consider people on client location. But then on salary day we don't get any and are called into VP's office for a verbal lashing. We literally had to fight for two weeks for the salary.
Worst Experience Ever2 -
We had a manager that blind-sided the entire Team. During annual reviews, he gave everyone on the Team an unsatisfactory/not meeting expectations. Why? Because rather than rating us on the work we were being assigned, he rated us against what our job descriptions said, but you can't do work you don't have. Not once, during any of our monthly one on one reviews did he tell any of us that we weren't meeting standards. No one on the Team got a pay raise that year. But, karma. Several month later, the company decided to do a 360, which is where we get to rate our manager anonymously. We're still here; he's gone.4
-
Professor at Uni: "Missing a semicolon on yozr final exam could be a reason to fail that exam. Coding on paper is much better because that is what you will be doing on the job. "
Hate those written Java exams on paper.18 -
So I put a very strict eslint configuration to a 6 month old project
..
..
..
..
924 errors in 27 files
..
..
..
..
..
I removed eslint from the project8 -
First post.
So, I've been teaching myself front-end for about 7 months now, and I'm really enjoying it, especially the actual programming aspect of JS. I also just started a new job, nothing to do with development, that I expected to be extremely boring and unfulfilling, as it doesn't fulfill any of my interests, but it'll pay my rent and it has decent benefits. I'll be mostly working with excel.
Now, like I mentioned, I'm really new to the dev world, just a little infant really. I know enough to know that I don't know shit. So, I was surprised to learn today that you can program in excel with VBA. I know the language gets a good bit of hate on here, I did a search before posting, and while I haven't started to learn it just yet (I'm starting tonight) I'm excited about. Firstly, because I'll get to do coding for my job, something I'm interested in, and secondly, because if I can figure out how to automate part of what I do well enough that it's implemented with the rest of the team, then maybe I'll be rewarded, and I'd be able to put professional coding experience on a resume for when I try to find a better job.
I've really enjoyed reading all the rants. They've been entertaining and also educational sometimes.
tl;dr Discovered VBA and was actually excited about it6