Before you begin:

• Know what you want. What you really want. And don’t think of “how” you’ll get it. • Write the desire in present tense on a card. It is now your goal card. • Carry this card with you and read it often. This is putting the desire into your subconscious mind. • Check if your goal is really what you want. Can you imagine bigger? Are you letting fear stop you? Are you answering your soul’s calling with this? 

Night:

• How you fall asleep determines what shows up in your life. Everytime. Without fail. So we start our day how we fell asleep the night before, actually. Ask your self one question before you sleep: “If my wishes were fulfilled, how would I feel?” Fall asleep to that question satisfied. • Record an MP3 or voice note of your OWN voice, reciting positive affirmations. Get examples online but personalize them. Your subconscious mind trusts your own voice. Use it.  • Never ever let yourself fall asleep feeling stress or failure. Don’t invite it in. 

Morning:

• When your eyes open, set your intention for the day.  • Did you have any dreams last night? Write them down. • Write 5 things you’re grateful for. Increase to 10 after a while and begin to include wishes that are yet to manifest e.g. “I’m grateful I now weigh __” 

Day:

• Read Think And Grow Rich by Napoleon Hill. (PDF’s online) Read slowly and reflectively.  • Read Feeling Is The Secret by Neville Goddard (PDF’s online)  • The Secret book/DVD is great for beginners but you’re going to have to dig deeper to pull this off.  • Do what makes you smile. Read, play your music, call a friend, go for walks. Do whatever you can to lighten your mood.  • Write about your desire as if it’s already happened.  • Visualize your life ASSUMING the desire has already happened. How do you feel? What are you wearing? Where are you? Was manifesting easy and fun?

Remember:

• Bruce Lee, Jim Carrey, Arnold Schwarzenegger, Oprah Winfrey, Big Sean, Conor McGregor and countless others have used this formula. It works, and it will work for you. 

jubilant (adj.) - extremely joyful, happy (The crowd was jubilant when the firefighter carried the woman from the flaming building.)

knell (n.) - the solemn sound of a bell, often indicating a death (Echoing throughout our village, the funeral knell made the grey day even more grim.)

lithe (adj.) - graceful, flexible, supple (Although the dancers were all outstanding, Joanna’s control of her lithe body was particularly impressive.)

lurid (adj.) - ghastly, sensational (Barry’s story, in which he described a character torturing his neighbour’s tortoise, was judged too lurid to be published on the English Library’s website.)

maverick (n.) - an independent, nonconformist person (John is a real maverick and always does things his own way.)

maxim (n.) - a common saying expressing a principle of conduct (Ms. Stone’s etiquette maxims are both entertaining and instructional.)

meticulous (adj.) - extremely careful with details (The ornate needlework in the bride’s gown was a product of meticulous handiwork.)

modicum (n.) - a small amount of something (Refusing to display even a modicum of sensitivity, Magda announced her boss’s affair to the entire office.)

morose (adj.) - gloomy or sullen (David’s morose nature made him very unpleasant to talk to.)

myriad (adj.) - consisting of a very great number (It was difficult to decide what to do on Saturday night because the city presented us with myriad possibilities for fun.)

nadir (n.) - the lowest point of something (My day was boring, but the nadir came when my new car was stolen.)

nominal (adj.) - trifling, insignificant (Because he was moving the following week and needed to get rid of his furniture more than he needed money, Kim sold everything for anominal price.)

novice (n.) - a beginner, someone without training or experience (Because we were allnovices at archery, our instructor decided to begin with the basics

nuance (n.) - a slight variation in meaning, tone, expression (The nuances of the poem were not obvious to the casual reader, but the teacher was able to point them out.)

oblivious (adj.) - lacking consciousness or awareness of something (Oblivious to the burning smell emanating from the kitchen, my father did not notice that the rolls in the oven were burned until much too late.)

obsequious (adj.) - excessively compliant or submissive (Donald acted like Susan’s servant, obeying her every request in an obsequious manner.)

obtuse (adj.) - lacking quickness of sensibility or intellect (Political opponents warned that the prime minister’s obtuse approach to foreign policy would embroil the nation in mindless war.)

panacea (n.) - a remedy for all ills or difficulties (Doctors wish there was a single panacea for every disease, but sadly there is not.)

parody (n.) - a satirical imitation (A hush fell over the classroom when the teacher returned to find Magdalena acting out a parody of his teaching style.)

penchant (n.) - a tendency, partiality, preference (Fiona’s dinner parties quickly became monotonous on account of her penchant for Indian dishes.)

perusal (n.) - a careful examination, review (The actor agreed to accept the role after a three-month perusal of the movie script.)

plethora (n.) - an abundance, excess (The wedding banquet included a plethora of oysters piled almost three feet high.)

predilection  (n.) - a preference or inclination for something (James has a predilection for eating toad in the whole with tomato ketchup.)

quaint (adj.) - charmingly old-fashioned (Mary was delighted by the quaint bonnets she saw in Romania.)

rash (adj.) - hasty, incautious (It’s best to think things over calmly and thoroughly, rather than make rash decisions.)

refurbish (v.) - to restore, clean up (After being refurbished the old Triumph motorcycle commanded the handsome price of $6000.)

repudiate (v.) - to reject, refuse to accept (Tom made a strong case for an extension of his curfew, but his mother repudiated it with a few biting words.)

rife (adj.) - abundant (Surprisingly, the teacher’s writing was rife with spelling errors.)

salient (adj.) - significant, conspicuous (One of the salient differences between Alison and Helen is that Alison is a couple of kilos heavier.)

serendipity (n.) - luck, finding good things without looking for them (In an amazing bit of serendipity, penniless Mark found a $50 bill on the back seat of the bus.)

staid (adj.) - sedate, serious, self-restrained (The staid butler never changed his expression no matter what happened.)

superfluous (adj.) - exceeding what is necessary (Samantha had already won the campaign so her constant flattery of others was superfluous.)

sycophant (n.) - one who flatters for self-gain (Some see the people in the cabinet as the Prime Minister’s closest advisors, but others see them as sycophants.)

taciturn (adj.) - not inclined to talk (Though Magda never seems to stop talking, her brother is quite taciturn.)

truculent (adj.) - ready to fight, cruel (This club doesn’t really attract the dangerous types, so why was that bouncer being so truculent?)

umbrage (n.) - resentment, offence (He called me a lily-livered coward, and I took umbrage at the insult.)

venerable (adj.) - deserving of respect because of age or achievement (The venerable High Court judge had made several key rulings in landmark cases throughout the years.)

vex (v.) - to confuse or annoy (My boyfriend vexes me by pinching my bottom for hours on end.)

vociferous (adj.) - loud, boisterous (I’m tired of his vociferous whining so I’m breaking up with him.)

wanton (adj.) - undisciplined, lewd, lustful (Joanna’s wanton demeanor often made the frat guys next door very excited.)

Women have always been at the forefront of literature, the first novel (what we would consider a novel in modern terms) was written by a woman (Lady Muraskai’s the Tale of Genji in the early 1000s) take your snide “Isaac Asimov” reblogs and stick it

even in terms of male scifi authors, asimov was predated by Jules Verne, HG Wells, George Orwell, you could have even cited Poe or Jonathan Swift has a case but Asimov?

Navy Rear Admiral Grace Hopper helped invent some of the early English-language programming languages. She is most famously associated with the Common Business-Oriented Language (COBOL), which was based on the FLOW-MATIC language that she designed back in 1958.

Cards Against Humanity is letting customers pick which 2016 candidate they’ll donate to, as long as it’s Clinton

The game’s creators have launched a fundraiser, America Votes With Cards Against Humanity, where they’re letting their customers decide which of the two campaigns should received the donations the company collects.

Disclaimer: I am a second year computer science major and have not had much experience interviewing for/getting a (solely) computer science/programming job. These are tips that I’ve collected from company info sessions held by Originate, Facebook, and Yahoo! at my university’s Women in Information and Computer Science club events that I am just sharing. Company representatives also say different things or have different views on certain topics, so these tips are not universal and absolute! Please take into account your own experiences as well!

Resumes:

Tailor your resume for each position/role that you apply for. Different positions look for different things, don’t just send the same general resume to everyone!

Make and maintain a LinkedIn account. Getting job and internship offers through LinkedIn is possible, and it is more informal than a job application. It’s also great for networking; be sure to add company recruiters on LinkedIn soon after you meet them so that they will remember you and know your seriousness about the internship/job.

Make and maintain a GitHub account to document and show off your side projects.

Personal/side projects are a great way to show off your skills and what you do in your free time!

Hackathons are great experiences, but focus on what you have made during the time, not the fact that you went.

Interviews & Programming Interviews:

Check Glassdoor reviews for the companies you are applying for. You can get a feel of how the interview will go beforehand, as well as how other people felt during their interview or work experience to see if the company might be a good fit for you.

During the programming interview, code organization and formatting will be crucial. If they ask questions about your code, also be prepared to explain your thought process clearly.

What are some good end-of-interview questions to ask the interviewer?: This is the time to switch places and interview the interviewer! Ask them questions about their job and what they work on, the challenges they have faced, about their professional growth at the company, how long they’ve worked at the company, what the typical day is life for them, what made them decide to work there, and much more. Get to know them since you might end up working with them!

Follow up with your interviewer after the interview through email. Wrap up your thoughts and answer unanswered questions, if they allow you to do so afterwards.

And although money should not be stressed or particularly focused on during the interview, be prepared to haggle for your pay if you want/if possible. Oftentimes, the pay for the next job you’re looking for depends on the pay from your previous job. But when they ask you how much you want to be paid, let them quote the first number/salary. If you succeed at multiple job offers, you might be able to bargain with the companies (i.e. telling Company X that Company Y is willing to pay you more).

Everything Else:

Should I learn multiple programming languages generally, or focus on a few programming languages?: It is mostly up to you and what skills you want to show. Simply put, learn more programming languages not to make your resume look nice, but to expand your experience with different programming languages and methods, learn the pros/cons of each, and learn about the different features they have. Some companies will not expect you to be complete experts in the specifics of a certain programming language, others may ask about your knowledge in only one or two languages during the interview, and others may allow you to use pseudo-code during their in-person programming interview. For these things, it really depends on what you want to do and if you want adapt to the company/companies.

Related to the above point, try to balance yourself. Learn some scripting languages if you know more object-oriented languages, more about the software engineering side of tech if you’re a computer science major, more about the front end if you work the back end, or vice versa.

Highlight the impact of projects you’ve done or jobs you’ve had in your resume or interview: your impact on them (what you did), as well as what impact the software has had on others (x number of users) or the impact you had on the company (x% increase in company profit through y actions).

Include and be able to talk about other things besides computer science, software, and tech in your resume or interview. They want to see what your interests are and how available and involved you are for other clubs, organizations, volunteering, etc.

- In general most tech companies all look for the same thing, so tailoring your resume isn’t *that* big of a hassle, and you can get away with just having two versions. One for financial firms where concurrency and high performance projects are stressed and another for normal tech companies where you can put any project you find interesting on it 

- LinkedIn is 10000000% important in tech. If you ever send your resume via email to someone, make sure your linkedin url is clickable and on there! I have gotten numerous interview requests and connections through that. 

- Github, Personal Projects, and Hackathons are great! But if you’re like me and you take 18-21 credit hour semesters, you probably have barely enough time to get through school, homework, and your part time job, let alone do something on the side. So remember, your school projects and assignments are projects! You can put those projects on your resume. All the projects listed on my resume were class assignments I thought were super interesting and cool and that’s worked out hella well for me. (Just don’t do what I did and accidently add your school assignment to your public github where the whole world can see it. Because a semester later you might have to deal with someone starting a cheating ring for one of your classes using your code. Woopsie. Private accounts are your best friend).

- When I was in school everyone and their mother stressed out about asking the right questions after the interview and was always told to ask things like “If I started tomorrow, what would I be working on? What do you work on? What’s happening with project X at this company?”. Don’t do that just because you have nothing else you want to ask. Chances are if you’re interviewing at a medium to large company, the interviewer has no idea what you’ll be doing. And they’ll tell you a tl;dr of what they’re doing which you likely won’t remember. And if anything kewl is happening with project X, they’ll tell you whatever was posted about it on the company blog and nothing more. Instead if you have no questions, just admit that (really! large tech companies don’t even report internally about this!). And if you do want to fill that void, ask things like “What’s your most and least favorite thing about working at company X?” 

- Always, Always, ALWAYS negotiate. This bit me in the ass so hard. Research the market value of your location. Look at the average Dev Salary in the area. It does 0 damage to ask. Worst that can happen is they say no. And if you’re at a large notable tech company and have multiple better offers, and the recruiter tells you that they’ll risk rescinding the offer if they ask for a counter, be firm and respectful and push for it. They won’t rescind your offer, worse they’ll do is say no, take it or leave it. 

- Practice, practice, practice. If you’re coming straight from school, you’re going to get a lot of technical whiteboarding questions, make sure you practice at home writing code on paper and talking through problems. This is a skill that only gets better with practice. 

That’s all I have the time for (though if you want help or feedback on your resume, feel free to message me! I do this ALL the time for friends and for WiCS events)! 

I highly recommend this blog post by Andrej Karpathy. He’s a wickedly smart Computer Science Ph.D student at Stanford University. He’s doing a lot of research on computer vision and learning, which is the primary focus of my summer internship! These are his tips for success as an undergrad, but even if you are only in high school, they are still very applicable.

TDLR: 

Never underestimate the power of a good night’s sleep.

Make a test study schedule, even if you don’t stick to it.

Talk to your professors/teachers. Ask them questions, even if you think you know everything!

Cram!!! Start studying at least 3-6 days before the exam, but also revisit all the material 30-45 minutes before. Short term memory is wonderful.

Tip: study while listening to instrumental music or to some songs that are on a language you don’t know how to speak, this way you can’t get sing along and get distracted. French songs are my personal favourite!

Albert Einstein (via studentsandlattes)

I wish I felt like this. I used to love learning.

New Adorable Three Piece Rings Transform Into Animals Once Worn

Created by Bangkok-based artist Mary Lou (previously featured here), these adorable animal rings are worn separately to create the illusion of one full figure animal across your finger or multiple digits. Extremely adorable and dainty, the three-piece accessories feature a range of wildlife creatures found in the wild. You can find these super cute rings on the Etsy shop.