@LordMordred what's so difficult about coding
@LordMordred what patience lol it's like writting in english just more efficient
fn main() {
if(say(you).so) { println!("It's better than english"); }
}
@FrailLeaf @LordMordred that it's a more efficient way to communicate? Why else do you think that computers are so fast these days :p
.. And like learning things like a rust is just reading https://doc.rust-lang.org/book and understanding the datatypes and primitives
@FrailLeaf @LordMordred and like if you have problems understanding something then join a community and ask https://www.rust-lang.org/community
They will help you with everything rust-related and teach you
@FrailLeaf @LordMordred and like worst case scenario ask me for help :P
I already addressed the environment namely using reproducible environments e.g. Gitpod, GNU Guix, Rustup.rs etc..
What is even a design pattern?
You coordinate with team through the code namely:
1. Using tags
2. in-code documentation
3. Discussing your design in merge request
> it gets really easy to write sloppy code that you have to reinterpret 3 months from now.
Bad code ain't a problem as long as it's documented, but good practices should be followed.
@bwk @FrailLeaf @LordMordred that's bullshit majority of programming jobs require documentation and even tests assuming that they hire you to work on an open-source projects
none really gives a damn on proprietary development i agree with that.
> have you actually been hired to work on free software full time?
Yes i have 14 years of experience with Free Software and Open-Source development.
> Everyone I know personally gets paid to work on proprietary software.
Find people that work on open-source then :p Proprietary in general pays less and is more infuriating
> Besides, when I have had to use free software on the job their tests have all been broken and poorly documented.
Free Software is statistically more robust and secure so either you were using a solution that did not yet reached Gold or your system is hugged up.
Documentation agree that not everyone makes it as understandable as it should thus why i prefer rust that generates the docs from the code.
But there is lot of people who are not good at programming, but they are improving the documentation for that reason.
i'm not arguing for projects you work on because you're having fun, its about the perspective of why people give up, that is the point you're missing. Shit workplaces and improper env setups are the reason. You cannot expect people in here to be industrious & skillful, your solutions will be ignored.
@FrailLeaf @LordMordred @bwk Good programming practices are not important in open-source development.
The documentation and making the code understandable by the next guy is as if your abstracting and the overall design of the solution is good then it will get used.
The code which follows best practices and is amazing or whatever without sufficient documentation is generally not appealing at least to me to contribute to, but you can always do "footprinting" meaning tagging the code with #WTF tags to things that you don't understand and then commenting codeblocks out and changing them to figure out what they do to write a documentation.
Real life example being the work done by edolstra on Nix package manager being used to create GNU Guix.
> but getting there often requires to work in places where they want things to be done and dont care if you do it sloppily.
yes proprietary development is that way and as long as it gets government funding to compensate for the long-term economical damages at the cost of tax payers that this development does then it will be still used (US).
> Shit workplaces and improper env setups are the reason.
none gives a damn about workplace on free software development..
You don't like the developer? -> Fork it
Real life example being slic3r being forked in prusa slicer. (https://github.com/slic3r/Slic3r/issues/5127)
about improper env setups i agree that those are annoying but i am not aware of a case where this was ever a problem, but you can always define a NixOS/GNU Guix and/or docker bootstrapping which is what i do when i work on something.
> You cannot expect people in here to be industrious & skillful
I don't expect them to be experienced i even welcome people that never coded in their life in my projects e.g. recently teached programming to a 12yo who used a project to which i contributed to and who found a minor bug that they were able to fix.
Aside from all that when you get to problems more complicated than a practice problem it gets really easy to write sloppy code that you have to reinterpret 3 months from now. Worse you have to interpret someone else's bad code. Programming is more than the sum of its parts.