the universal code

AND THIS IS HOW GEMS ARE NAMED.

Amethyst: Facet-5 Cut-8xM
Peridot: Facet-2(F5L) Cut-5xG

Hey! @the-a-j-universe , I got one!!!


Peridot has extra in her name because she is in a sub vein where as our amathyst’s kindergarten is no where near as eaten up as homeworld projections are.

9

happy black history month ft black cartoon characters!
click the pics to see the show names :)
click here for an updated list/gifs!!!

My Top 20 Anime-Influenced TV Series

This is a list of my most favorite TV series from my PreTeen to my Adult Hood years. Hope you guys like it.

1. Steven Universe

2. Kappa Mikey

3. My Life Me

4. Totally Spies

5. Martin Mystery

6. W.I.T.C.H.

7. Wakfu

8. Hi Hi Puffy AmiYumi

9. Code Lyoko

10. Avatar: The Last Airbender

11. RWBY

12. The Legend Of Korra

13. Teen Titans

14. Ben 10: Alien Force

15. Super Robot Monkey Team Hyper Force Go

16. Samurai Jack

17. Jackie Chan Adventures

18. Xiaolin Showdown

19. Magi-Nation

20. Boondocks

supernovabucky masterlist

Bucky Barnes x Reader

Code Dead

edge of the universe

Somebody else

Greaser boy - part I - II - III - IV - V - VI - VII VIII - IX

faking it - part 1 - 2 - 3 - 4- 5 -6

Tuyo Sera (coming soon)

Stevebucky

robbers (coming soon)

Avengers x reader

Otherworldly - part 1 *On Hold*

The Kids Aren’t Alright (coming soon)

7+1 tips for coding…

I had this post sitting on my drafts for a few weeks, so I decided to make it pretty and post it. Enjoy!

Based on what my teachers told us.

1. Think before coding.  →  Take 10 minutes, 20 or even 30, whatever you need and think about which design pattern (if any) is appropriate for what you are going to code. Really think about it, you’ll be glad for those “wasted” minutes when you have to change or add something on the code and it only takes you 30 minutes instead of 5 hours.

2. Comment your code. →  Seriously, there’s nothing worse than check your own code two months later and don’t remember what it does. Comment everything important, avoid really obvious things.

3. Write clean code →  Indentate. Use spaces. Separate your code in blocks by functionality.  Read Clean Code by Robert C. Martin, it’s really useful. Also, follow whatever convention/standard the code has (like the Java Code Conventions), especially if it’s a shared code.

4. Refactoring is your friend. →  Nobody likes those looooooooong methods with tons of lines. Usually (almost always), that means you’re mixing functionality. Separate the code in more manageable methods. It also helps to make the code more reusable… which lead us to 5.

5. DO NOT COPY AND PASTE CODE.   →  If you have the same chunk of code twice or more times, you’re probably doing something wrong. Read no. 4.

6. Use meaningful names. →  It’s always funny to name your int variable “elligent” or your char, “mander”; but that doesn’t say anything about what it is for.

7. Test your code. →  Test, TEST, test, tEST. Also, test as you code. Don not wait until you’re done with the program to test it or you’ll regret when you find a giant bug you don’t even know where it came from.

7b. Automated testing is usually worth it. It also helps to save a lot of time with retesing and regression testing.

7+1. Learn to debug. →  In my first year, I used to think that I could manage without knowing how to do it and by printlning every time I had a problem. Wrong. Sometimes, I wouldn’t even find the bug and checking for “lost” println is a waste of time.

01 . 15 . 17 — Style Influence Map

I’ve been struggling to find my own style lately so I decided to go back and study my favorite art styles. This is a (condensed) list of the major studios that have shaped me as artist :)

[personal commentary under the cut]

Keep reading