Skip to content

Instantly share code, notes, and snippets.

@BlakeBarrett

BlakeBarrett/Things to learn when approaching a new programming language or framework

Last active June 14, 2021 21:58
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save BlakeBarrett/3ad4a1f21681600433b66578bafdc221 to your computer and use it in GitHub Desktop.
Save BlakeBarrett/3ad4a1f21681600433b66578bafdc221 to your computer and use it in GitHub Desktop.
Download ZIP
Learning a New (Programming) Language Checklist
Raw
Things to learn when approaching a new programming language or framework
* What are the files named?
* What casing is convention?
* Semi-colons or not?
* What does the code look like, conventionally?
* Programming in general:
variables, constants, static, structs, interfaces, enums, lists (arrays, maps) classes, abstract, anonymous classes, functions, closures, async, threads, network io, (de)serialization, files, streams, graphics, local hardware, etc...
unit testing
* UI:
What are "screens" called?
Views, containers, text, images, buttons, text input, "component" input i.e. sliders, radios, check boxes, etc,
scrolling,
grids, tables, item cells
cards,
* Animations, transitions, segues, effects, etc, external files (like Lottie, etc)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment