Bingo.
Technical debit is mostly the collection of old not fixed bugs reported, known, and that still exist, or workarounds done to ship things that need to be done correctly in the future, and not done yet.
The impression I have reading the OP is that the report he received was assigned to, or reported from, the Technical Department (Technical Dept). If they called Xojo a “Technical Dept” maybe they have some system to measure companies and very small teams can fit under such label. Who knows…
But I see reasons to people analyzing the tool and company and refusing to accept it due to “Too much technical debit found”, but it does not seem what it was reported.
Xojo actually has a published page about these questions where they discuss the reasoning and respond to the issues.
Funny you mention that … To further support that point, both of the large companies I spoke of spent a good deal of time going over all the documentation I had created for my projects … everything from the software design specification to the final user’s manual. They also had a keen interest in where and how the source code was stored and what were the details of the backup protocol I used. But once again, if you’re doing your design the right way to begin with (meaning you’re doing all of that as a standard way of doing business already), you should be positioned to sufficiently provide proof and evidence that would allay any possible concerns on the part of the client.
Very well done value proposition/FAQ, Anthony! … I had no idea it even existed. I wonder just how many folks even know that it exists? Any Xojo developer who wishes to deal with business clients should steep themselves in the details on that page before they even have Meeting #1.
Xojo’s readability in my opinion is one of its greatest strengths. Nothing is worse for code maintenance than clever but cryptic coding, and I often write code that might be more brute force than necessary, just for the sake of readability.
We have been working on this for a little while but just published it. Hopefully this helps and we hope to deliver more resources to assist in making the case.
Well done Dana and team! It is partially what I told customers in the past, but it extremely valuable if this is coming directly from Xojo. I particularly like that it is not brute force marketing like “Xojo is the best tool” but balanced and leaves room for readers to come up with their own conclusions.
Likewise here, Julia for the same reasoning … I refer to it affectionately as my “personal bloatware”!
From the page at the URL provided by @Anthony_G_Cyphers
The Mythical Man Month explains that every extra developer you add to a team decreases the overall productivity due to the overhead of communication and coordination.
I read that book a long time ago. Still valuable. Everybody in development should read that book.
Perhaps that explains why Microsoft with its army of hundreds of programmers still struggles
to deliver one true cross platform development environment compared to a company with 5 developers .
REALbasic 1 (and 2 with Windows ?) was created and built by one man…
VisualBasic was created by one man in a weekend. But it was just a POC. An entire team followed him after, for the expanded and enhanced product, libs and components. Turbo Pascal, idem. One man, more time, and well done. And an entire team followed him for the expanded and enhanced product, libs and components.
Well, actually is beacause most of ther 14 million Visual Studio users were not interested on MAC or Linux. When more users needed to go on the mobile trend, They offered a working product, Xamarin.
Now that there are more interest on a cross platform development environment. They anounced one (Single proyect/code base to target Windows, Linux, Mac, iOS, Android and Web) and just in a couple years it is on schedule to be released this november so…
This page needs fact checking, specifically around the link to Pascal.
… basically interested on Windows. The Desktop OS that holds 80% of the market of the desktop OS’s but set as a second class citizen for Xojo for years.
Yes, there’s nothing worse than smart-■■■■ programmers who don’t document what they do.
As I did not see any other post talking about Pascal. Here is the detail:
Anders Hejlsberg (/ˈhaɪlzbɜːrɡ/, born 2 December 1960) is a Danish software engineer who co-designed several programming languages and development tools. He was the original author of Turbo Pascal
And yes. I was an young software dev that time using Turbo Pascal for CP/M in an multi-user compatible OS I helped to develop writing in Z80 ASM for a computer company I was working at that time.