Details
-
AboutSoftware Engineer
Joined devRant on 9/19/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
-
Ok c++ professionals out there, I need your opinion on this:
I've only written c++ as a hobby and never in a professional capacity. That other day I noticed that we have a new c++ de developer at the office of which my first impression wasn't the greatest. He started off with complaining about having to help people out a lot (which is very odd as he was brought in to support one of our other developers who isn't as well versed in c++). This triggered me slightly and I decided to look into some of the PRs this guy was reviewing (to see what kind of stuff he had to support with and if it warranted his complaints).
It turns out it was the usual beginner mistakes of overusing raw pointers/deletes and things like not using various other STL containers. I noticed a couple of other issues in the PR that I thought should be addressed early in the projects life cycle, such as perhaps introduce a PCH as a lot of system header includes we're sprinkled everywhere to which our new c++ developer replies "what is pch?". I of course reply what it is and it's use, but I still get the impression that he's never heard of this concept. He also had opinions that we should always use shared_ptr as both return and argument types for any public api method that returns or takes a pointer. This is a real-time audio app, so I countered that with "maybe it's not always a good idea as it will introduce overhead due to the number of times certain methods are called and also might introduce ABI compability issues as its a public api.". Essentially my point was "let's be pragmatic and not religiously enforce certain things".
Does this sound alarming to any of you professional c++ developers or am I just being silly here?9 -
My girlfriend knows what a coder needs when it’s their birthday. Lucky to have her. Walked into my room and it was set up like this.51
-
If I have headphones in
and I'm intentionally away from everyone
and it looks like I'm working
and you want to talk to me
Here's some advice:
DON'T FUCKING TALK TO ME.
If you're curious why, I've compiled a list of points:
1) DON'T
2) FUCKING
3) TALK
4) TO
5) ME
Also, see Fig. 1 below:
(Fig. 1)
| DONT
| FUCKING
|
| TALK
| TO
|
| ME
---------------------------------------
Don't fucking talk to me!26 -
Can someone get an excerpt from the SO user db and diff it against the DevRant user db and compile a do-not-hire list of the ones that are only on SO?
And yes, I was recently triggered by a SO elitist.
This also assumes all the nice SO members are members of DevRant, which I think is fairly accurate.2 -
I hate it when people dislike things because it’s cool.
“PHP is terrible,” they say.
Yeah! If it was any good then most websites on the Internet would be coded in it... oh wait.
“Nickelback suck,” they say.
Of course. That’s why they’ve never been able to make any money off their “terrible” music. Oops. Wrong again.
What other things are “cool” to hate just because people say so?39 -
CS Professor: “What M word is the black hole to all productivity?”
Student: “Management”
CS Professor: “Was going to say meetings but that’s better”16 -
I wanted to post a note on devRant community etiquette and rule-breaking behavior we’ve been seeing lately to make clear it will not be tolerated. This is pretty much a rehash of this rant, https://devrant.com/rants/609739/... and also our official rules which I highly encourage people to read: https://devrant.com/rules
I’ve noticed an influx of a select group of members, mostly older users, expressing a distain towards other users or declaring content they dislike “shouldn’t be posted”, “please stop”, etc. If you find yourself about to post that, as per our rules, please don’t. It blatantly violates our rules and we are going to start cracking down on it much more. Whether you have 30k+ points or 10, we will apply the rules fairly to everyone and not give breaks to specific people, which admittedly I’ve done in the past.
If we see this behavior in rants/comments first we will give a warning (and the rant/comment will be deleted) and the next offense is a ban.
A valid question (even though I’ve answered it before) might be why does this need to be a rule? Simply put, it’s a rule for a number of reasons: posts like described try to inflict one’s will upon the entire community (even though we have a Democrat voting process...), they create confusion (almost every time they try to sound official, ex. “Stop doing this”), and beyond those two main reasons, they literally accomplish nothing because they offer no constructive methods of achieving what’s being requested, and only a fraction of the community will actually see it.
Here’s an example of what’s not allowed and what is allowed:
- Allowed: posting an issue on our GitHub issue tracker saying “I really dislike seeing this type of rant in my algo feed, here’s some ideas I have to improve the algo and add more personalization so I can see what I want.”
- Allowed: posting on GitHub issue tracker: “I found this awesome image similarly algo that I think can improve the ‘repost check feature’ - you guys should check it out and see if it might be good”
- Not allowed: “Omg stop shitposting windows update rants and Linux rants I hate them. Go post this type of rant because that’s what everyone really wants to see.”
One is constructive an the other is merely an opinion expressed as an enforcement of a self-made rule on the community and tries to tell other people how they should use devRant.
I cringe when people tell others how to use devRant because without fail when I see those posts, I go through that person’s rant/comment history and I nearly always see them using devRant in some kind of way I disagree with or isn’t exactly what I like to see. But that’s OK. I understand I’m not going to enjoy everything posted and I’m also not going to agree with everything posted. But I think it’s fair for those same people to then lecture on what isn’t appropriate to post on devRant, and it’s even more silly when their posts are sometimes irrelevant to development and the posts they are complaining about are relevant.
In the end, based on the large majority of feedback we get, we want to make devRant a place where everyone feels comfortable expressing themselves and doesn’t have to think about possibly getting ridiculed every time they post and that don’t have people trying to dictate what kind of ideas they are allowed to post. We also realize there’s types of content people don’t enjoy, but telling others not to post it is not the solution. We will soon be launching post type filters that will make filtering rants by post type possible.
Please let me know if you have any questions and thanks for reading.64 -
As a long-time iPhone user, I am really sorry to say it but I think Apple has completed their transition to being a company that is incompetent when it comes to software development and software development processes.
I’ve grown tired of hearing some developers tell me about Apple’s scale and how software development is hard and how bugs should be expected. All of those are true, but like most rules of law, incompetence and gross negligence trumps all of that.
I’m writing this because of the telugu “bug”/massive, massive security issue in iOS 11.2.5. I personally think it’s one of the worst security issues in the history of modern devices/software in terms of its ease of exploitation, vast reach, and devastating impact if used strategically. But, as a software developer, I would have been able to see past all of that, but Apple has shown their true incompetence on this issue and this isn’t about a bug.
It’s about a company that has a catastrophic bug in their desktop and mobile platforms and haven’t been able to, or cared to, patch it in the 3 or so days it’s been known about. It’s about a company, who as of a view days ago, hasn’t followed the basic software development process of removing an update (11.2.5) that was found to be flawed and broken. Bugs happen, but that kind of incompetence is cultural and isn’t a mistake and it certainly isn’t something that people should try to justify.
This has also shown Apple’s gross incompetence in terms of software QA. This isn’t the first time a non-standard character has crashed iOS. Why would a competent software company implement a step in their QA, after the previous incident(s), to specifically test for issues like this? While Android has its issues too and I know some here don’t like Google, no one can deny that Google at least has a solid and far superior QA process compared to Apple.
Why am I writing this? Because I’m fed up. Apple has completely lost its way. devRant was inaccessible to iOS users a couple of times because of this bug and I know many, many other apps and websites that feature user-generated content experienced the same thing. It’s catastrophic. Many times we get sidetracked and really into security issues, like meltdown/spectre that are exponentially harder to take advantage of than this one. This issue can be exploited by a 3 year old. I bet no one can produce a case where a security issue was this exploitable yet this ignored on a whole.
Alas, here we are, days later, and the incompetent leadership at Apple has still not patched one of the worst security bugs the world has ever seen.81 -
I have a request for anyone that manages a project.
Please don't reschedule a demo to be earlier than the original date without talking to the developers(s) first.
That is all. Thank you.2 -
A devDuck update!
Hey everyone,
First off, thank you to everyone who has purchased a devDuck (or a bunch!) and thanks to all who have given us feedback. @trogus and I are thrilled at the incredible response these ducks have gotten. If you haven’t seen them yet, you can check them out at https://devDucks.com or the devRant Swag Shop (https://swag.devrant.io).
We are trying to process all of the orders as quickly as possible and our goal is to have all current orders out by the middle of this coming week. Many orders have already shipped, but if yours hasn’t, rest assured it will very soon!
If you ordered a Java devDuck or cape, your order might be delayed a bit until the middle of this coming week because Java seems to be a heavily-demanded cape and we needed to get the material shipped in to make more of that, specifically.
So far we’ve gotten some awesome feedback from the community. A short list of possible future additions based on what’s been requested: Go devDuck, Kotlin devDuck, Perl devDuck, Android devDuck, and possibly some devDuck accessories like little hats, sunglasses, headphones, etc. If you have any other ideas just let us know:)
Lastly, please know that even with the launch of devDucks, we remain extremely committed to the devRant product and we have some very exciting big devRant features coming very soon.
Thanks again everyone!28 -
Big congrats to @AlexDeLarge for being the first devRant member to hit 50,000 ++!
A pretty awesome accomplishment highlighting great contributions and content.71 -
Brainwashed Oracle HR Associate: So tell me, why do you want to work here at Oracle?
Applicant (that loves Apache Struts 1.2.4 and WebDav): It would be an honor to be a part of this great conspiracy and sell your products to mid-level project leaders that should not take tech stack decisions.
Brainwashed Oracle HR Associate:
Welcome aboard!3 -
Thank you dear mr. boss for fucking up our master branch by adding local changes to a 2 months outdated master branch (250 FUCKING COMMITS BEHIND), pull the remote and then just push without resolving any conflicts!!!1!!!
But thank you so much for sending me an email at 10pm asking me to resolve the conflicts.
It is 3 in the morning and it took 1 hour to get it clean.
Sometimes I want to break some necks...9 -
Get into bed.
Gets all comfy.
About to drift off.
Realizes solution for the problem I have spent all week on.
Now wide awake.
Guess who's not sleeping tonight!17