|
It turns out you don’t have to be employed as a programmer to use programming at your job. Necessity is the mother of invention.
|
|
|
|
|
Quote: I spent the next four days surfing the web
Unless he was on Code Project, I don't think he's cut out to be a real programmer.
Terrence Dorsey wrote: Necessity is the mother of invention
And the father is Tesla.
|
|
|
|
|
Did he just realize that? 
|
|
|
|
|
"When I was a college student, I spent a few summers working at a law office as a file clerk. Basically, the job was as boring as it sounds: get requests for files from the file room, physically sort through boxes, pull out said files, deliver them. Occasionally rearrange the entire file room to accommodate more boxes."
Even before programming, the guy was the file server for the firm!
Rearranging the file room? That sounds like a database reload.
|
|
|
|
|
My goal for Johnny-Five is to create a framework for programming Arduino Robots with nothing more then JavaScript. I believe that JavaScript, inherently asynchronous and the platform that Node.js has built around this paradigm, is the perfect environment for writing evented, streaming programs for controlling the highly synchronous world of hardware. The 4th rule of robots: program them in the language you like best.
|
|
|
|
|
NO NO NO NO, this is the stuff of nightmares!
|
|
|
|
|
Many people don’t expect pairing, itself, to be a skill. They don’t realize that they’re going to have to learn new ways to think, to problem solve, to be creative, to filter their perceptions, and even to converse. Since they don’t realize this, they get surprised. And then they set themselves up to make that learning hard, and quit when they get poor results and find pairing to be hard while learning. It takes two to tangle.
|
|
|
|
|
I've never really used it beyond a couple projects at school, but I hate pair programming. Mostly because I hate having someone looking over my shoulder. Only in the physical sense though, something about having someone looking over my should just makes me freeze up. If what I typed was duplicated to another monitor somewhere not directly behind me, or something to that effect, I'd be fine it.
|
|
|
|
|
It sounds ridiculous. I've never done and I don't expect I ever will.
Frequent code reviews make more sense.
|
|
|
|
|
it really suits me. My creative reasoning really comes alive when I'm involved in a conversation. Compared to solo work, working in a pair lets me do like 80% of the feature count in the same elapsed time, with 1/50 the bug count.
|
|
|
|
|
I suppose I'd have to give it a longer try. Recently, I spent most of a day trying to figure out something with a coworker. Then I spent an hour after work and I'm pretty sure I got it solved. Though, that may just be because I had enough preparation with the coworker that I had everything I needed to finish solving the problem. I'm not sure.
One thing I did notice though was that we each learned a few things. He learned some ways of doing things in LINQ and how to better use Umbraco (a CMS we use), and I learned a few things about our infrastructure at work (and how frustrating parts of it are).
Another thing I noticed is that I was mentally exhausted at the end of the day. I went home, fell asleep immediately, and woke up 9 hours later (which happened to be 4AM)... that never happens to me (if I go to sleep early, I usually wake up in a couple hours). I think the experience basically kept me mentally engaged all day, which is why I was so tired.
One downside I saw was that, when sitting next to somebody, you don't really have the opportunity to stare into space for a few minutes considering the problem. It'd probably be good to take breaks on occassion, if only to think to oneself.
|
|
|
|
|
It's bloody awful: complete waste of time unless you have one submissive and one dominant person and then the dominant person always wins.
Tried this about 20 odd years ago and nearly killed each other. Got to the point where I couldn't even look at him without wanting to punch him and I'm pretty sure he felt the same way.
You don't get two for the price of one, you get one for the price of two. 
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
CoffeeScript has a number of other nice features, and it's always evolving. I understand that some people simply don't like it, which is fine, since a lot of what it offers is subjective. However, I'm baffled that people dismiss as being nothing but syntactical sugar. It's less verbose and improves readability. That's a win in my books. What do you like - or not like - about CoffeeScript?
|
|
|
|
|
Syntactical sugar?
Hey, I take sugar with my coffee! 
|
|
|
|
|
In Architectural Smells I argued that there are architectural smells in the same way that there are code smells (aspects of a system that indicate but not guarantee a possible issue) and the example I gave was caching. I also think that VM size is an architectural smell. 4GB ought to be enough for anybody.
|
|
|
|
|
For a long time, some Microsoft officials have privately griped that PC makers don’t present Windows in its best light. They clutter desktops with icons that are often little more than ads for third-party products; include confusing utilities that duplicate functions already in Windows; require lengthy setup; and configure PCs in ways that slow them down. Signature PCs get rid of the bloatware... for a price.
|
|
|
|
|
DJ Sures, mastermind behind the EZ-B Bluetooth Robot controller, sent in a really interesting build where he controls a robot with a 1983 TRS-80 computer. The robot in question is [DJ Sures]‘ adorable WALL-E we’ve seen before. WALL-E takes out the TRS-80.
|
|
|
|
|
Once you’ve mastered a particular language, you’ve also mastered a means of thinking. You understand how to decompose a problem into knowable units, and you learn how to intertwine those units into pleasant and functional flow. There is no doubt in my mind that this is an essential and valuable skill for anyone to learn and master. However, there is a language you could master that teaches many of the same lessons, appears far more forgiving in terms of syntax, and has immediate broader appeal. The language you can learn is your own. Writing is the connective tissue that creates understanding.
|
|
|
|
|
The best argument for learning to code appeared this morning, when it turned out that Judge William Alsup in the Google case could program, and learned Java in the course of the trial, and wasn't going for Oracle's claim that a short range-checking function was days of work. I object(!);
|
|
|
|
|
Server teams are made up of the people who write and maintain the code that makes servers go, as well as those who keep that code working. When things go right, nobody notices, and they get no praise. When things go wrong, their phones ring at 3 in the morning.... It's a thankless job. Sysadmins of the world, unite!
|
|
|
|
|
It's time to hook your WiFi up to "t-rays"[^]. Well, it will be once they iron out wrinkles and scale it up.
|
|
|
|
|
Microsoft is changing their Visual Studio 11 User Interface[^] because of all your whining and complaining.
Thank you.
m.bergman
For Bruce Schneier, quanta only have one state : afraid.
To succeed in the world it is not enough to be stupid, you must also be well-mannered. -- Voltaire
In most cases the only difference between disappointment and depression is your level of commitment. -- Marc Maron
I am not a chatbot
|
|
|
|
|
A couple of points.
1. This story has already been covered here in the Insider News, as well as being done to death elsewhere on the forums.
2. People did not whine and complain about the interface. They raised legitimate concerns. Treating them as though they are petulant children who can be talked down to is the type of condescension that got Microsoft into this trouble in the first place. When a seasoned professional who uses your tools all day long tells you that you are going to make them less productive, you'd better believe they have valid reasons and that, perhaps, you don't know better than they do.
|
|
|
|
|
A couple of rebuttal points.
1. I have not seen this story covered or anyplace else. I don't generally go to the soapbox so it may have escaped my attention there.
2. I am with the whining and complaining group regarding the VS11 interface. I think I've even posted by objections to it around here someplace. Microsoft has always talked down to the developers. I still remember those helpful diatribes from Mike Blaszczak in the golden age of MFC. Frankly, some developers need to be talked down to, that is to say, they need a little humility.
3. Finally, I wasn't concerned with the changes so much as the article itself: how it was written, its choice of words. Hence, the title of my message. I am just so impressed with how opacity of the language used by some "technical" writers, specifically, the use of "high energy" and "low energy" as opposed to "exciting" and "boring".
m.bergman
For Bruce Schneier, quanta only have one state : afraid.
To succeed in the world it is not enough to be stupid, you must also be well-mannered. -- Voltaire
In most cases the only difference between disappointment and depression is your level of commitment. -- Marc Maron
I am not a chatbot
|
|
|
|
|
Michael Bergman wrote: 1. I have not seen this story covered or anyplace else. I don't generally go to
the soapbox so it may have escaped my attention there.
In this very forum. Link[^].
It was also posted out in the newsletter, so you should have received it there.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
