Home sessions: A bitter pill to swallow
Hi again! I’m drained. Drained enough to sit here glancing at my computer screen with the hopes that I come up with a story good (and very short..) enough that will keep you glued for (just) a fraction of your life.
After successfully taking on a coding challenge and giving it the best I got, I’m happy to say that I’ve maneuvered around one of my biggest obstacles of Object Oriented Programming, properties. That’s right, those pesky, annoying little annotations that begin with @. Who comes up with this stuff anyway? The point is, (for those already lost in my lamentations), the reason I found them quite an obstacle was because I hadn’t really understood the concept of python decorators. I still don’t. Turns out I don’t really need to understand them to hit the ground running with properties.
Alright alright, I get it. You’re clueless to what properties are. Well I hope this chocolate crusted definition melts away in your mouth and leaves a permanent etch in your gray matter. Properties are just a way to help you get and set hidden attributes in your program without revealing the hidden attributes name. It’s not a perfect definition, but it is what it is. At least for me. If at any point you thought, hey buddy, your definition is way off and a tad too vague, then you really haven’t heard of the internet. Or how to use it.
I learnt through everyone else’s experiences that working at a computer under terrible ergonomics can dampen your mood. Today I learnt (the hard way) it can also cause back, neck, shoulder pains, headache, eyestrain and overuse injuries of the arms and hands. Don’t believe me? Let’s trade lives right now. Come on! What are you waiting for?
Before I take a nap and think about how I’m going to submit a real world problem modeled using OOP, I’d like to ask you something..
What would keep you up all night and not apologize for any ergonomic health issues if not the opportunity of a lifetime? Food for thought…