Forgot your password?

typodupeerror

Comment: Re:Points on your license? (Score 4, Informative) 151

by ciurana (#39006145) Attached to: San Francisco Enlists Bus Cameras For Traffic Law Enforcement

Howdy!

I split my time between my homes in San Francisco and Moscow, and more than 50% of my time I'm traveling around major cities in Europe and Asia. I seldom use cars in Moscow, London, Paris, Tokyo, or pretty much anywhere else where trains, metro, buses, trolley cars, etc. are available. I never owned a car or motorcycle anywhere in Europe or in Tokyo because I just don't need to. If necessary, I rent a car for a day or two, then it's back to the metro.

Public transportation in San Francisco just *sucks* in comparison to other cities, both in the US and worldwide. My beloved city (SF!) doesn't have the flexibility of underground trains like NYC or DC do. MUNI is a joke -- they have lots of buses that have the most inefficient passenger pickup areas in the world -- never have I seen a bus line with bus stops at almost every flipping corner along the route, like in San Francisco. Taxis? More suckiness. Trains? Forget it. San Francisco without your own wheels becomes a pain in the ass very fast.

"The bus system was great!" - try planning your trip by bus, and being on time without having to leave too early, from any point in San Francisco to your destination within the city. You often have to wait for 20-30 minutes without a bus in sight, then four or five come together, in a bunch, because the MUNI drivers decided to take a smoke or lunch break and end it at the same time. This is a far cry from a place like say, Zurich or Oslo, cities of the same approximate area and with a high automobile density, where the bus schedule is met at exact times (e.g."next bus will be a 10:43" and it shows up at exactly that time).

I love San Francisco more than any place in the world. Hearing someone praise its public transportation, though, is like hearing someone praise my mentally handicapped kid brother's arithmetic ability as if he were solving differential equations.

Cheers!

Comment: Re:On-line, other education and courses - advise (Score 1) 201

I agree with the spirit of what you say, perhaps disagree a bit on the details.

When hiring a civil or mechanical engineer I'd certainly put the guy through the paces (I did that when I was in charge of building industrial robots, early 2000s) to ensure that he or she doesn't kill someone by swinging a fingerboard to far, too fast, or too close to where people might be, and so on. Or cause an explosion. Or... you get the idea.

You wouldn't let a civil or mechanical junior engineer design a bridge or industrial tool either. You'd invite her as part of a team, watch them contribute, and build accountability over time in response to their ability to deliver, to learn the details of the job, and to deal with human factors ranging from management to on-site security.

I do find a more cavalier attitude in software development, where computer "science" graduates are thrown to develop mission-critical or business-critical system without much thought IN SOME SHOPS. Throughout my career my teams tried to be responsible about who's building what, to prevent hurting our users, clients, or employers. But then I'm a computer *engineer*, not a computer *scientist* -- different animals. We had a joke back at the university: "Please don't call me 'computer scientist' -- I do know math, physics, and statistics, and didn't go to college just to get credits."

Cheers!

E

Comment: On-line, other education and courses - advise (Score 5, Insightful) 201

Howdy.

I'm a VP of technology for several companies, and have been in a position to hire software, network, and system engineers since at least 1997. In all honesty, neither I, nor any of the people who've reported to me, ever paid much attention about where someone went to school, what their actual degree was, or whether they had earned some honor -- as long as the guy could deliver. From certs to prestigious schools, we never really bothered. Eventually I found out that I had a couple of MIT grads and at least one Stanford kid. I also had a pile of people whose degrees were awarded by foreign universities (including my own) and really... nobody really cares.

If you have the skills and you have the work experience, then you should be fine.

Right now I sit on the tech board for a couple of companies in Europe and the US, and I'm driving the technology at a very large social network with dev operations in the UK and Russia. I do notice that Europeans pay more attention to "schooling" and "degrees" and "titles" than US companies do, but not by much. My former employers and clients include some of the largest companies in Silicon Valley, rest of the US, Europe, Japan, and Mexico. The only occasions when I had to produce some kind of official proof of education were:

* When getting my US labor certification (1991... long time ago...), and when getting my Russian labor certification (last year) -- bureaucrats just love the fsck-ng paperwork
* When applying for a US federal job -- even then, they clarified that all they care about is whether I completed the degree or whether it was accredited, the date, and some accreditation equivalence since my degrees are from foreign institutions

Pro Tip: see if your employer will pitch in for part or whole course. Tech departments have educational budgets ranging from a couple of hundred dollars/year for books per employee, to full scholarships. I've auth'd books, on-line courses, conferences, PIM, and university courses for my peeps many times in the past. Check that out with your supervisor or with HR. A lot of people don't realize the option might be there -- and, if others in your group aren't taking advantage of it, your manager may be amiable to extend your budget a bit more (since money she doesn't spend is money she may have to cut next year).

So -- get your education wherever you can as long as they are legit, kick some butt, take names, and good luck in your career advancement!

Cheers!

Comment: Simple tricks for shielding your phone (Score 1) 225

by ciurana (#36787710) Attached to: Police Increasingly Looking To Smartphones For Evidence

Let's say, for sake of argument, that for some reason you want to shield your phone for a period of time. Make it completely opaque. Just put it inside a mid-range to good quality microwave oven. Good shielding prevents the signals from going in or out. This way the phone disappears in a certain location. It reappears at the same location some time later; while it was in the microwave oven, if the shielding is good enough, nothing will come in or out.

Other fun tricks: are you on GSM? Remove the SIM card, and pop a different one from a different provider. Preferably one from out of the country. Don't do it at the same location, though. Remove and leave at home, go a few km away, pop the other SIM card in. Don't pay for the second one with the same credit card as the first one. And so on.

Any other fun tricks out there?

Cheers!

Comment: Good interview, deeper thoughts? (Score 1) 337

by ciurana (#33729120) Attached to: Father of Java, James Gosling Unloads

The interview was entertaining and somewhat insightful. I wish the interviewers would've asked more details about Gosling's current doings, what aspects of NoSQL he's working on, details about the languages, etc. Too much space was allocated to Oracle Venting. I wish the interviewers or Gosling would've devoted more time to more technical stuff and future directions.

**** out of 5 - great job, Basement Coders!

pr3d4t0r

Java

Father of Java, James Gosling unloads

Submitted by javab0y
javab0y writes "The folks over at basementcoders (http://basementcoders.com) did a podcast with James Gosling, The Father of Java, last week at a coffee shop in San Francisco during the JavaOne conference. In a raw and no-holds-barred interview, James let loose on Oracle, the Google Lawsuit, and his experience with IBM. You know its going to be good when he starts out saying "I eventually graduated in '83. Went to work for IBM which is, you know, is within the top 10 of my stuipidist career decisions I've made". The podcast was fully transcribed and can be found at http://www.basementcoders.com/transcripts/James_Gosling_Transcript.html."

Comment: Best mouse operation for programming (Score 3, Interesting) 569

by ciurana (#28642659) Attached to: Best Mouse For Programming?

Howdy.

While taste in mice and features vary, one thing I would vouch for, if you're right handed and have a full keyboard, is to learn to use your mouse with your left hand. I worked with Gene Korienek in the early 1990s and we discussed how to optimize mouse motion. Since the page navigation, Return key, and numeric pad are all on your right side, using your mouse with your left hand will make you more effective for some activities such as using spreadsheets, Photoshop, web surfing, etc. I went "mouse southpaw" since then -- super-comfortable.

Now... for programming I use MacVim and a number of plug-ins and extensions. When I'm programming, unless it's something that's got a GUI or it's iPhone/Mac specific, I seldom use the mouse. One of the biggest advantages of using a keyboard instead of a mouse is sensory memory. There are actions in Vim (and possibly TextMate, emacs, etc.) that you can execute automatically, without thinking about the exact key press sequence, and without having to lift your hands off the keyboard. Check into any of these editors, add the appropriate plug-ins (e.g. "UNIX is my IDE") and see what works best for you. I went from keyboard-only (TurboPascal, Turbo C, vi/UNIX) to GUI IDE (Smalltalk/V, Symantec Cafe, Visual Studio, IDEA) back to keyboard-only for most programming tasks. Now my coding is split between keyboard-only (scripting, Java, C, assembler) and GUI/mouse for only a few environments that leave you no other option (Xcode/Interface Builder).

Cheers!

E

Education

OLPC Development: Cool New Interview and Specs->

Submitted by
ciurana
ciurana writes "Rob Savoye is a contributor to the OLPC project. He talks about OLPC in this video interview, and tells us how to contribute code and ideas. The article and video cover the hardware specs, a system overview, and a photo gallery showing the OLPCs features. Rob Savoye is a long-time member of the GNU project and is the CTO of lulu.tv. If you have ever used Red Hat, Debian, or Cygwin, chances are good that you've used his software."
Link to Original Source
PHP

PHP and RSS: Getting it together

Submitted by Anonymous Coward
An anonymous reader writes "RSS Syndication is virtually ubiquitous these days, so it's imperative that a PHP developer at least understand RSS and how it works. This article explains the basics of RSS, some of its many uses, how to use PHP to create an RSS feed from a database, and how to use the XML_RSS module to read an existing RSS feed and translate it into HTML."
Java

PMD Applied

Submitted by
Simon P. Chappell
Simon P. Chappell writes "It's a fundamentally agreed fact within our industry that code reviews are good. Really good. Sliced bread good. But have you actually tried organising one? If you can get everyone together that needs to be there at the same time in the same meeting room, then you still have the challenge of trying to keep a roomful of geeks from getting trapped in minutiae and squabbling over details like formatting conventions. Well, what if I told you that you could get your code reviews done in less than five minutes and that there would be no arguing? Enter PMD , an open-source Java static analyzer. Think of it as a code review in a box. As if that weren't wonderful enough, there's even a book, PMD Applied , written by Tom Copeland, the author of PMD.

I hope that it's not too much of stretch to suggest that this book is primarily written for users of PMD. That said, I actually purchased it (yup, this one wasn't a freebie) because I was considering a recommendation to use PMD as part of the build process at a previous employer. This is not a slam on the documentation on the PMD website, but Mr. Copeland was offering signed editions of the book if you pre-ordered and I wanted to add to my growing collection of books signed by the author. (No contest; geeky as charged.)

PMD Applied has ten chapters. The first chapter is the mandatory introduction and the second covers installation. Nothing unusual there. Chapter three covers using PMD from within Ant or Maven. I'm glad to see both build systems covered here. Both have a pretty good sized user base and both deserve to be represented here. Chapter four covers using PMD within an IDE. The range of IDEs covered is excellent and includes all of the ones that I would have covered and a couple of others that I hadnít heard of.

Chapter five begins the serious job of using PMD for static analysis by examining the ability of PMD to detect duplicate code using the wonderfully named Copy and Paste Detector (CPD). Chapter six is titled Best Practices. It's a wonderful collection of advice from Mr. Copeland, on how to begin applying PMD to your Java development process. As a Team Leader, I understand many of the points he makes. Teams generally don't enjoy having impartial tools dumped on them in the middle of a project that do nothing but nitpick their code and programming style; such things are a fast-track to being unpopular. Mr. Copeland's guidelines will increase the chance of your team accepting PMD, as you start with a subset of helpful rules with low chances of false positives.

For all of its cleverness, PMD is nothing without well written rules and chapter seven has this covered. PMD ships with a good sized rule set of its own, even though not all of these will be suitable for every site. Creating custom rule sets is an important first step in customizing PMD for your team. Once the team is used to PMD, they're likely to want to start adding new custom rules to the mix and the book has you covered there as well, with instructions on writing rules with both Java and XPath expressions.

Chapter eight addresses the matter of customizing PMD. Naturally, making changes to the code and recompiling is the first customization covered, but then it looks at custom report formats, adding new languages for the CPD and advice on making contributions of code to the PMD project. Chapter nine is a look at the internals of PMD. Now, perhaps this won't be of much interest to some of the readers of this book, but I found it fascinating. There's nothing quite like having the internal workings of a useful tool explained clearly by the person who wrote it. If you don't like it, it's only twenty pages, so skip over it and check out chapter ten where the playing field of similar open-source tools is examined. The book wraps up with a large appendix with a very useful explanation of all of the rules that ship in the standard PMD deliverable.

I'm going to let a good part of my personal biases show here, but I absolutely love slim and detailed technical books. PMD Applied is 221 pages, which is about the size of the pre-ANSI version of Kernighan and Ritchie's The C Programming Language; the greatest technical book in the known universe. This is the perfect size for a technical book, allowing the author to introduce their subject, explain everything that needs saying, wrap up and be done before the reader's eyes roll back into their head and an information overload coma descends upon them. This book is perfectly sized.

The level of technical discussion matches the size of the book and is just right. While the first few chapters deal with what is PMD and how do you install it and run it, the rest of the book deals with good solid code analysis using PMD. This is why we bought the book. We're geeks ... show us the code! Mr. Copeland doesn't disappoint us and there are many excellent code examples throughout the book.

The appendix is a snapshot of the rules that shipped with PMD at the time of the book's publishing. While new rules have been added since this time, the list of every rule and a portion of example code that would trigger that rule are useful. Even if you don't use PMD, buy the book so you can use the appendix as a comprehensive list of examples of how not to write Java code!

After having been out for a year, the exact level of the software described in the book has been passed by. This may bother you, but I feel that the basic principles of PMD have remained true and so I wouldn't let the version numbers dissuade you from purchasing.

The book is only available from the publishers, Centennial Books. They're a smaller publisher, but I had no problem with purchasing through their website.

If you use or are considering using PMD for static analysis of Java code, then this book should be by your side."

The magic of our first love is our ignorance that it can ever end. -- Benjamin Disraeli

Working...