Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
On the programming front, there are a couple general buckets you can fall into.
Do you tend to naturally follow logical reasoning (given then )? If yes, you're in a pretty good starting position for algorithms. Computer programs should be predictable/deterministic. This all hinges on the people making algorithms implementing them well - especially when it comes to corner cases.
Do you build excel files with tons of vlookups and the like? If yes, data structures (think database schemas) and potentially back end could be your jam. Programs store/access data. That information should be well structured.
Do you have workflows/UX front of mine? If yes, maybe your strong suite is UI/"front end" design (and potentially implementation). IMO this is where a lot of FOSS falls down - my current podcast app can show you podcasts episodes that have been released in chronological order. You can remove them from this list, or you can add them to a secondary list they call a quque which... offers basically the same functional as the first list but now that it's a separate list you have to manage. This is not a dig on FOSS. If anything, it's meant as encouragement to say that even without knowing how to code you can contribute to help the apps you use feel better to users.
If you want to get your toes wet in Android download Android Studio. It's free.
Give the Jetpack Compose tutorial a run-through.
Kotlin is what happened when Oracle sued Google about using Java to anchor Android development. The link above gives a decent programming 101.
Finally, if you live close to a local community college, signing up for a few programming classes might be pretty helpful.