|
|
I remember them, the paper tapes. And also the HP "Moving Head" whith that time terrible big space of 10MB mounted in about 20 Inch racks
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Is the need for a distraction-free working environment really the reason for the strange sleeping and working habits of software programmers? "After midnight, we're gonna let it all hang down"
|
|
|
|
|
I thought it was because the best time to byte someone was at night.
Marc
|
|
|
|
|
I'm more of an early morning "owl" (while it's still dark). All my epic focus and creativity only happens at day break. The rest is noise and "inspiration".
|
|
|
|
|
I do enjoy working at night,but I don't prefer to do it regularly. Jaxenter: Successful development: really a 9AM to 5PM job? Now it does fit with regular corporate office hours too.
Wonde Tadesse
|
|
|
|
|
I'm a morning person. I screw my stuff up best before 10:00 A.M
|
|
|
|
|
I wouldn't mind shifting my rhythm with a few hours.
I already work 10 to 6 instead of 9 to 5, but I wouldn't mind 11 to 7
That probably won't go well with my employer though...
|
|
|
|
|
|
If I want a distraction free environment I'll work at home.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music."
-- Marcus Brigstocke, British Comedian
|
|
|
|
|
Cursor speed and precision link to anger and other negative emotions. Especially if the mouse is halfway through the monitor
|
|
|
|
|
For sure in a world where touch and gesture taking place of mouses...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
If you visit votetrump.com we know you're mad?
|
|
|
|
|
Do you mean:
- mad (crazy)
- mad (angry)
- both
- neither
- unsure
- all of the above
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
For such details I'll need your mousing behavior
|
|
|
|
|
Thanks to a new revolutionary laser printing nanotechnology, it is now possible to print this article in color on an area no bigger than a hair, say scientists. The ink cartridge will cost 120% of the price of the printer, however.
|
|
|
|
|
I need new glasses as it is man.
|
|
|
|
|
Cool!
I've got a couple of hundred mols of electrons going cheap. Unfortunately, I wont be able to supply the printing media at quite the same appealing low prices. 100nm structures covered with 20nm of aluminium icing are not exactly available at commodity prices.
|
|
|
|
|
Netflix has a solution for all the people who’ve fallen asleep while binge watching a show: DIY smart socks that automatically hit pause when they detect viewers have dozed off. Ladies and Gentlemen: your Nobel Prize winner!
(Probably for Peace, that one always gets the strange choices)
|
|
|
|
|
That would be the Ig Prize.
|
|
|
|
|
This version brings new tests to our existing tool, such as canvas and touch-capability fingerprinting, updating its ability to uniquely identify browsers with current techniques. You (or at least your browser) are a unique snowflake
|
|
|
|
|
Is there life after Agile? Agile principles may be too informal and artisan-based for today's complex digital operations. The nice thing about methodologies is that there will be a new one along in a few minutes
|
|
|
|
|
You know, the irony of all this is that software development is actually a highly social process, and a successful social process does not come about from formal methodologies but rather innate or trained social skills. Psychological skills like listening, non-violent communication, team building, etc.
Yes, processes are needed, but typically only when members in the process are corrupting the process. And therein is my estimation of the problem -- we, as humans, are usually not proficient at socialization. Or we come with our own agendas (and fears) that corrupt the process. Or frankly, both. The fourth kind is the worst, which any developer that prefaces his/her title with the word "senior" has experienced: a highly skilled anti-social engineer who manages (pun intended) to put forth their own agenda with varying affects, from disillusionment, "it's just a paycheck", to more devastating affects.
The one and only test you need that you are working with the latter kind is when he/she says "don't take it personally." Because a successful social process works only when people are personally vested in their own goals and accomplishments and the goals and accomplishments of the other people on the project.
The rest of us, what we need are less methodologies and more training in how to be functionally social, with the effect being that even fewer methodologies are needed. Yes, we still need to be skillful at our technical work, but if we don't figure out the social process, then everyone (the customer, the QA dept, the developer, the manager) will continue to create failed or mostly failed projects--either personal-subjective or product-objective or both.
The only way out of this loop is to develop social skills -- not the BS that management inflicts on you with week long "retreats" (if you are so lucky/unlucky) but real skills where we acknowledge each other as human beings with diverse and often divergent goals and at the same time agree to collaborate on something and have the skills to work out the differences that doesn't rip out the human in us but instead leaves us feeling validated, recognized, and with our honor and dignity, if not elevated, at least left intact.
Thanks for reading.
Marc
modified 20-Dec-15 18:55pm.
|
|
|
|
|
A superb response Marc where I found myself nodding in agreement pretty much all the way through.
My only comment would be that I'm not sure how you would teach social skills to those that require them. Some people find socialisation easy, whereas to others it is daunting or even frightening. I have met people who are naturally gregarious and outgoing, and also with those who are insular and withdrawn.
There's nothing intrinsically wrong with this, as everyone is different and we all shine in different ways. Every group needs a leader. The problem comes when the leader turns into a manager, and no one else in the group is able to stand up to them.
There is a distinction between a leader and a manager. A leader is someone who people want to follow (hence the term "leader"). A leader has the interests of the group at heart and wants what is best for the group as a whole. A manager has an entirely different agenda. They want what is best for themselves (or some other group that they represent) and have little interest in the group itself.
In a nutshell we need more leaders and fewer managers.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Very true!
I would add that all programming is a form of prototyping. In the hardware world, engineers and designers put their hearts and souls into a prototype. If you aren't willing to do the same for software, you should leave the profession!
That being said, there are times when, as a previous boss of mine put it, you have to "shoot the engineer" and get the product out the door. The name of the game is, after all, money, and it is sometimes better from a marketing viewpoint to release a product with missing features now rather than release a perfect product in a month's time.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|