>No prototypes – always maintain constantly shippable code. Polish as you go
>Ensure that your program can always be run by your team, providing defaults upon load failure
>Keep your code absolutely simple. Keep looking at your functions and figure out how you can simplify further
>Spend as much time on tools as possible
>Use a superior development system than your target to develop
>Write your code for this program only, not for a future program. You’re going to be writing new code later because you’ll be smarter
>Encapsulate functionality to ensure design consistency. This minimizes mistakes and saves design time
>Try to code transparently. Tell your lead and peers exactly how you are going to solve your current task
>Programming is a creative art form based in logic. Every programmer is different
The Sup Forums Programming Manifesto
MAKE SURE YOUR LOGO IS THE BEST IT CAN BE
>Anybody that isn't using your language is an idiot and can't program
>Anybody that is using your language is using it wrong
nah
USE C
REEEEEEEEEEEEEEEEEEEE
no
write minimal software
write software with less lines of code
good code produces
- Fewer bugs
- Better performance
- Lower memory footprint
- Better maintainability
- Higher scalability
- Longer software lifetime
- Prompt delivery
Good code is subjective.
bump
>manifesto
NO! PROGRAMMERS MUST BE FREE AS IN FREEDOM!
...
I reject your communism
>2
maybe if you're a loon. But if you want your program to sell, try make it usable.
communism have failed
Pack it up, comrades.
small != simple
Simply use the Code of Conduct from Geek Feminism Wikia, it's already perfect as it is.
Respect for other people's choices is the most important thing in team work, everything else is superficial.
:O
Is this Kek's will?
based
exquisite
...
praise kek
SMITED
M
I
T
E
D
f2pbp
nice sexts