Mock Technical Interviews (&&&) A Story about Overfishing

It’s time to sign up for Mock Technical InterviewsSign up here.

Why should you sign up for Mock Technical Interviews?
If you don’t sign up for Mock Technical Interviews, it will be harder for you to get a job. And without a job, you wont have any money. Without money, no house. You’ll be living on the streets. Where you’ll probably catch malaria or be run over by a bus. Or something less morbid but equally negative in nature. Yep.
Sign up for Mock Technical Interviews; don’t be run over by a bus! Sign up here.
What are the actual benefits of Mock Technical Interviews?
Technical interviews are at the heart of the job and internship search. If you’re applying for a job that relates to programming, you’ll have to go through a series of technical interviews. They usually involve whiteboard programming — solving some problem by writing some code on the spot on a whiteboard — and practicing this makes a huge difference in your performance. Yep, you get better with practice. Crazy, eh?
When are these Mock Technical Interviews?
Various times on 2/28, 3/1, and 3/2 (Friday, Saturday, Sunday)
They’re in various rooms in the CS Building.
If you’d rather be the interviewer rather than the interviewee, go to the same spreadsheet and add yourself to the times you’d like to interview on the sheet called “Interviewers”.
Tell us a story?
There once was a small but well respected fisherman in the village of Thimble. Every morning he would go off to the Finger Lakes, and that was where he would spend his day. In the evening he would come home to his family, hug his tiny children, play the lute, write some code, and then lay down his bucket full of the day’s catch: hundreds of little fish. Why he did things in this order is a mystery to all.
One fateful day, our hero returned from the Finger Lakes with his greatest catch ever. One hundred forty little fish! This would feed Thimble Village for a week! (For Thimble Village was by no measure a large village.) The day after that our hero broke his fishing record once again. One hundred sixty little fish! The day after that, two hundred and eleven little fish! Thimble Village would never go hungry again! (He thought, not realizing this was a story about overfishing.) (The author wrote, not realizing this story would have a happy ending.)
Day after day, the fisherman of Thimble Village caught more and more fish. He was no longer a small fisherman now, but rather a mid-sized one, and a pleasing shape to boot. The Finger Lakes held only so many fish, and what this fisherman did not know soon would hurt him.
The fish ran out. The well respected fisherman of Thimble Village brought home the last fish from the Finger Lakes. With the only fish remaining, Thimble Village prepared fish fingers, and our hero never went fishing again. He had been overfishing, and now he was over fishing.
This is the bit where you get sad and resolve never ever to overfish as long as you live.
Fortune shined upon Thimble Village that day. The people of Sew brought over an Introduced Species which quickly repopulated the Finger Lakes and was super yummy. And everyone lived happily ever after.
Sign up for interviews! (link)
Posted in main | Comments closed

Microsoft Programming Competition

Show off your love for coding and your savvy problem solving skills! Teams of 1-3 people.
Compete to win $300
Make sure to bring your laptop, power cord, and your A-GAME!
February 17th, 2014 @ 7:00 PM CITP in Sherrard Hall
All contestants will be entered to win a SURFACE just for participating! Maximum participants will be capped at 50 people, so don’t be late!

2-17 Princeton Coding Competition Ad

Posted in main | Comments closed

February 21 Code@Night

Our next Code@Night will be on February 21. Location and details to be announced later.

Posted in main | Comments closed

AI: A Return to Meaning

Dave Ferrucci, Senior Technology Associate at Bridgewater Associates and the mastermind behind IBM’s Watson (which you may have seen on Jeopardy), will be joining us Feb 5 to discuss AI.

Wednesday Feb 5. 6pm.
McCosh 10

The practice of Artificial Intelligence has evolved from being predominantly theory-driven to being predominately data-driven. The best approach to building intelligent system design may be somewhere in the middle.

In this talk Dave will discuss the history of AI in terms theory-driven, data-driven systems. Dave will introduce the approach Bridgewater is taking to build an intelligent system that can dramatically improve the way in which a company models and reasons about how to manage people.

Posted in main | Comments closed

Teddy Bear Programming

Story time. Fiction. Based on real life.

Once there was a badass lab TA. Her skill was known far and wide. People from all over would come to her for help. And always they would leave bug-free.

“Please, I have a bug. Help me!” they would say.

And the lab TA would do this: She would hand them a teddy bear, and before she would so much as glance at their code, she would have them explain their problem out loud to the floofy bear. Most of the time, the bear found the solution on its own and the TA never even had to read the source.

The end.

Introducing Teddy Bear Programming, the latest and greatest Princeton ACM initiative.

Teddy Bear Programming aims to foster learning experiences and friendships centered around building cool things.

You can sign up for Teddy Bear Programming here:

What is it? It works like this: Two people get together and program something. One person serves as the main programmer and does most of the programming. The main programmer explains what they’re doing and why they are doing it as they program. If you’re the main programmer, keep in mind that your partner hasn’t seen your code before and it may look like magic to them. The secondary programmer sits back and watches. As the secondary programmer, ask lots of questions and make lots of suggestions. Don’t hold back; if you see the main programmer making a bug or don’t understand why they’re doing something or have an idea, no matter how silly, let the main programmer know.

We hope lots of Teddy Bear Programming pairs blossom from this experiment, and we hope it’s fun and a good experience for all involved.

Sign up for Teddy Bear Programming here:

Teddy Bear Programming FAQ:

What is the role of the main programmer?

The main programmer does most of the programming and explains what they do as they do it. It’s their project that you’re working on. They should answer any questions that the secondary programmer has. And they will take into consideration suggestions the secondary programmer makes. They will be supremely grateful for the eyes and ears of the secondary programmer.

What is the role of the secondary programmer?

The secondary programmer watches as the primary programmer programs. It’s their job to have questions and suggestions as the two of you pair program. They also take on the role of pointing out silly typos the main programmer might make as they program.

Don’t you think the term “secondary programmer” sounds inferior to “primary programmer”?

Maybe a little, but it’s not. I promise.

Can we call secondary programmers “teddy bears”?

Sure, I guess. Cuddling is optional.

How will we decide what to work on?

When people sign up to be the main programmer they will say what project they are working on. Then, we’ll send out the list of possible projects to all the secondary programmers and we’ll work together to try and find matches that are a good fit.

How long are Teddy Bear Programming sessions?

You should set aside 60 minutes for your Teddy Bear Programming session. But if you both want to keep programming for more (or less) time, by all means, please do so.

Should I be a main programmer or a secondary programmer?

Be a main programmer if you have a project that you want to work on already. Be a main programmer if you enjoy teaching. Be a main programmer if you want motivation to spend an hour working on a side project. Be a main programmer if you want practice programming while being watched, perhaps for interviews. Be a main programmer if you want feedback on your style of programming or on your project. Be a main programmer if you want a second pair of eyes and ears to catch your bugs. Be a main programmer if you want to meet cool people interested in CS. Be a main programmer if you want to help someone learn.

Be a secondary programmer if you want to see how someone else programs. Be a secondary programmer if you want to help someone with their project. Be a secondary programmer if you’ve always known you were a teddy bear. Be a secondary programmer if you want to get to know an interesting CS person better. Be a secondary programmer if you want to be exposed to a new language or a new type of programming. Be a secondary programmer if you want to know what’s possible in the world of programming. Be a secondary programmer if you want inspiration for your own side projects, or want to have a side project but don’t know where to start.

You’re welcome to be both a main programmer and a secondary programmer.

Who learns more, primary programmers or secondary programmers?

If I had to guess, I’d say secondary programmers. But it’s hard to say and probably varies from team to team.

Isn’t this just pair programming?

Yes. There are lots of types of pair programming though, and this is just one.

Will ACM pay for me to have coffee with my Teddy Bear Programming partner? Will you supply us with a real teddy bear?

We’re still working out the details here. Stay tuned.

Do you have any tips for how to be a good main programmer?

Always make sure you’re on the same page as your partner as much as possible. For instance, make sure they know what you are trying to do at all times by being explicit about what you are trying to accomplish.

What does all this have to do with overfishing?

It’s an ACM event. All ACM events have to do with overfishing. This makes searching for ACM events really easy; you just search your email for overfishing and *poof*, there they are.

How can I sign up for Teddy Bear Programming?

Sign up here.
Posted in main | Comments closed

Enterra Code@Night

We want to give a big thank you to Enterra for hosting our last C@N. It was a huge success. If you weren’t there on the 22nd, you missed a fascinating presentation on ontological networks.

You can make up for your absence by coming to the next C@N! It’s hosted by Tower Research, and it’s going to be so exciting that we can’t wait to see you there! In fact, we moved the date up because we couldn’t wait! The next Code@Night is Friday, December 6th in Sherrerd Hall from 9PM until late. Don’t believe me? Here’s proof.

Posted in main | Comments closed

The Yext Code@Night

We are excited to have a Yext themed Code@Night just around the riverbend.

Come to Sherrerd Hall, third floor on October 25 to celebrate the night with code and with Yext.

As always, Code@Night is 9pm to late.

Posted in main | Comments closed

Code@Night with Codecademy in Sherrerd Hall

Can a can can-can? No. That’d be ridiculous. Cans don’t have legs.

Code a code code-code? What? That’s even more ridiculous. It doesn’t even make sense.

Code at night at Code@Night with Codecademy? Ok, now you’re being reasonable.

Join Ryan Bubinski, CTO and Founder of Codecademy, for a Code@Night this Friday, October 11, at Sherrerd on the third floor from 9pm to late. is a website where millions learn to code interactively, for free. Check it out, and have your parents do the same.

RSVP on Facebook:

Posted in main | Comments closed

Code@Night at TigerLabs

This week’s Code@Night is coming up, and it’s at TigerLabs. :D

The address of TigerLabs is 252 Nassau Street, 2nd floor, Princeton, NJ, 08542 — it’s right by Ivy Inn and Hoagie Haven.

Come to Code@Night at TigerLabs on September 27, from 9pm to late.

We’ll have pizza, ping pong, and programming.

Perhaps this week we’ll order the pizza via our pizza-ordering Python script.

Maybe we’ll even get a totally random!

RSVP for the event on Facebook.

Posted in main | Comments closed