- Not having time to deal with your review backlog.
- Delaying a release because your reviews aren't done yet.
- Posting reviews that are no longer relevant since the code has changed so much in the meantime.
- Doing poor reviews since you have to rush through them at the last minute.
Friday, September 26, 2014
Wednesday, September 10, 2014
Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.
Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"
Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.
Guess that means the iPhone 8 will be back to boxy.
And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming. The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" worthy? No. Maybe I'm just jaded.
One more "bad thing" is that the Apple Watch (which does look very cool) requires an iPhone. So now you can walk around with more Apple devices instead of just one. If you're going to change my life, make my load lighter, not heavier.
So much for real Continuity.
Thursday, August 21, 2014
At a client recently, we developed our WPF application under Windows 7, tested it under Windows XP and everything looked great.
Then it was deployed.
As it turns out, one of the deployments was over a Citrix server that forced applications to run under Classic mode.
Those of you who have worked with various operating systems over the years will know what I'm talking about. Classic mode isn't quite classic, unless you are one of the few who think playing bar pong on an 84" TV is superior to playing one of the more dimensional games. Or maybe one of the few who like to get up and change the TV channel rather than finding the remote. Or one of the .... (you get the idea)
While most things converted well, Tabs do not. In WPF, we have these beautiful tabs that look fresh but over in Classic mode, they have the look and feel of, well, Classic Windows 95 and VB 6 applications.
The application was demo'd to the client under Windows 7 but deployed under Windows Classic so all of a sudden, the user's experience went from "wow, that looks great" to "what kind of crap did you give me".
But all was not lost. I found this very old (2006) but super useful post about forcing WPF to use a theme. In the end, it was as simple as adding a forced reference to PresentationFramework.Aero in the solution and adding
<ResourceDictionary Source="/PresentationFramework.Aero;component/themes/Aero.NormalColor.xaml" />
to the Resource dictionary (or to the Application.xaml file).
Voila our tabs went from crap to zap!
To make the experience even more sweet, that post from 2006? The blog is still being updated today (a lot more posts than here recently as well). Well done, Aelij Arbel, well done and Thank you!
Monday, July 28, 2014
If you haven't registered yet, be sure to listen for a special offer from Rick in the show.
Hope to see you there!
Friday, April 25, 2014
The explanation of time-tracking (second paragraph) really hits home when trying to promote why it should be used. I've been working with Microsoft's TFS for the past few years and one of the challenges has always been getting people to track time. If they don't see a real benefit to it, it's often perceived as a negative performance measurement tool. They have to get over that mindset.
As the post says "the Product Owner needs to know when the work on a story has gone over the original time estimated for the story. The Product Owner is concerned with Return On Investment... a legitimate reason to halt work on the story and reconsider the story’s business value."
The post then mentions SonicAgile, which I had never heard of. SonicAgile is a new online Agile Project Management and it is really really great. I've run through the gamut of online project management tools- from Basecamp, Kanban Kit, Trello, TFS, among others. All of them are great tools and depending on the client, I still use them. KanBan and Trello use the card-style interface and it's such a great way of forcing users to stay focused, even Microsoft turned to using a similar approach in TFS 2013.
SonicAgile uses a similar interface - but focuses on making project management super easy. After going through challenges with introducing agile processes, the fact that you can turn concepts (like iterations or epics) on or off can make this very useful for experienced or new teams!
If you're tracking multiple projects and/or different teams, you can turn on features just for specific projects.
Just getting started? Keep only the basic idea of using Cards to track features, change requests and bugs from To Do, In Progress and Done, just like Trello.
Need Iterations? Turn on the feature and now you can group your cards into time-sensitive Iterations.
Need Epics? Just turn them on.
Another cool feature - Roadmaps. You can create a public roadmap (much like Lianja did during its beta cycles) and use it for planning your iterations.
Oh yeah, on the road but without browser access? Just email your user stories to a special email address and it will create the cards for you.
It's a new tool - so I'm excited to see where it goes (it needs a mobile client) - but right out of the gate, SonicAgile got a number of features (including scheduled reporting) that are right there when you need them.
Thursday, September 05, 2013
If you go to Get VFPX , the price of the new book says it's $59,99 but if you actually click on the "Buy Now" button, you should be able to get it for $49.99 before September 6th.
Saturday, August 17, 2013
They have a demo version you can look at to get started but are also filled with lots of AlphaAnywhere.
I'm going to be publishing our talk in a FoxShow next week but one of the great things for Fox developers is that he's hoping to be at the SW Fox conference in October. Sounds like there's going to be a lot of HTML 5 being spoken at SW Fox this year.
Update: The show has been posted here
Sunday, June 16, 2013
While Visual FoxPro isn't receiving internal code updates from Microsoft, Visual FoxPro (or VFPX) continues to grow into a larger tool in the developer's arsenal. While Thor continues to deliver more power in the actual FoxPro IDE, new interface features grow what FoxPro applications can actually do.
But the core of FoxPro (fast and efficient database access) remains - and for all the tools or applications provided with Oracle or SQL Server or Postgres or whatever, VFP still provides the best data access environment that I've ever worked in. That means for developers who still need to deliver solutions, VFP will still be in demand. It may not be the "development language" for the next application nor will the DBF be the database - but the concepts behind accessing data and the extensibility keeps the product compelling.
How is that possible? When you run software in a corporate environment, IT departments liked to lay claim and identify the software they wanted to support. Typically, that meant whichever software was a) sold into the department by vendors (Oracle/MS) and b) understood by the most recent IT hire. Today, the corporate world has evolved - it's run more efficiently. People don't care as much as what software is developed in or with, they care that it works. That's not to say, they didn't care before - but I've seen government departments spend four-five times as much on new development to replace an older working technology and STILL not get the same result. Now the focus is on efficiency. If someone had told a corporate department that they would be running with a free database server 15-20 years ago, they would have been escorted politely out of the room. Today, it's all about what works.
At the same time, new software is constantly sprouting up. New databases, new extensions, new technologies, new cloud ideas, open-source environments, new environments ---- all of these make for exciting times for developers. SWFox also features a co-conference with Alaska Software, who have breathed new like into older Clipper applications with xBase++. In one of my sessions, we're going to highlight a lot of these new environments and how VFP developers can leverage their experience and expertise in these new tools.
Registration for this year's conference is wide open but they have an early-bird deadline coming up that ends on July 1st ($670, which includes a Pre-Con session - a steal considering some conferences are still going at $2500). Check it out at Southwest Fox 2013.
Friday, June 14, 2013
Doug's written up some of the sessions he's looking forward to and I have to say the sessions announced for Southwest Fox cover a wide gamut for the FoxPro (and xBase++) developer. (full disclosure: I'm speaking so I'm excited about that too)
Like Doug, I'm very excited about Eric Selje’s Will the Circle Be Unbroken: Continuous Integration and VFP
When VFPX first came about, Alan Stevens had done some work on an MS Build target for VFP. This never really took off which was too bad. Continuous Integration is so wonderful that once you have it, you will wonder why you didn't do it earlier. It's a great way for ensuring you compile, teaching your team, identifying conflicts and just feeling good about your approach. We're using it extensively at one of my clients and it really has helped identify the culprits (gulp!) who break code.
Hope to see you there
Wednesday, June 05, 2013
So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinctions I would argue are the difference between programmers and developers.
While many advanced developers make assumptions such as "every programmer unit tests their code" or "everyone uses TTD", most developers I've ever met know that's not the reality.
Software developers write code. Software architects solve problems.
Software developers see bugs. Software architects see the big picture.
Software developers focus on the computer. Software architects focus on the customer.
Software developers think about new technologies. Software architects think about trusted technologies.