Epiphany moments

A set of epiphanies

  1. Thinking about functions, while writing an application is as likely to lead to overuse of functions as overuse of objects. it’s all in the thinking habit more than in the paradigm(OOPS vs functional programming)

  2. Expectation management: is just a very crude, buzz word for referring to the practice of quoting/predicting/setting schedules/targeted time when others should pay attention to check/verify/test the result(i was tempted to say when others should expect, but yay, managed to avoid it).

  3. I definitely love attention of other people. Though it’s clear it’s not as simple as just liking it all the time. It seems there’s a temporal phase component(sine wave??nah.. am being too wishful.. prob. more complex, but good heuristic to start with). I wonder if there’s some number component tooo. i.e number of people who are paying me attention. past experience suggests that a big number > 50-100 is unnerving. Am convinced am comfortable at a number closer to 50. Though, i think that measure has another confound factor of strangers vs people i already know or have spent considerable time with

  4. When i hear about people not having official documents like DL, passport,etc.. my bias or sense of respect for them changes negatively it seems. though am uncomfortable with calling it sense of respect.

  5. Reading this post from Rushabh Mehta about going to or not going into sales <a href="http://erpnext.com/to-be-or-not.html"&gt; </a> Made me realise a lot of things. 1. Am not a product guy. because i can’t maintain that sustained focus irrespective of the rate/speed of feedback. 2. Am impatient and want quick/instant feedback. Maybe i can be the product guy for some type of apps, where there’s a very short feedback cycle, but for the most part i just am not that guy. 3. Not to mention the limitations of my own rationality. Am now very convinced of a career change.

  6. My auditory attention is untrained/under-trained. That’s basically why i have so much trouble in verbal communication clarity. i have to put deliberate attentional capacity to speech and listening that i don’t have any left to see the gaps in what i hear.

  7. With the request to change REST Api back to the standard http querystring parameter now i understand. It’s a waste of effort. But it’s ok because am paid a lot less than that .Net developer who has to learn json to consume my API. Darn it. that’s the end.

  8. I am beginning to realize, that the time to

  9. Looking for ahava* via the scientific method(<a href="https://en.wikipedia.org/wiki/Nullhypothesis">NHST</a>) might be craziest thing you ever do and is likely to render you peaceless and lonely for the rest of your lifetime…. But it does lead to an interesting life. *– Hebrew for love

  10. A good heart may be a necessary condition for a heroic/ethical/moral life, but definitely not sufficient. Infact, para-phrasing Million Dollar Baby show me a hero who’s all but heart, and i’ll show you a shooting star that’s gonna get 15 minutes of fame and then fade into nothingness.

  11. Life’s 99

  12. Before asking a question, think what you will do to find out the answer. In most cases, you’ll find that you don’t even care about the answer and asking the question is rather moot/pointless.

  13. the more specialized your role/expertise/area becomes the more your job becomes that of convincing a group of people to follow something or some way. The more i think or write about s/w architecture, the more i think it is about convincing people. than getting something done asap.

  14. the beauty of dynamic typing is also it’s bane. i.e: Not worrying about type conversions, can easily blow-up into badly designed code base, especially when you’re part-timing into a project.

  15. also just realized that vim addiction’s side effect. copy, paste without functionality understanding.

  16. Writing and building a s/w application from scratch is exactly like writing/proving a rigourous theorem.that’s why i got into it. EWD was right. but it is also a little masochistic and in the words of Hofstadter, yeah, the rest can be left to the rigourous mathematicians. that’s why i want to get out of creating software. i didn’t realize it before because, i never really created software at IBM. it is this epiphany that 3 years of working at IBM has cost me. and it is this epiphany i find the costliest of all prices i have paid in making that decision.

  17. Beginnig to get annoyed at vim at dealing with text and doing it great, but being crude like using a butcher’s knife at a neuro-surgery table. i really need to start using some other ide or consider emacs.

  18. Realize why function composition is such a good idea and very useful. in big projects with humongous code bases, chaining multiple functions is a necessity. Using a language that doesn’t design for it is painful for the same reason. And it’s for the same reason java and .Net shops are so big and hierarchical. And more importantly, slow or rather programmers who work in those languages tend to become lazy and have poor understanding of how the computer works.

  19. The browser is not a pure functional object. it provides lot of semantic ambiguities that are grounded in being designed for endusers, most of whom don’t know math.

  20. Very clearly, i have an overactive/ am over-dependant on ACC. it needs to be actively suppressing something pretty much most of the time. i am beginning understand the source of the bipolar lisp programmer internet meme and it’s appeal to so many other programmers.

  21. So does that part that is responsible for simulation(of any kind) of real-life experiences..

  22. Error handling in python is a pain if you set the value to None and check it everywhere. and a pain if you use try catch. in the first case you have to go catch the error at every function that calls a given function. in the second if there’s a failure, you don’t really get the stack trace of where it occurred only where the exception was raised/caught. Damn.. i can almost see why the either approach is haskell is better for the programmers. first thought is it works because of the type system. but would like to know more details than that.

  23. Another way to put venkatesh rao’s HIWTYL’s strategy is that people automatically assign higher malintention to errors of commission than to errors of omission.

  24. the more the number of states involved in your application the more the code base size in moving them around. The more the number of states in your application’s db design, the more configurable it is and that’s the core of the trade-off.

  25. creating separate python files to separate two different set of functions at the start of an application is a crazy idea(because it’s one of those naming issues, that’s neither here nor there and is only likely to confuse you in delivering the completed functionality).. You’re better off writing out all the functions required for the application functionality and then splitting them and renaming the files as necessary.

  26. Just when i was beginning to berate python’s philosohpy of reabability for not providing the ability to subtract two lists, i realize, i can use sets for the same purpose and there is a possible semantic confusion avoided by that policy. hmm… i think i understand the benevolent dictators attitude

  27. Am now tired of the multiple layers i have created for vip migration project. it doesn’t seem to make any sense to have so many layers.

  28. Problem with imperative programs?? One misplaced return function can waste half a day of a programmer’s effort, because it doesn’t throw any meaningful error/raise exception, but just returns.

  29. Copied music files to that dmguest user’s folder and realized, that i would like a progress bar like see on windows. then realized it’s not on linux, because the coding up something like that would be inaccurate,approximations and some assumption making guesses. Not sure why it’s not available as a cmd line?. thunar file manager has it and am sure other File managers have it too..

  30. Also am beginning to realize that i am probably not someone who can program(John Cook’s blog link: someone who can write large programs, with large probability of being correct). but more of a computer scientist in that context.

  31. Also perhaps, not for the first time, i realize i have been pathetic at quantitative analysis in my life’s past decisions. though i have been fairly good(read slightly above average/median) at qualitative analysis. Remember thinking i am good at managing globally but horrible at managing locally. Remember thinknig am good with global targeting?. Remember 9-10 years ago, deciding, i don’t want to go into a work career in my base degree, mechanical engineering? Remember regretting that even3-4 years ago, hell even now there’s a little wonder in how life would have turned out in that case. Anyway, the truth is it was a good decision in terms of how the market has panned out. i.e: the profit margins growing lower and lower on the ront of manufacturing.

  32. I want a programming language/framework/toolset, that lets me ignore the hacked up together technological mess that is the web,lets me focus on the problems and the math solutions to it, but doesn’t restrict my problem space. But guess what, there isn’t a reasonable compromise. Yesod + haskell seems promising so far, but not sure how it’s going to stand the changes over the next decade or so.

  33. ORM is a big fuck-up because it is a leaky abstraction. but more importantly, it’s leaks are not evident till you’ve invested long enough time in it, to waste. infact that’s pretty much the problem with learning new abstractions. you just can’t be careful enough with which ones you learn.

  34. You know, you’ve fucked up on organizing the code functions across files, when you want to find a function definition and are not sure, where it is. worse, when you start fearing having to search for a function name and not finding in the current file.

  35. ORM is a double jeopardy, actually, because it lets you pretend your tables are objects, which they aren’t. And then forces you to use the object oriented syntax for dealing with them. Duh….

  36. Infact the other jeopardy about object-oriented programming is that it forces you to think in terms of objects/data structures that can do stuff. So you when building an application you tend to think of objects/data structures as core and functions as support structures. it’s reverse. most of the time you need to figure out the functionality as you go. it means quick turn-around time. w

  37. Just had a simple trial run of geany. it’s cool i love the symbols bar on the side.. seems useful. pros: symbol table on the side bar cons: it opens a new terminal window on running, would rather use something plugged in the geany window itself.

  38. I name my functions trying to match what they do and find it a useful indicator that i have to break down the function into smaller ones. too long names are signs that am cramming too many things together.

  39. There’s a enchantment in listening to music in a language that you don’t understand. it’s a taste of the mystery and/or mysticness. listening to japanese music now.

  40. I can use the typeracer game as a test of how co-ordinated my visual attention and typing skills are and whether that leaves any attention level free for logical reasoning. that would be a good test to se e if i should do server admin stuff or development or just go home or just type out journal stuff.

  41. One more epiphany, today when raj asked whether i know C. ofcourse i learnt. i never used it professionally. but been playing around on and off on open-source C projects. and have found the linux C- development chain painful. but have a bad confidence issue that heavily undercuts my confidence level in C. partly left-over from living with brother and his ideas on how C user should be .

  42. Working only with python for a long time is likely to make you pick up bad thinknig habits. like preferring cute, short, readable code over clear, well-commented, efficient code. Am getting the hell out of python for some time now.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.