Some long time ago I was working on a large software development project, and I wasn’t happy with either the quality or the velocity of our programming effort. So one night I sat down and tried to work out an activity diagram to show what our software development process needed to be, to improve both speed and quality. It turns out that a lot of this is just common sense, but for some reason or another team members would try to circumvent the process, which always led to more pain for everyone involved.
If you’re interested in developing applications for the Google Assistant, there is now a Google Assistant Developer Community Program. From that link: “To support your efforts and celebrate your accomplishments, we put together an ever-improving program with benefits and incentives that are tied to specific milestones.”
Here’s a link to Google’s announcement about ARCore Developer Preview 2.
Seibel: What do you enjoy about programming?
Peyton Jones: For me, part of what makes programming fun is trying to write programs that have an intellectual integrity to them ... so I think a good attribute of a good programmer is they try to find a beautiful solution.
I started to write a joke or two, but this picture from Apple’s 2015 WWDC (developer’s conference) speaks volumes about the ratio of male to female developers attending the conference. Photo from this Twitter page.
There’s a nice collection of front-end developer job interview questions at this Github link.
I don’t know the original source of this image, but the questions are good. I usually ask the “Typical day” or “Typical week” question. When I’m talking to the person I’ll be working for, I also ask if they can describe their managerial style or philosophy. When it comes to software development, I also want to make sure they use source code control systems, can build their apps with one command, they write unit tests, etc.
In my spare time I’ve been working on a talk about “X Things Java Developers Should Know About Scala,” inspired by the “Ten things every Java programmer should know about Ruby” presentation. Currently I’m thinking there are a baker’s dozen things Java developers should know about Scala, and I’d organize them as follows.
(If I just show a slide below, that means I haven’t finished a video for that topic yet.)
A note from Apple regarding the security problems of their Developer website.