In the hobbit animation the animators mixed up the two blocks of runes on the map. They had the normal direction runes portrayed as the moon runes and the moon runes as the normal ones. May sound small thing to complain about, but it has bugged me for years.
I remember editing altchar.sys and changing the ascii chars to runes on the Z-100 so my folks couldn't read over my shoulder. Had to make up some characters that didn't match and I had my own numbers, but I got pretty good at reading them. Had to be in order to use WordStar, PeachTree, Condor rdms, etc. in green monochrome runes.
You mean I can't possibly accurately study DNA sequences from such a small sample.
You mean, I can't power an electrical device over xxx distance because the dispation is yyy.
You mean I can't have a glow-in-the-dark bunnywabbit because wabbit DNA does not code for luciferase and luciferin.
I couldn't possibly sue someone for creating an entirely independent work that is magically a derivitive of my own because a) it uses a file structure b) puts binary files in/usr/bin c) loads an operating system off a disk ala von Neuman. I can't possibly use the law for intimidation and evil.
I could not possibly sail that far without falling off the edge of the earth.
Oh, You mean I can't access this file because the operating system does not allow for it?
OHHH, ok...I can't do A because I do not have B, or because it is against the known laws of the world.
I see.
Well, good thing we are all content law-abiding reasonable individuals not inclined to skirt or bend the laws of man, or the universe or to change our world or feed an obsessive understanding of it such that enables utilizing parts of the universe for unintended purposes (and consequences).
I only hope we don't crash the system while hacking it.
Regarding the parent: the cheat would not necessarily to be to do it at high efficiency, but possibly a) make it not necessary, somehow skirting the requirement or b) using some other part of the system to help you out.
how much enegry it requires to bend space time. Its a crap load.
Unless you cheat.
Investors like to see geeks looking like geeks
on
Suit Up Or Ship Out?
·
· Score: 2, Insightful
The two successful companies I've worked for both settled on the general pattern of first sheltering the customers from the geeks while the geeks are being geeks. As soon as there is a weird technical problem, or the customers need to see a freak show, they are introduced to the technical staff. We have a few key customers who just eat up a team of us working on a problem, drawing on whiteboards, typing, and yelling down the hall, pointing at code, at each other, etc.
As for those companies returning to some dress code, where there is not proximity to the customer, you will find people who wear suits who are disturbed by other people who are not wearing suits. As far as I can tell, it's some sort of nakedness, protection and projected image thing. The suit-wearer may expound on how poorly the khaki's reflect on the company, but the body language will be the same as if you are geek-nekked. Yes, they are threatened by your 'leet-geek-nekked-ness, their inability to control it, and the fact that you are not hiding behind a suit like everyone else. Read "Dressing for Success" and some other books for the choices made when buying a suit and how/why the affect other people's judgment of the suit-wearer.
It works the other way around, as well. Many of the people I work with will distrust, either actively or passively, anyone wearing a suit. If you are wearing a suit, you are automatically categorized as shady, untrustworthy and probably criminal. Many of our customers wear suits when dealing with mgmt and sales. When it's a technical issue, they shift to kaks and polos.
The company I work for is seeing a backlash against the technical staff for perceived excesses during the boom. At least that's my best take on it. So now, the rats all have their swimming caps on, but aren't needing to jump, because other companies are flying helo's out to pick them up. In other words, we've got excellent people here with irreplaceable domain expertise, and we're losing them because upper management is trying to bf them. Yes, we're losing them in spite of the industry slump. Out of all those tech people in the world looking for work, our people are landing jobs. We're losing them for stupid reasons. Middle management is horrified because 1) their fief-base is eroding 2) upper management is doing and saying the weirdest and strangest things which are serve only to make software developers lives miserable at the company and 3) middle-mgmt is next. It's a software company, and a software company needs two things: product to sell, and sellers of the product. The dress code is just another way to reduce our ability to produce product.
The court protects publishing the source code from the injunction because it is expressive and not compiled. So, does commenting my code imply that the code is not as valuable or expressive as my comments, or does it improve the value of my code as a form of expression.
I guess it is clear that I should use meaningful variable names, write clear, intelligible readable code, and only hand optimize in the inner loops when/iff the compiler doesn't cut it.
Perhaps we should start a grass-roots, OpenSource Mars Probe effort. Rather then using WindowsCE, it can use embedded Linux. Navigation AI can be written as an Emacs LISP extension. Before entering orbit or aero-braking, we can disperse a constellation of Palm/ucLinux mini-probes to stay in radio contact with the probe while it is on the away-side of the planet.
In the hobbit animation the animators mixed up the two blocks of runes on the map. They had the normal direction runes portrayed as the moon runes and the moon runes as the normal ones. May sound small thing to complain about, but it has bugged me for years.
I remember editing altchar.sys and changing the ascii chars to runes on the Z-100 so my folks couldn't read over my shoulder. Had to make up some characters that didn't match and I had my own numbers, but I got pretty good at reading them. Had to be in order to use WordStar, PeachTree, Condor rdms, etc. in green monochrome runes.
-s
#include
/usr/bin c) loads an operating system off a disk ala von Neuman. I can't possibly use the law for intimidation and evil.
#include
#include
You mean I can't possibly accurately study DNA sequences from such a small sample.
You mean, I can't power an electrical device over xxx distance because the dispation is yyy.
You mean I can't have a glow-in-the-dark bunnywabbit because wabbit DNA does not code for luciferase and luciferin.
I couldn't possibly sue someone for creating an entirely independent work that is magically a derivitive of my own because a) it uses a file structure b) puts binary files in
I could not possibly sail that far without falling off the edge of the earth.
Oh, You mean I can't access this file because the operating system does not allow for it?
OHHH, ok...I can't do A because I do not have B, or because it is against the known laws of the world.
I see.
Well, good thing we are all content law-abiding reasonable individuals not inclined to skirt or bend the laws of man, or the universe or to change our world or feed an obsessive understanding of it such that enables utilizing parts of the universe for unintended purposes (and consequences).
I only hope we don't crash the system while hacking it.
Regarding the parent: the cheat would not necessarily to be to do it at high efficiency, but possibly a) make it not necessary, somehow skirting the requirement or b) using some other part of the system to help you out.
-s
how much enegry it requires to bend space time. Its a crap load.
Unless you cheat.
The two successful companies I've worked for both settled on the general pattern of first sheltering the customers from the geeks while the geeks are being geeks. As soon as there is a weird technical problem, or the customers need to see a freak show, they are introduced to the technical staff. We have a few key customers who just eat up a team of us working on a problem, drawing on whiteboards, typing, and yelling down the hall, pointing at code, at each other, etc.
As for those companies returning to some dress code, where there is not proximity to the customer, you will find people who wear suits who are disturbed by other people who are not wearing suits. As far as I can tell, it's some sort of nakedness, protection and projected image thing. The suit-wearer may expound on how poorly the khaki's reflect on the company, but the body language will be the same as if you are geek-nekked. Yes, they are threatened by your 'leet-geek-nekked-ness, their inability to control it, and the fact that you are not hiding behind a suit like everyone else. Read "Dressing for Success" and some other books for the choices made when buying a suit and how/why the affect other people's judgment of the suit-wearer.
It works the other way around, as well. Many of the people I work with will distrust, either actively or passively, anyone wearing a suit. If you are wearing a suit, you are automatically categorized as shady, untrustworthy and probably criminal. Many of our customers wear suits when dealing with mgmt and sales. When it's a technical issue, they shift to kaks and polos.
The company I work for is seeing a backlash against the technical staff for perceived excesses during the boom. At least that's my best take on it. So now, the rats all have their swimming caps on, but aren't needing to jump, because other companies are flying helo's out to pick them up. In other words, we've got excellent people here with irreplaceable domain expertise, and we're losing them because upper management is trying to bf them. Yes, we're losing them in spite of the industry slump. Out of all those tech people in the world looking for work, our people are landing jobs. We're losing them for stupid reasons. Middle management is horrified because 1) their fief-base is eroding 2) upper management is doing and saying the weirdest and strangest things which are serve only to make software developers lives miserable at the company and 3) middle-mgmt is next. It's a software company, and a software company needs two things: product to sell, and sellers of the product. The dress code is just another way to reduce our ability to produce product.
The court protects publishing the source code from the injunction because it is expressive and not compiled. So, does commenting my code imply that the code is not as valuable or expressive as my comments, or does it improve the value of my code as a form of expression.
I guess it is clear that I should use meaningful variable names, write clear, intelligible readable code, and only hand optimize in the inner loops when/iff the compiler doesn't cut it.
The engineers probably tuned the lander's radio to xxx in AM instead of FM or FM instead of AM. ;-)
We need to demand selective cookie control in our browsers!
It might be really cool to have a robotic snake prosthesis available!
Perhaps we should start a grass-roots, OpenSource Mars Probe effort. Rather then using WindowsCE, it can use embedded Linux. Navigation AI can be written as an Emacs LISP extension. Before entering orbit or aero-braking, we can disperse a constellation of Palm/ucLinux mini-probes to stay in radio contact with the probe while it is on the away-side of the planet.
What happened to bubble memeory?