case: (Default)
Case ([personal profile] case) wrote in [community profile] fandomsecrets2014-01-25 03:42 pm

[ SECRET POST #2580 ]


⌈ Secret Post #2580 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.

01.


__________________________________________________



02.


__________________________________________________



03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.


__________________________________________________



08.


__________________________________________________



09.


__________________________________________________



10.


__________________________________________________



11.


__________________________________________________



12.















Notes:

Secrets Left to Post: 04 pages, 082 secrets from Secret Submission Post #369.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Re: Hawaii, Being a Military Brat, Programming, Trumpets

(Anonymous) 2014-01-26 01:07 am (UTC)(link)
How are you finding using PHP and Javascript for work? Do you feel like your classes were enough prep?
othellia: (Default)

Re: Hawaii, Being a Military Brat, Programming, Trumpets

[personal profile] othellia 2014-01-26 08:24 am (UTC)(link)
I like them. Sometimes it's frustrating how many extra tags and classes I have to output into things to get the Javascript to communicate right with the PHP and vice versa. It doesn't help that this start-up is really more of an evolution/expansion of an earlier, smaller product, so there have definitely been times where I've been like "Holy constructing ramshackle code on top of ancient existing code ruins because of deadlines, Batman!"

It'd be nice if I could get the time to go through everything again and reorganize it, breaking stuff up into modules that I wasn't able before because I had no idea what direction the project was heading. One of my coworkers got to start a new system from scratch and he's been doing it all in Python and says it's a lot cleaner.

As for classes being enough prep, I had a part time job at my university for a year and a half before I graduated and most of what I relied on going in and getting hired came from that job rather than any of my classes. But on the flip side, what I relied on going into my university job was the stuff from my classes, so half and half? My classes were good at teaching me the basic logic and fundamentals of programming, and my near minimum wage university job was good at honing and extending those skills by forcing me to program almost every single day.

IDK, I think that if I could change anything about my college education, I'd...

1. Cut out the bullshit classes. For every class I had where I learned new and helpful things, I had another one where we just went over the same stuff from three semesters ago (YES. I KNOW WHAT I FUCKING VARIABLE IS. YOU DON'T HAVE TO EXPLAIN IT TO ME IN A POWERPOINT FOR THE FIFTH TIME.) or basically read Malcolm Gladwell books for the whole semester or - in one infamous example - tried to learn how to juggle.

These were compounded by the fact that my major was technically 'Digital Media' which was like the bastard child of computer programing and art. (I technically started college with the intention of entering a 3D animation program, ultimately switching over when I realized programming was giving me infinitely less stress and 2D animation was always where my heart had been to begin with.) But yeah, so for every programming and bullshit class, there was also a third digital art/video/narrative class to go with them. Some were fun. (I did get to make a short Japanese squirrel drama in my sophomore year.) Some were painful. I currently use nothing of what I learned from any of them in my day to day job.

2. Restructure the one or two projects we'd have a semester and either make more checkpoints or transform them into some low key, let's-see-what-you-can-create-this-week creative programming exploration or something. Because practically no one, including myself, started them more than a week ahead of time. My first couple semesters I was really gung ho, but towards the end I started burning out. And when you only have one or two big projects a semester, you don't get as familiar with the code as you could. And there isn't really this desire to innovate when you can go "ooookay, that's enough for this project. done. turning this code in and never looking upon it again." So yeah, some incentive to just have fun with the stuff you're learning and trying new things just to see what might happen would've been nice. Maybe not for every class, but just for some variety.

Sure, my job is all mini-projects and deadlines now, and being able to pull an all-nighter and crank out that code is a really valuable skill... but more than anything it's pacing, and getting through things one step and one day at a time, and never really having a predetermined solution of "this is how I solve this problem in front of me", and not being able to just shove my code off to the side and start afresh every month...

And for those things, my classes were not very good prep at all.

(This got kind of long, didn't it?)