Till today I didn't know that following are real language. I heard these words from experts.....thought Ummm nice synonyms....but in reality
There is a complete wikipedia about this....
The brainfuck language is an esoteric programming language created by Urban Müller in 1993 noted for its extreme minimalism. It was designed to challenge and amuse programmers, and is not suitable for practical use. Its name has been variously bowdlerized, as in brainf*ck or brainfsck, since its name contains the expletive "fuck". The name of the language is generally not capitalized, despite the fact that it is a proper noun.
This language, Boolfuck, is based off of the programming language Brainfuck, for which it is very difficult to write useful programs. There are very few differences between this language and Brainfuck; the primary difference is that Boolfuck works with bits instead of bytes.
Brainfork was conceived during a german lesson in High School. As the teacher spoke his words of wisdom for hours on, the brains of the architects behind the language was beginning to slowly wear down to a state where only fundamental thought routines could persist. But then, all of a sudden, lightning struck. The beautiful Brainfuck language was thus extended to include yet another instruction: fork
There is a complete list of implementation...programms and other's...
Interesting isn't !!!!!!
Vivek
Labels
- A Curate's Egg.... (1)
- Artemus Ward once wrote (1)
- Beauty lies in the eyes of Beer - Holder (1)
- Boolfuck and Brainfork... (1)
- Brainfuck (1)
- Cricket is Killing... (1)
- Design Rules..... (1)
- Geeks and Nerds Need To Work Happily (1)
- Happiness....Let' search...can we (1)
- Help yourself (1)
- Monster (1)
- Programmer vs. Developer ... (1)
- Some things I’ve learned from TV (1)
- six Wonderful Google Games To Keep You Entertained (1)
Tuesday, April 10, 2007
Things to Say When You're Losing a Technical Argument...
Mr. Bad and Crackmonkey collaborate on a fine Mr. Bad's List
I believe I've hearing most of them - following are the great and get use to of listening them
I believe I've hearing most of them - following are the great and get use to of listening them
- I agree that it works in practice, but does it work in "_theory_" ?
- I had the same thought ?... Ugh, I hate that one.
- Yes, well, that's just not the way things work in the real world.
- I like your idea. Why don't you write up a document and we'll review it at the next meeting?
- That won't scale.
- I think you need to stop taking this so personally. We need to think about what's best for the project, not about our own little pet theories.
- Have you LOOKED at the number of I/O requests that will create?
Monday, March 26, 2007
Monster
Wednesday, March 21, 2007
A Curate's Egg....
I was just reading an article and in meantime I got a call from one of my colleague installing my fixes at customer site. He told me "My fixes works....but not fully....fixes have spoiled existing working configuration" .
Same sentence can also be expressed as "Somewhat of a curate's egg, I'm afraid; the fixes was working, but with full of exceptions in it."
What I want to say is: there is a expression in english "a curate's egg" which is used for the above mentioned scenario.
I checked in wikipedia and found following description:
Expression "a curate's egg" means something that is partly good and partly bad, but as a result is entirely spoiled.There were many pepole who doesn't know this word and there are many peole who use this.
Just like the word "A curate egg"....
Same sentence can also be expressed as "Somewhat of a curate's egg, I'm afraid; the fixes was working, but with full of exceptions in it."
What I want to say is: there is a expression in english "a curate's egg" which is used for the above mentioned scenario.
I checked in wikipedia and found following description:
Expression "a curate's egg" means something that is partly good and partly bad, but as a result is entirely spoiled.There were many pepole who doesn't know this word and there are many peole who use this.
Just like the word "A curate egg"....
Tuesday, March 20, 2007
Design Rules....
As as programmer I always struggled on design document. Sometimes the document are mixed with languages and sometimes the whole story has been cut-paste.
#1. Talent is one-third of the success equation...Hardwork and luck is also needed
#2. 95% of any creative profession is shit work ...rest 5% is fun
#3. If everything is equally important, then nothing is very important.
#4. Don’t over-think a problem.
#5. Start with what you know; then remove the unknowns...Draw what you know.
#6. Don’t forget your goal...
#7. When you throw your weight around, you usually fall off balance.
#8. It all comes down to output and the rest of the world counts.
#9. Its not a novel its a document somebody gonna read it.
This is very well applies in software design...I don't know if it make sense in other field ?
#1. Talent is one-third of the success equation...Hardwork and luck is also needed
#2. 95% of any creative profession is shit work ...rest 5% is fun
#3. If everything is equally important, then nothing is very important.
#4. Don’t over-think a problem.
#5. Start with what you know; then remove the unknowns...Draw what you know.
#6. Don’t forget your goal...
#7. When you throw your weight around, you usually fall off balance.
#8. It all comes down to output and the rest of the world counts.
#9. Its not a novel its a document somebody gonna read it.
This is very well applies in software design...I don't know if it make sense in other field ?
Happiness....Let' search...can we
I think happiness and satisfaction are synonyms of each other.
I just had a discussion with one of my support colleagues and I told him "You will never be happy if you continue to search for what happiness consists of
"Actually, Success is not the key to Happiness, Happiness is the key to success.
I had a colleague, He is happy working on "C", because its a new challenge. Me as a programmer not happy working on technologies like "unifAce" and I have a Colleague, he accepted recently an offer to work in "unifAce". The point is if you love what you are doing, you will be successful, satisfied and happy.
There is also a perception to copy a happiness. I guarantee you....You will never win.
One of my colleague told me "Action is the happiness". "Action may not always bring happiness, but there is no happiness without action".
Wow....Look so different way to be happy. Look at the picture....Perfect example of happiness
I think, there is only one happiness in life, to love and be loved. ...That's the one which is very real and everybody wants more of it....
Tell me what u think ?
Geeks and Nerds Need To Work Happily
There are many reasons to let geeks work the way they want to work. Today they work in every industry. They are the knowledge base, blood and sweat equity of many businesses. They work harder than most. They work longer than most.
Geeks work almost every moment they are awake. They are online before they go to the office. They are home working after the office closes. They work weekends. They are even sometimes working in their dreams.
#1. Let them work when they want
#2. Let them work where they want
#3. Let them control their lighting
#4. Let them wear Headphones
#5. Do not expect them to wear a suit
#6. Do not make them participate in company events (!= geek-friendly)
#7.Do not hold a lot of meetings that could have otherwise been handled through email
#8. Do not make them do anything other than work
#9. Do not force them to do something
"A person often of an intellectual bent who is disliked"---Its a Geek
"In a meeting full of pepole talking about release plan or business policy and you see a person writing algorithm, drawing diagram, writing mathematics theorem or solving sudoko"... I tell you the guy is a geeky.
I hope you understand the world of geeks and how to identify them , and how to keep them happy in my words....
Tell me what you think ?
Geeks work almost every moment they are awake. They are online before they go to the office. They are home working after the office closes. They work weekends. They are even sometimes working in their dreams.
#1. Let them work when they want
#2. Let them work where they want
#3. Let them control their lighting
#4. Let them wear Headphones
#5. Do not expect them to wear a suit
#6. Do not make them participate in company events (!= geek-friendly)
#7.Do not hold a lot of meetings that could have otherwise been handled through email
#8. Do not make them do anything other than work
#9. Do not force them to do something
"A person often of an intellectual bent who is disliked"---Its a Geek
"In a meeting full of pepole talking about release plan or business policy and you see a person writing algorithm, drawing diagram, writing mathematics theorem or solving sudoko"... I tell you the guy is a geeky.
I hope you understand the world of geeks and how to identify them , and how to keep them happy in my words....
Tell me what you think ?
Subscribe to:
Posts (Atom)