Things Programmers Shout #454

How do you make the jump from like, completing CodeAcademy lessons to actually conceptualizing and building a program?

Honestly, it is really tough. People seem to make it sound like it’s a lot easier but if you’re doing it by yourself, you really have to work at it!

What you could start doing is drafting up a thought in your head from any idea; say you think "I have this problem and it could be solved this way”. Transform that thought into a solution and use it! It’s going to be a bit tougher since CodeAcademy can’t teach you the logic of everything, but it will start to get easier and easier as time goes on! 

I would also suggest maybe looking at school websites for Computer Science, as a lot CS teachers will post their assignments on a website and you can use those to base projects off of!

envision yourself exactly where you want to be. what motivates you? picture that, and never let it go. keep it in your mind and heart as you construct a plan to achieve what you want. with discipline and some confidence, you will reach your goal. you will.

My kink? Knowing all the information

Fun fact: the plural form of octopus is actually octopodes (oct-op-o-tees) since octopus isn’t an English word nor a Latin word. Octopuses would be the English form if octopus was an English word. Octopi would be the plural form if octopus was a Latin word. However, octopus is a Greek word which means that the grammatically correct plural form of octopus is octopodes.

The first guy who heard a parrot talk was probably not ok for several days.

The thing about computer programming is that it’s a complete pain in the ass when you’re trying to figure out the problem, yet when you finally solve it, when you finally have that aha moment, the feeling of accomplishment is unlike anything you’ve felt when you’ve accomplished something. You think holy shit, I can make technology work, and that feeling is totally worth the long stretch of hours or even days when computer programming feels like a pain in the ass.

my favorite out of context quotes from my archeology professor so far in no particular order

and floridians are just as human as you and me!

and the moral of the story is that there are no deadly snakes native to alaska

you might know this guy as one of the only archaeologists cool enough to be mentioned by indiana jones

it’s my dream to have my name said by harrison ford

i’m not going to apologize for having this class at 6am because you paid for it and it’s your fault. 

we don’t all dress like lara croft. i tried to get it to be a thing on a dig and my colleagues yelled at me. 

they were pretty good archaeologists except they were too racist to realize anything they found. 

i take back what i said about us not dressing like lara croft because lewis binford here is wearing nothing but short shorts and a cowboy hat. take notes for an academic halloween costume!

archaeologists can be good artists! not me, though. or anyone i know. but if you can draw just know you have options.

sometimes you find dead bodies when you dont really expect it and you just have to deal with it

archaeologists are the only people allowed to get exited when they find corpses. 

once i ruined thanksgiving dinner when i told my family i had gotten my degree in archaeology and my uncle commented he liked dinosaurs too

the closest i’ve ever been to a grizzly bear is when i left my glasses in my tent on a dig in alaska,  saw a big rock in the distance, and almost screamed

hey hey hey everyone!! as a self-proclaimed mathlete & absolute math nerd, i figured i could share some quick little tips for such an amazing subject! soooo here you go:

practice, practice, practice!!

I always say that practice is the most essential aspect of studying & learning math- and many other subjects! This can take the form of homework (mini tip: always do your homework if you are able!!! it’s only to your benefit! even if it’s not for a grade, try your best to work on it anyway), practice problems from a textbook or workbook, old questions from a past quiz or test, etc. Even just a couple of practice problems every day, or some quick q’s before a test, can help a lot. Remember, repetition is a key form of revision!

take active notes

Math is a very active subject, so it’s important for your notes to reflect that. Basically, if you’re working on an example problem in the middle of your notes, write it down too. These problems can come back in quizzes or tests, and they really help reinforce material when you’re reviewing. Another way to keep your notes active is by drawing diagrams!! Diagrams can be essential for certain topics, so please don’t ignore them, even if you think you can remember what that graph looks like. Also, if you ever need to jot something down in the margins of your notes, do it! All of this will really help when you review.

know your calculator 

Whether you need to know how to use one, or how to survive without one, calculators are pretty much always relevant when it comes to math. If the subject you’re learning allows it, you should always have a calc nearby, and you should know its basic functions. That doesn’t mean know how to add & subtract (unless that’s all that’s necessary for you), it means being able to work the graphing function, or how to enter data into your calculator for statistical evaluation, how to find certain functions in your calc, etc. It’s also very important to know how to work without your calculator. As you progress in math, there will be certain things that you just need to know how to do, because they take too long with a calc. Basically, make sure you understand what you’re doing with your calculator, so that you can understand how to do it without your calculator.

keep track of everything!

Math is a lot of data & different steps that you need to keep track of. When working on something, know where your numbers (or other forms of data) are, make sure you aren’t missing any! Do your best not to skip steps, even if you’re great at working in your head. Missing data & skipped steps are major sources of error and tiny mistakes that can mess up a whole problem. Also, know your common errors! Do you tend to skip a certain step because you think you’ve got it? Do you sometimes misinterpret graphs or data? Once you’ve figured that out, be extra careful with the specific problems that you have trouble with. Keeping track of your work & your mistakes can help you improve a lot!

memorize what needs to be memorized

A lot of math can be done with basic understanding of how to work a problem & the process to find a solution (these things are generally memorized with practice!) but there are some things that just need to be memorized. Whether it’s elementary functions like addition & division, or basic trigonometry, if it’s not a process you can learn through understanding, and need to know, make sure you know!! Some things can be memorized with practice, and others require different methods of memorization (I typically write & rewrite things multiple times). You can find some great posts on memorization here!

more masterposts!!

stem studying

study methods

precalculus

algebra

geometry

(ap) chemistry

ap world history

studyblr-ing

the everything book

the pomodoro method

how to use flashcards

how to use sticky notes

welcome to high school

tiny study spaces

what’s in a pencil case

i really love math & i wish everyone could see it like i do, so i hope this was helpful! keep shining like the star you are and don’t forget to be awesome today!!

- Aza

right, if you are in college and are a cs major or a budding software developer, i highly recommend you to check out the architecture of open source applications, especially the 500 lines or less section. architects, artists etc look at thousands of buildings/paintings  throughout their lifetimes, critique them, learn what’s worked and what didn’t. most software developers, however, do not share that experience - unless it’s with a codebase they have written themselves. 

reading other people’s code is JUST as important as writing code of your own. i especially recommend the projects/documentation in 500 lines or so section b/c while they are big enough for you to understand basic system design, 500 lines of code isn’t too overwhelming. plus it’s super cool to read about building a database built from archeological principles or how the code behind pedometers works