Any pronouns. 33.

Professional developer and amateur gardener located near Atlanta, GA in the USA.

I’m using a new phone keyboard, please forgive typos.

  • 61 Posts
  • 2.86K Comments
Joined 3 年前
cake
Cake day: 2023年6月13日

help-circle














  • This is why CC0 should not be used for code. Its public license fallback explicitly does not give patent rights. Compare that to MIT which implicitly does by saying you can use the software however you want. CC0 literally has this clause in the public license fallback.

    No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.


  • Yeah, a lot of copyright law in the US is extremely forgiving towards creators making mistakes. For example, you can only file for damages after you register the copyright, but you can register after the damages. So like if I made a book, someone stole it and starting selling copies, I could register for a copyright afterwards. Which honestly is for the best. Everything you make inherently has copyright. This comment, once I click send, will be copyrighted. It would just senselessly create extra work for the government and small creators if everything needed to be registered to get the protections.

    Edit: As an example of this, this is why many websites in their terms of use have something like “you give us the right to display your work” because, in some sense, they don’t have the right to do that unless you give them the right. Because you have a copyright on it. Displaying work over the web is a form of distribution.



  • So, if you’re brand new and want to learn concepts of how to write code, I might suggest a game. There are a lot of programming games. Obviously it’s never a one to one about learning something useful, and a lot of them even make “bad” things useful (though not bad enough to think it’s going to teach you bad habits you won’t be able to unlearn). I really enjoyed Exapunks, but it’s sort of unrealistic. The Farmer Was Replaced looks fun as well and uses a “simple Python-like” language, but I haven’t played it.

    If you sort of already understand the concepts and want to dive into a real language, well, it’s hard to say what will be fun. Chase your fun. It might be easier to think about what’s not fun and avoid languages at the start that deal with that. For example, if setting up an environment to code in is the problem, then maybe something like JavaScript would be a good place to start. It runs in your browser! Press F12, click “console”, type alert("Hello, World!"), boom, done, you just did Hello World in JavaScript without downloading anything at all.




  • Disclaimer: I am not a rust developer, but I am a professional developer with over ten years experience.

    I think folks telling you things like “you should learn X language before Y language” are not giving you the best advice. I often understand their arguments. The advice is typically “don’t learn X high level language before Y low level one.” But if we need to start lower, where would that advice end? Must someone really understand transistors before writing hello world in Python? No! Absolutely not.

    Learning any programming language will make you better at all programming languages. There is no perfect starting place. There is no bad starting place.

    Think about it like this. Someone tells you before learning to drive a car with automatic transmission you should learn manual. They say it’ll make you appreciate the automatic transmission more and that it’s easier to go from manual to automatic than from automatic to manual. Well, a more relevant question is do you plan to ever drive a manual on a normal basis. If the answer is no, you don’t plan on ever using it apart from learning how to, why bother? If you ever need to learn it, you can learn it. You’ll be better at driving by then and can focus on shifting gears without having to struggle to also focus on all the rest of the driving things you do (like staying in the lane, going the right speed not hitting people, etc.)

    If you only want to learn C just so you better appreciate things in other languages, don’t bother. Learn the language you want to use. If you want to use C, go for it! There’s nothing wrong with it. A lot of folks want to learn both Rust and C because they want to learn both and stick their toes in everything. That’s fine too! Just don’t feel obligated because you think it’s the best way forward.