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
-
Everything in one method is ok as long as you are writing in a language tat foes not support methods, like old line number basic, or if the whole program fits on a page or if its a contest.
Outside of that it has never ever been an acceptable practice.
Methods was introduced for a reason a looong time ago ;) -
@Arhicy the advantage I have is management is in my side. As the team hasn’t really been lead in the past .. pretty much was the wild Wild West do what you want.. and in the last year I’ve turned the team around or atleast pulled the team into the modern age.. it’s just that one guy who’s stubborn..: it will come down to him being given an ultimatum by upper management.. we’re moving forward and he’s either jumping aboard or being left behind.. I run a tight ship lol
-
@Voxera One of the first things I was taught when doing assembler in school, was how to simulate methods using jumps. If you wrote all your programs in one chunk you wouldn't have passed the class.
-
@HollowKitty exactly
-
@HollowKitty of cause, but its still not quite the same.
You can do similar things in line num basic with gosub.
And in assembly you do have the stack, but in basic with gosub there was no equivalent.
Except possibly data which was very rarely used.
I never thought clean architecture concepts and low complicity, maintainable, readable, robust style of software was going to be such a difficult concept to get across seasoned engineers on my team... You’d think they would understand how their current style isn’t portable, nor reusable, and a pain in the ass to maintain. Compared to what I was proposing.
I even walked them thru one of projects I rewrote.. and the biggest complaint was too many files to maintain.. coming from the guy who literally puts everything in main.c and almost the entire application in the main function....
Arguing with me telling me “main is the application... it’s where all the application code goes... if you don’t put your entire application in main.. then you are doing it wrong.. wtf else would main be for then..”....
Dude ... main is just the default entry point from the linker/startup assembly file... fucken name it bananas it will still work.. it’s just a god damn entry point.
Trying to reiterate to him to stop arrow head programming / enormous nested ifs is unacceptable...
Also trying to explain to him, his code is a good “get it working” first draft system.... but for production it should be refactored for maintainability.
Uggghhhh these “veteran” engineers think because nobody has challenged their ways their style is they proper style.... and don’t understand how their code doesn’t meet certain audit-able standards .
You’d also think the resent software audit would have shed some light..... noooo to them the auditor “doesn’t know what he’s talking about” ... BULLSHIT!
rant