Things Programmers Comment #60

Computer Science

*screams into the public static void*

Here is thing I learned when I was 29, which I now give away for free: If you want to do a thing, do it now, or as soon as feasible. Because there might not be a later. If it is a complicated or expensive or hard thing that takes many stages or has a steep learning curve, start working on the parts you can work on while you can work on them, then move on to the next thing. Accept that there will be a lot of failures along the way, and that you can come back from nearly any mistake that doesn’t involve making a left turn in front of an oncoming semi. Concentrate on yourself and what you can do, and don’t rely on other people to fix things for you, even though you might love them or they you. (This doesn’t mean you can’t love friends or family or partners. Friends and family and partners, in the long run, are the thing other than Useful Work and Adventures that make life worthwhile. Well, all that, and a really nice coffee and tea kit in the kitchen and the skill to use it. But that last thing isn’t terribly expensive unless you make it be.) But to succeed at a thing–a job, a relationship–in the long term, the thing is: You Must Commit, even though commitment is scary. And commitment is scary because once you’re in you’re in. It’s not bobbing around close to the shore, paddling with your feet. It’s both feet and swimming as hard as you can out where the rip currents and the sharks are, where the water turns blue. You can’t hold back because you’re afraid of getting hurt: you have to accept that you are going to get hurt, and put your hand in the fire of your own free will. It’s like climbing. You can make sure you’ve got good ropes and a belayer you trust (you SHOULD make sure you have good ropes and a belayer you trust!), but there’s moves you can’t make unless you’re willing to risk falling. I’m not saying follow your bliss off a cliff, in other words: part of being prepared and committed is having the right kit, whether it’s money in the bank for the lean times when starting off as a freelancer, or a partner who supports your work, or being young enough that starving in a cold room for a few years with pneumonia is romantic (I have the T-shirt!). That’s why it’s scary. It’s scary because you are taking an actual chance. But: things don’t work out the way you want them to if you just kind of drift along seeing what will happen. Nice things might happen! …but they didn’t, for me. Basically, what I figured out was that I had to be a protagonist if I wanted anything to happen, and part of being a protagonist was accepting that I might fail. And then have to deal with that failure. And that if I didn’t do it I would more or less inevitably fail, but I could pretend to myself that it wasn’t because I wasn’t good enough and that I didn’t know why. Seeking success, in other words, meant letting go of a layer of ego defense. This realization directly led to me having the career I always wanted, and doing pretty well at it. It also led to me having the best relationship of my life. I wish I’d learned it when I was sixteen, rather than twenty-nine, but I had some things I had to work through first. 

So that thing you want to do? Assuming it’s not illegal or immediately fatal? Do it now.

“We are assuming here that the user is competent. In reality this is always false. Users are very dumb and will do weird things.”

Intro to Computer Programming Professor (via mathprofessorquotes)

Did you know that 2015 equals 11111011111 in binary, a palindrome?

Oh, and by the way, on May 15th, 2015 at 02:09:25 UTC, Unix time will be 1010101010101010101010101010101.

Making changes to the live site.

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

Computer Science

*screams into the public static void*

tumblrfolk, we are so much more skilled than we think

one thing I want to say today relates to my current job. (As you guys know, I’ve left off working in science labs to work an office job in sci comm. My role is kind of … nebulous and involves a lot of “oh, Elodie can help you with that, she does weird stuff. Train Elodie on that.”)

Because it’s an office job, the mentality is for everyone to present their workflows as incredibly difficult and skilled, requiring a lot of training and experience to do properly. Which is fair enough! These skills are difficult!

“Elodie, today we are going to train you to use… A HIGHLY COMPLICATED AND DIFFICULT WEBSITE INTERFACE. You will need to take a lot of notes and pay careful attention, because it is extremely advanced. ARE YOU READY”

“… This is Wordpress.” “…No it isn’t! it says something different at the top. And it’s very complicated, it’s not something you can just know already.” “Nah son, don’t worry, it’s Wordpress. I mean, God knows I don’t blog much, but I can manage me a bit of Wordpress, it’s cool.”

“No. You can’t. Don’t worry, it’s very difficult. Now sit still and be trained on how to upload a photo to Wordpress.”

“All right.”

—-

“Elodie, do you think that you can MANAGE SOCIAL MEDIA? It is INCREDIBLY HARD and may involve THE HASHTAGS”

“… I think I’ll manage.”

—-

“Elodie, can you put a HYPERLINK in a thing? Think about it before you answer.”

“Is it like a BBCode kind of thing, with the boxy bracket things, or do you want it in HTML, with like angley bracket things?”

“It is a button that you press that says HYPERLINK.”

“I can do this thing for you.”

—-

“Elodie, can you write a punchy summary that will make people want to click on a special link that says “read more” to read all of the text?“

“Probably?”

—-

“Elodie, this is how to use TAGS on CONTENT. TAGS on CONTENT are important because - because of THINGS. Things that are too arcane and mysterious for anyone below the level of Manager to know.”

“Cool, I can tag stuff for you.”

—-

“Elodie, this is obviously a ridiculous question, but can you edit videos?”

“Not very well, and only if you want to make it look like there is sexual tension between characters from different forms of visual media, or perhaps to make a trailer for a fanfiction? Which is not necessarily a good use of my time and I’m not sure why I felt it was so cool to do to begin with…”

“What?”

“Actually, upon further reflection: no. No. Nope. I can’t edit videos. They’re completely beyond me. Not in my wheelhouse. Hate videos. Hate them. No innate skill whatsoever.”

“That’s what we thought”

—-

“Elodie?! You can use PHOTOSHOP?!”

“Yeah, I mean, I usually just use Pixlr. It’s free, it’s online, it’s powerful, you don’t have to download anything…”

“but you are not a GRAPHIC DESIGNER!!” “Er… no.”

“Next you’ll be telling us you can MAKE AN ANIMATED PICTURE.”

“I mean, I haven’t really done a lot of it since Livejournal, and they weren’t that good anyway, but yeah… I can do you reaction images.”

“THAT IS WITCHCRAFT”

“Yes. Definitely.”

—-

What I’m trying to say is: a lot of people talk a lot of crap about what we Millenials do on the Internet, because there is NO CAPITALISTIC VALUE in the screwing around we do with our friends. “Ughh why are you ALWAYS on the computer?” our parents whined.

“How did you make the text go all slanty like that?” our bosses wonder.

We have decades of experience in Photoshop. We know how to communicate; we can make people across the planet care about our problems. We know how to edit media to make two characters look like they’re having the sexual tensions. We can make people read our posts, follow us, share our content. We run and manage our own websites - and make them pretty. We moderate conversations, enforce commenting policies, manage compromises, lead battles, encourage peace, defend ourselves from attack, inspire others, and foster incredible levels of communication.

We produce our art. We advertise our art. We engage with others through our art. We accept constructive criticism and dismiss destructive trolling of our art. We improve our art. Our art gets better.

We narrate our stories.

All by ourselves. Our pretty blog backgrounds, custom-edited themes, tasteful graphics, punchy content, clever gifs, our snappy putdowns and smart-ass text posts, even our familiarity with fonts and composition - all of these skills we’ve casually accumulated for fun/approval are MINDBLOWING LEVELS OF COMPETENCE IN THE WORKFORCE.

When these skills are sold to you - when they’re packaged and marketed, and when you pay to consume them and have the Elders rate you on them - they are incredibly valuable. They are Media and Communications degrees. They are marketing internships. They are leadership workshops. They are graphics design modules. They are web design courses. They are programming courses. We are good at this shit; we have it nailed down.

You can’t put “fandom” or “blogging” on your CV, but you deserve to. You should get this credit. You should claim this power and authority.

Claim these skills. They are valuable. They are important.

Everything you have ever done is a part of your powerful makings.

Don’t let your idea of who you are become a prison. 

Meet yourself anew every morning.

Allow change.

Allow growth.

Allow yourself to become.