Latest Posts by tres-4b-blog - Page 6
How To Code: Insertion Sort in C language
Insertion sort is a basic algorithm for sorting elements in an array or list. Insertion sort works by grabbing one element and comparing to the element next to it. If the element is larger than its neighbor, then the element is left in its original position. If the element is smaller than its neighbor, than it compares it to the other previous elements to find a suitable position. Then all larger values are shifted up a space and the element is inserted into the correct position.
Output:
Sorted Array array:[17][26][36][48][52]
Custom cursor malware that destroyed your computer in 2008 and got you yelled at by your mom moodboard
*me on ellen*
ellen: so i hear u like spyro the dragon
me: yeah i guess u could say i’m a bit of a fan
*everyone in the audience turns to crystal*
me: omg ellen u didn’t
Crazy Blue/Purple Fluorite on Calcite
Locality: Summit Cleft, Weisseck, Lungau, Salzburg, Austria
Size: 13 × 10.5 × 7.4 cm
Hubble Space Telescope Image of Globular Cluster NGC 6397
Credit: NASA, ESA, and H. Richer (University of British Columbia)
Artificial intelligence bot trained to recognize galaxies
Researchers have taught an artificial intelligence program used to recognize faces on Facebook to identify galaxies in deep space.
The result is an AI bot named ClaRAN that scans images taken by radio telescopes.
Its job is to spot radio galaxies – galaxies that emit powerful radio jets from supermassive black holes at their centers.
Keep reading
This is Earth, our amazing home. The only planet in the solar system with the ability to harbor life (that we know of).
This is the distance between our awesome planet and the moon.
Doesn’t look that far does it? How about if I told you that you could fit EVERY planet in our solar system neatly in that distance.
Speaking of the other planets in our solar system, this is them & this is where our amazing planet resides.
The moon’s our cute little companion. This is the United States compared to it.
The planets in the solar system are so cool. This is what North America looks like in comparison to Jupiter.
Speaking of Jupiter and the moon, this is what it would look like if Jupiter was in the place of the moon. (The white dot is our moon).
Earth compared to Saturn (well 6 Earths…)
Ever wonder about what Earth would look like if it had rings like Saturn? Well wonder no more..
Amazing right? Want to see something cooler? Here is the Earth compared to our Sun.
Here’s what we look like from the moon
And from Mars
From Saturn
From Neptune…
Here is what the Sun looks like from Mars
Remember what Carl Sagan said? There are more stars in space than grains of sand on every beach in the Earth.
That’s a lot right? That only means there are stars way larger than our Sun..like this one for example:
And there are stars bigger than that….
Stars are huge, but the galaxy is even bigger. If you shrunk the Sun down to the size of a white blood cell, the Milky Way Galaxy would be the size of the United States.
This is where the Earth is in our huge galaxy
You know all the stars we see in the sky? These are the ones we only ever see (this isn’t our galaxy but its very similar)
The Milky Way is so big that the last time the Earth was in this exact position in the galaxy, the dinosaurs were here
Even though our galaxy is huge, there are galaxies that are even bigger…
This picture from Hubble shows thousands of thousands of thousands of galaxies that each have their own stars with their own planets…
Here is one of the galaxies in that picture. It is 10 BILLION light years away. When we look at it, we are looking 10 BILLION YEARS BACK IN TIME
And just to keep this in mind, this is a very small portion of the sky that was believed to be empty…
Everything is relative.
Next time you’re stressed out or worried about something, stop and take a step back. Look up at the sky and think about all of the things that are out there. All the stars being born, the stars dying, galaxies colliding.
We live in such an amazing universe, and we are only an extremely tiny part of it.
Credit- pictures from: Buzzfeed on Facebook
hi. happy holidays. I'm going to start my college next month. I'm generally a messy student. I have a hard time managing my schedules and notes. I recently started following some studyblrs. but I'm still lost. I could really use some advice right now. love your studyblr btw.
Helloo! Happy holidays as well :-) Here are a few links that might help:
how to improve your handwriting
balancing study and work
whats in my bag
my favourite stationery
back to school basic supplies
how I stay motivated
tips on maintaining motivation
how to start a studyblr
how to take effective class or lecture notes
how to take notes from a textbook
how to memorise information effectively
my note-taking method
my notebook system
how to write faster
how I organise my binders
good habits to implement
how to study (my method)
how to get ahead in school
dealing with stress
productivity and time management applications
how to remove distractions
Here are some printables that might help you get organised:
2018 monthly planner printables
2018 student printables (2018 overview + calendar, daily + weekly + monthly planner, 30 habit tracker, class overview and timed worklog)
weekly study schedule
note-taking printables (dotted, grid, lined, cornell method)
exam revision printable pack (revision checklist, formulas + definitions sheet, essay + project planner, weekly schedule)
studying printable pack
ultimate student organiser pack
study and revision pack
pomodoro tracker
2018 student planner
2018 weekly planner
grade and assessment planner pack
essay guide and planner pack
student finance planner
note-taking printables (cornell, lecture, dotted, grid, etc)
goal and habit planner
I hope this helps!! Good luck with everything and thank you xx
Chemical Space Gardens
You know that colorful crystal garden you grew as a kid?
Yeah, we do that in space now.
Chemical Gardens, a new investigation aboard the International Space Station takes a classic science experiment to space with the hope of improving our understanding of gravity’s impact on their structural formation.
Here on Earth, chemical gardens are most often used to teach students about things like chemical reactions.
Chemical gardens form when dissolvable metal salts are placed in an aqueous solution containing anions such as silicate, borate, phosphate, or carbonate.
Delivered to the space station aboard SpaceX’S CRS-15 cargo mission, the samples for this experiment will be processed by crew members and grown throughout Expedition 56 before returning to Earth.
Results from this investigation could provide a better understanding of cement science and improvements to biomaterial devices used for scaffolding, for use both in space and on Earth.
Follow the growth of the chemical garden and the hundreds of other investigations constantly orbiting above you by following @ISS_Research on Twitter.
Make sure to follow us on Tumblr for your regular dose of space: http://nasa.tumblr.com
I want to make games so which code should i learn?
I’m unsure if you already have an engine picked out because you asked which language to use and different engines may use different languages so here we go.
I personally would say you may want to download the Unity engine. Unity is a tool developers use to basically build the world, add items, characters, etc. There are, of course, other engines out there but Unity is one that most people tend to use. Then there’s also Cryengine and Unreal Engine although, these are more advanced and have a wider learning curve. Unity is free to use (there are also features that only paid users are allowed.) and most colleges will instruct their students to use Unity for their learning. If you scroll down far enough, you’ll see the games I made while learning. Although I never finished them, Unity has more than enough power to make good games while learning. Unity supports 3D and 2D game development and I don’t believe Unreal or Cry engine do. (Not positive on that so correct me if I’m wrong everyone..) There are a lot of lower-level engines out there as well such as Love Engine (I hope I’m spelling all of these correctly…). I’m assuming you want to make the entire game on your own, right? If not then you’ll need a team of friends. If You do plan to develop alone, you’ll need a programming language that the engine supports. I know Unity supports C# and JavaScript. Most would tell you to learn JavaScript first because it’s easier to grasp and I do believe that to be true. Trust me, go JavaScript. I’m unsure of what languages you should study for the other engines but I assume most of them use JavaScript or C#. I’d check for yourself on that.
I really hope this helps you or someone out there to get started.
Good luck!
Disclaimer: As always, this is a guide on how I like to study maths and how I did well in final exams- but of course doesn’t work for everyone! These are only suggestions. ´･ᴗ･`
Mindset- A lot of people dislike maths and a big reason (from experience) is that people believe that it is too hard/ don’t understand. The great thing with maths that is different to subjective classes like English- if you know all of your concepts and formulae, you WILL do well. Your mind will help you pull through. Maths in honestly not that difficult. Everything that is hard is really just the concepts you know, in a more creative way.
The Mistake Palm card- Any silly errors you make- put down onto a palm card in terms of topic. For example, on my “Sketching graphs” topic, a mistake I make is not marking the point of inflexion. Things like not forgetting to mark your axes, label a point etc. go here.
The Mistake Word document- your mistakes from practice tests, exams at school and questions you don’t know how to solve initially all go on this. Scan/ take a photo and dump it into Word. This is for you to go over a few months later (or before your test) to make sure you know how to do the question! Mine ended up being 20+ for my HSC exam and it definitely helped!
Formulae Palm card- Same as the mistakes palm card, just dump all your formulae and you can carry it around in your pocket to read on the train or wherever you go.
Practice!- Practice papers are the most important thing. Exercises from your textbook are great, but you have to do past papers more so. This is to get familiar with format, tricky questions that could be asked and how fast you can do one.
Study depth, not breadth- Doing question after question from the textbook is not smart studying. A lot of those questions are the same thing but with different numbers so you’re not really giving yourself benefit of different formats. A lot of people saying they “study a lot” when they do this but you have to expose yourself to different kinds of questions. Know when to skip questions if you get the concept and to repeat if you don’t understand.
Timed Conditions- Practice papers under timed conditions are great at home. Aim to do the whole paper in 80-90% of the time to make sure you have time to check in tests! However in Australia, the HSC exam is 3 hours for mathematics when it only takes 1- 1.5 hours to complete- if you’re at home and you finish checking before time is up- just mark it. You’re wasting time by waiting for 3 hours when you could do two more tests in that time.
Don’t Repeat Papers- Don’t repeat papers! Repeat the questions you got wrong. This is because you’ve seen the questions before, and you know what to do. Try to find more practice papers on the internet instead.
I hope this helped anyone who does Mathematics- this probably works best with HSC since I don’t really know how overseas exams work. Thank you!!
Jade
xx
“This is what happens when you reply to spam email” - James Veitch (TED)
This is worth the watch. It’s hilarious!
8.10.2016 // 13/100 Days of Productivity// Now that I’m on vacation again, I finally found some time to invest into my favourite notebook. On another note, thanks for 900 followers! Have a nice day!☀️
Advice to a New Programmer
So much advice is heaped upon beginners that it can be hard to know where to start. However, these five practices are the foundation upon which everything else is built. The beginner I have in mind has a basic understanding of how programming works, has written mostly small programs of varying complexity, and is heading off to either a career in the field or committed to excellence for his or own personal projects. There is only one truly foundational activity in programming: writing code. To be good at it, you’re going to have to write a lot of code. That big body of work can be a vehicle for growth, or an exercise in repeatedly practicing a limited set of skills. To avoid the latter, you need to: Read a lot of code. Specifically, read a lot of code by excellent programmers. Not just good programmers, like the guy down the hall, but excellent ones. Due to the huge amount of open source today, this is easy to do. When I was learning Java, I read code from the Tomcat project and from the CI server, Cruise Control. I’ve read lots of good code since. It might be tempting to look for main() and start from there, but you’re likely to spend a lot of time just reading set-up code and command-line parsing. I prefer to scan the filenames to look for some activity that interests me and then dig into those files. It’s not crucial to understand the whole project or the ins and outs of the entire design, you’ll wear yourself out doing this. Read the code. Look at the comments, see what the authors are doing, and how they went about it. Learn your tools thoroughly. I think the greatest loss of programming time is not in debugging or rewriting code, but in the innumerable seconds lost here and there by developers who don’t really know their tools. I am referring to: the IDE, the language, the build system, and the VCS. Of these, the IDE and the language are by far the most important. You should, after a few weeks of practice, know almost every keystroke combo in the IDE, so that you touch the mouse only when it saves a lot of keystrokes. If you know the keystrokes, you know the commands. If you use the mouse only, you know only menus on which you tend to click on the same one or two entries. Knowing the IDE is pure discipline. Knowing large languages, such as Java or C++, takes more than discipline. They’re huge, as are their libraries. Reading is the best approach, in my view. Read code that uses features you don’t know and you’ll look for opportunities to use them. Books (rather than blogs) are another excellent source. Read about features that are on the periphery of what you use currently, and soon you’ll find the periphery expanding. Knowing the VCS and build systems make you a desirable team member — who doesn’t waste time due of ignorance of important operations. Plan your code before you write it. I think this is the most difficult item on this list. In exchange, it probably delivers the most benefit. I’m not thinking of formal design — at your stage, that’s unlikely to be necessary. But you do need to plan out the code in some manner other than carrying it around in your head. The simplest approach is to write up a small document (I frequently use a mind map): What are the requirements for this code? How will you implement it? What do I need to know that I don’t know now? What are the objects I will need or need to create? And write this out. Only then begin to code, you’ll find the code much easier to write, to document, and to get correct. Save your notes — they’re great reference material. Write lots of code and have it reviewed. If your site does not do code reviews, do them yourself. Find the best programmer who’ll give you useful advice in a way that can be heard and understood. Don’t be a pest, but don’t avoid the process because you’re shy, busy, or feel you’re good enough, etc. Code reviews should be part of your programming life. Be creative. Try pair programming with someone more senior than you for an afternoon. The important thing is that you need feedback that you cannot give yourself. Write tests as you code. This advice is perhaps the only controversial item here. It’s not an endorsement of TDD. But it is an endorsement of knowing that your code works in most scenarios it will face. Start with unit tests and exercise new code with edge-case values. For example, does your function work if it is passed a negative value, or the maximum integer size? If not, does it throw an informative exception or just blow up? If not an exception, have you narrowed the range of inputs with asserts? If so, test the asserts. Use the planning you did earlier to write mocks, and then begin testing your new code with objects you still need to write. This will clarify design issues in your current code and the upcoming objects. Save your tests and run them prior to every check-in, so that they can be early warning systems for later code that breaks your current code. There’s a lot more advice and many wise sayings that can be added to this list. But that’s part of the problem: There’s so much advice available that it’s difficult to know exactly where to start. For that reason, I purposely limit my recommendations to just five points. If you apply them with diligence, you’ll soon find two things: You’ll be able to handle progressively larger and more important tasks, and you’ll look back in embarrassment at code you wrote just a few months ago. Both experiences are sure signs of progress. Good luck!
