You’d be surprised how little math is involved in programming that doesn’t require it. A significant majority of programming is simply managing conditionals. For example: “when the door opens, turn on the light.”

Math comes into place when you need it, and hardly ever comes as a surprise. Additionally, solved problems are generally kept in libraries. For example, you don’t need to calculate a sum; simply tell it to calculate a sum for you, because this is a solved problem.

What you’re already running into is called “impostor’s syndrome.” You believe that you are not capable of something to some degree, even though reality says otherwise. You haven’t tried your hand at programming, so why worry now? You’re inventing problems for yourself before you even got a chance to start.

Just go for it and see what you think. If you don’t enjoy it, no biggie. If you do enjoy it, keep going. No obligations 👌

deleted by creator

YouTube’s users when they adhere to the YouTube TOS:

Vim handles remote files over SCP natively:

vim scp://192.168.1.2//data/editme.txt

It was trying to is, then it isn’ted. Help?

Imagine your “code” as English sentences. If it is hard to read, you might rephrase it. If something is getting long and drawn out, use paragraphs (methods and functions). At the end of the day, the easier it is to read, the better, unless there’s a performance cost that’s worthy of considering.

Like the top-level comment suggests, you should comment your methods. I would go one step further and use a standard comment format. I like Ruby, so immediately, I think YARDoc. With a YARDoc comment, you define what it does, the parameter types and descriptions, what it returns, possible exceptions that could be returned, etc.

Even better, by using standardized comments, not only does this make it easier to read by you and others, but most of the time, you get documentation rendered for free. For example, here is a library I wrote:

• https://github.com/synthead/timex_datalink_client

And here is the automatically-generated HTML documentation:

• https://www.rubydoc.info/gems/timex_datalink_client/0.12.3

More specifically, here’s some YARDoc for a method:

• https://github.com/synthead/timex_datalink_client/blob/263bffa8a71a0af792c46bea2ae69ab2a015f670/lib/timex_datalink_client/protocol_3/time.rb#L38-L46

And here is the generated documentation from this comment:

• https://www.rubydoc.info/gems/timex_datalink_client/0.12.3/TimexDatalinkClient/Protocol3/Time#initialize-instance_method

This style of auto-generated documentation is available for pretty much all mature languages, and I highly recommend that you hit the ground running with them 👍

There was an explosion of users when Reddit went Monopoly Man over their API. It makes sense that usage will waver a bit for a while, and that not all people will stick. Lemmy is like Reddit, but it doesn’t have full parity to it.

Why Apple?

To people that really spend time in code, this banter is meaningless.

You might enjoy !veryrealtechpics@lemmy.world

It’s a shame how obvious they’re working their corporate bullying cards simply because of money. Imagine if I created a product called Google and tried to sue Google for it. That would be ridiculous, right? Well, that’s what Facebook is doing, just with money.

I wouldn’t worry about Chrome having vulnerabilities in its image readers.

Hopefully you’re not using an image reader that’s shitty enough to have vulnerabilities like this 🤨

Pointers hard!! LOL

You’ll get an OSError if you try to remove a directory with os.remove

https://docs.python.org/3/library/os.html#os.remove

“Designed for Windows Me Millennium Edition”

Keep filling those bugs and stop complaining on random forums, kids

Probably whitespace.

Maybe we just need to tighten them? Perhaps a lock washer will help 🤭

What’s the name of your first pet?