Recently, a favorite band of mine named “Blaue Blume” have released their new single, called “Macabre”. (Go ahead and listen my Blaue Blume playlist!) And you know, you get goosebumps and tears (I think that would make a great band name btw) when you hear/see/experience something truly beautiful. Well.. that happens to me a lot when I listen to this great band from Denmark.
The thing is, they made me appreciate music a lot more. Also, isn’t it weird that among all those songs/albums released, we love only a very small subset of them? It’s like we all have some neural networks that are initialized with random weights and in the end some songs make our neurons fire and some do not.
And then I watched this old video from Vsauce (It’s been 5 years wtf!?):
Is the number of all possible songs uncountably infinite? Please go ahead and enlighten me about the countability of all the possible music we can produce/generate. In any case, the number of all the music scores we can compose is pretty big. Yet, we seem to be interested in only a really small subset. And maybe we can use this knowledge to create better compression algorithms? And yes, I do know that we get rid of less audible sounds and kinda fine tune the audio signal for human ears, thanks to psychoacoustics.
Also, are there any other life forms who appreciate sound waves? They may be totally unresponsive to them I guess.. What do they do to wind down after a long day? I think I will be long dead when we get answers to these questions and that sucks.
Hmppfssss.. whatever, go ahead and listen to this great band and have a great day! 🙂
As Joel Runyon states in his blog, the impossible list is more like a collection of challenges rather than a bucket list, and it should contain the things you never thought that you’d be able to do. It is completely fine if you wanna reevaluate and alter your list later.
Also, if you happen to have a impossible list, please share it by leaving a comment.
Here is mine:
Move to another country
Own a Tesla Model S
Volunteer for an organization for a year
Visit Every Continent (North America, South America, Europe, Asia, Australia, Africa, Antarctica)
Visit Japan! ^ __ ^
Visit Universal Studios, Orlando / Harry Potter World in London, UK
Climb a volcano
Be an extra in a movie/tv series
Take part in a photoshoot of a brand
Get to space OMG * _ *
Events to Attend:
The Cranberries concert [July 22, 2010, Istanbul]
See the Northern Lights
Meditate 10 mins every other day for 6 months
Workout 3+ days/week for 6 months
Draw something everyday for a month
Draw something I’d be proud to sell on RedBubble
Do 10 DIY projects
Learn to draw
Build a robot
Become fluent in English
Become fluent in Japanese
Become fluent in French
Develop a game & put it on Steam
Start a startup!
Create an apparel line
Become an economically self-sufficient jobless person & do what the eff you want
On the first day of my job, Aug 5th 2014 to be exact, which also happens to be the starting point of my first working experience in a.. ehem..“professional” environment, I gave myself a promise:
“I will not become that person who hates his/her job..someone absorbed by corporate life so much that he/she becomes a soulless person.”
Reader:“Wow, this is kinda childish.. Is this actually a line from a shounen anime haha..”
Sooo.. this idea struck me recently. I truly feel like I’m losing my genuine self and it feels awful. 😦 Yesterday I caught myself behaving unnecessarily impatient and aggressive about some issue.. I immediately tried to rollback to “real me”, but this whole thing got me perplexed.
That was not me.. such an attitude was not constructive, not at all. Why would I stress about something that is so insignificant? It is just a task after all..
I don’t know. Maybe it is disgusting office politics, maybe it is due to my manager’s invasive and abusive attitudes, maybe it is being “professional” as Linus Torvalds himself explained here.
I am not happy, and I think I have legitimate reasons for that. For example, why would some group of people, who are on the higher steps of hierarchy, decide to hire someone after testing his/her skills and then do not let them do anything without their approval ? …*crickets chirp*… I honestly cannot comprehend.
Reader:“Aaaah.. The good old micromanagement..”
*Darth Sidious voice* Yeeees.. But let’s talk about that later.
Soooooooo..I feel like my creativity is slowly being extinguished and I’m losing my authentic self. I need to find a new job that is much more employee-friendly and humane.
In PostgreSQL, every function has one of the possible volatility classifications: volatile, static and immutable. When it is not specified, PostgreSQL assumes that it is a volatile function, which is not always the case.
Volatile: functions with side-effects. Immutable: pure functional functions. Stable: smth in between. (wow, such explanation, very clear *applause*)
Yes, IMHO stable is utterly error-prone and you need to consult to the documentation. Sorry that TL;DR was inadequate 😦 ..(but.. it is supposed to be inadequate by definition right?? whatever..)
So, I’d like to draw your attention to immutable functions before this post gets too long. When declaring a function, using the immutable keyword actually implies the following:
I solemnly swear that my function does not modify the db.
It does not do any database lookups.
Given the same arguments, it ALWAYS returns the same output.
BEWARE: As stated in the PostgreSQL documentation, your function should be volatile if you use anything like random(), currval(), timeofday(), current_timestamp(), etc. in your function.
Reader:“So, like.. when shall I use immutable functions? “
Recently, we had to implement a hash function and it was much more appropriate to do the job in PL / pgSQL. So it was all sunshine and lollipops, the hash function came out well etc. But unfortunately it was a tad bit slow. To fix this issue, we just altered the volatility classification of some helper functions. For example, a function that converts characters into ascii values was perfectly suitable to use the immutable keyword!
*Reader: ughh the obligatory ‘I hate agile, it is useless’ post again..*
Sooooo, it’s been like a year and a half since I have started working in a professional working environment and I have yet to understand what story points stand for.
“It’s not about the time, it is about the effort!” Yeah, I have been warned about this many times already. And as team members, we do not necessarily have to agree on the effort of a story either.
The other day I was trying to load 700k records from a database using a tool called datatables and ajax server-side processing. For the record, I am eager to learn new technologies but my learning curve is kinda pathetic. I am just a junior and I have been hired as a C++ developer. Whatever, I took the task with the hopes of learning something new..
*3 days later* *Meanwhile, we put cute little dots on post-its..*
PM:“Sooo.. what have we done concerning this task?” Me:“Well..erm.. I am done with loading the records, I have managed to fix that bug bla bla. But we can’t insert/delete/search yet. But the rest should be easier as I kinda understood how datatables works.” PM:“*not pleased* hmm.. ok, but we need to finish and deploy it asap. It is a 5-point task, can you add insertion/deletion mechanisms today?”….
Then he begins to creep on my screen every now and then..
I’m sorry, wut? – _ –
OK, I get it the team gave that task 5 points in the meeting, and I respect that ofc. But instead of a much more experienced team member, if I take that task, it will naturally take much more TIME & EFFORT. Considering every one of us is a unique being, what is the point of story points? Is it merely a tool for managers?