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
Search - "dogma"
-
Person: "I'm using Ubuntu. It's my first time using Linux. It looks pretty nice and it works for me."
People: "Eww. Loser. Ubuntu sucks! I'm a Linux god."
Person: "I think PHP is fine and has improved."
People: "Yikes. Don't use PHP. Everyone hates it."
Person: "I like using Angular. It gets the Job done."
People: "Boo! Use React. Angular sucks!"
So there you go, kids. If you wanna stay cool, listen to other people's opinion and their way of thinking. No need to really immerse and try out the tools that seem to work for you.16 -
Disclaimer: I apologise in advance for those tired of language wars, if it bugs you that much just skip this rant.
"C++ is better than C"
An accepted truth. OO is better than Procedural, C++ is an upgrade from C, it fixed all the problems.
End of.
Except - when it comes to actual evidence, empirical studies have shown that there are no productivity gains with C++ vs C.
This bugs me the most because it's such a fringe view, OO has dominated industry purely by dogma, alternative programming paradigms are just simply ignored because: "OO is best. End of."
https://researchgate.net/profile/...22 -
@Owenvii made a post over at (https://devrant.com/rants/2359774/...) and I want to write a proper response.
The biggest thing you have to look out for as a new dev is the jobs which you accept to begin with.
This isn't minimum wage no more, this is "big league", well, maybe not apple or google big league, but it's not $9.25 an hour either.
Basically you don't want to work anywhere where 1. your labor will be treated as a highly disposable commodity. 2. where the hiring manager doesn't know how to do the job themselves.
The best thing you can do is, if you're new, and just breaking through (and even if you're not), is ask them common questions and problems/solutions that crop up doing the work. If they can answer intelligently that tells you the company values competence (maybe), enough to put someone in place who will know ability from bullshit, merit from mediocrity, and who understands the process of progressing from junior dev to a more involved role.
It also means they are incentivized to hire people who know what they're doing because the training cost of new hires is lowered when they hire people who are actually competent or capable of learning.
Remember, an interview isn't just them learning about you, it's your opportunity to interview *them* and boy, you'll be making a BIG mistake if you don't.
Ideally you want them to ask you to pair program a problem. If your solution is better than theirs then they aren't sending their best to do interviews, and it tells you the company doesn't fire incompetents. The interviewers response can tell you a lot too, if they critique your work, or suggest improvements, and especially if they explain their thinking, that is an amazing response to look for, it says the company values mentorship and *actual* teamwork (not the corporate lingo-bingo 'teamwork' that we sometimes see idolized on posters like so much common dogma).
Most importantly, get them to talk about their work and their team. If they're a professional, it'll be really difficult to pry anything negative about their co-workers out of them, but if they're loose-lipped and gossipy thats a VERY bad sign, regardless of what they have to say.
Ask to take a tour and do a meet n' greet of who you will be working with. If they say no, then it's no thank you to a job offer. You want to take every opportunity to get to know everyone there, everyone you'll be working with, as much as possible--because you'll be spending a LOT of time with these people and you want to rule out any place that employs 'unfireable' toxic assholes, sociopath executives, manipulative ladder climbing narcissists, and vicious misery-loving psychopathic coworkers as quick as possible. This isn't just one warning flag to look out for, it's the essential one. You're looking for the proper *workplace culture*, not the cheesy startup phrase of "workplace culture", but the actual attitudes of the team and the interpersonal dynamics.
Life is really short, and a heart attack at 25 from dipshit coworkers and workplace grief can and will destroy your health, if not your sanity, the older you get.
Trust and believe me when I say no paycheck is too grand to deal with some useless, smarmy, manipulative, or borderline motherfuckers at work constantly. You'll regret it if you do. Don't do it. Do you fucking do it. Just don't.
Take my words to heart and be weary of easy job offers. I'm not saying don't take a good offer that lands in your lap, I AM saying do some investigating and due diligence or the consequences are on you.1 -
How many of you feel you learn something on the job?
As for myself, I learn much more from books than sitting day in, day out at work, doing more or less of the same things.
To me, this whole trial-and-error way of 'learning' is not really learning. I don't subscribe to this dogma. I don't 'learn' by messing up and fixing something. I need a full specification of why something works, when and how. I'm not satisfied by just being a code plumber.
This, next to the fact that most jobs in small startups don't provide a budget for you to expand your knowledge.5 -
What do you think of pair programming?
Does it automatically allow for (much) higher quality code?
Is there truth and practicality in it?
Have you applied this in your company?
I think it's a bit of a dogma and its benefits depend on whom you're working with. Sometimes two incompatible people will waste each other's time, or a person who works much better alone will instead work in a worse manner.
I know for a fact there are colleagues (including myself) who can't stand it when someone else is looking at their screen.
source:
http://extremeprogramming.org/rules...13 -
In my experience object oriented is very good for composing high level abstractions into a complete system. Functional is awesome for validation, parsing and massaging data in any way and imperative is tithe most useful paradigm to handle side effect dependent code that either manipulate the computers state ( read/write) or communicate with external systems.
The people acting as if one of them is the one true way are misleading you.3 -
Nothing is more pointless, or wastes more brain energy, than arguing about whether or not something is "RESTful"2
-
!dev at all, but I just had to share it with someone. I know I'm quite late to the party here, but hey, I might not be the only one walking in darkness here...
Anyway! I just came over this cover of Sound of Silence by Disturbed. It fucking floored me! How the fuck is a man supposed to keep up his dogma induced stonewall when someone creates something so fucking beautiful? This cover is truly an epic recording of what was already an amazing song, but not something you'd play on repeat.
Add some metal to the mix and man...! I can't hear it enough... Drives the wife crazy :D
Enjoy!
https://youtu.be/u9Dg-g7t2l4
PS! Do watch the video, crank up the volume and relax. Oh, and use real speakers or a decent headset at least somewhat capable of tickling your spine :P -
Dragon’s Dogma 2 is Elden Ring lite and i fucking LOVE it! It’s Elden ring combined with that classic action rpg vibe I grew up with! And the climb the enemy feature is damn SICK (nothing screams being a fucking man like climbing the back of a huge beast and plunging a sword down its skull)
Here’s to sticking a sword up an ogre’s ass!4 -
It annoys me immensely when I struggle with myself, criticizing my own lack of knowledge in certain areas and my colleagues say: "You'll learn by doing". No, I won't, that's a foolish dogma.
I won't and I have never learned by 'doing'. The best results I've obtained have been through understanding every last bit of what's under the hood of a particular functionality. I'm not going to understand the white box by constantly probing the black box, it's just unsatisfactory and insufficient information. It's even dangerous to base yourself on the black box results because you often might get false positives.
I got through university by massive multilateral sensory focus: kinesthetic (writing things down), auditory (listening to the professor), visual (observing graphs and models of the material taught), conscious (mentalizing it all and interlinking information so that later it's accessible from long-term memory). I can confirm this is necessary for the brain because a Neurologist once told me just that.
At least for me, I had the most horrible grades (D's and F's) in freshman year with the 'learn by doing' method and the best grades (A, A+) with the multi-sensory method in later years as I matured my studying methods. In fact, with that method I've continuously outsmarted other people who had 10 years more experience than me ('experts', 'consultants',..) but they preferred to stay in the ignorant 'bro zone' rather than learning things properly. Even worse, the day they arrived on the scene, they completely broke the production environment and messed it up for the whole team. I felt like banging my head on my desk. It just makes me disappointed in the system.
If you follow popular method, you'll soon find yourself in the same problems that arise from doing what everyone else does. What happens at that point? That's right, they have to call in someone who actually bothered learning things.10 -
I can see people who fight biological limitations and deny dogma from a mile distance. They shine from within.
If the immense work of creating a full map of pathological automatic thoughts is required to beat anxiety, I will do it just because it constitutes pure, conceptual beauty and the idea of reasoning beating primal biology. When I look in a mirror, I see myself shine.
There are no limitations to personal development other than laws of physics.1 -
Has anyone actually seen a monster take a shit in Dragons Dogma 2?? I found this after defeating a chimera9
-
FUCK wolves in dragons dogma 2, biggest pain in the ass next to harpies. I’m a fighter class and can’t reach them when they dodge my short ass sword