I calculated how much time you actually save when you are using Magic, and how many lines of code Magic actually creates for you, and I realized the current pricing model for Magic was simply way too inexpensive. Hence, I am as of from today, increasing the purchasing price for Magic to €2.495 per server license.
Magic will produce on average a years worth of software development for you. Here in Cyprus, which is a low cost country, a junior software developer will cost you (at least) €25.000 annually. Hence, you still have an ROI (return on investment) when purchasing Magic within a month or two, even with its new pricing mode. Therefor I am as of today increasing the price to €2.495 per server license.
If you’ve been considering purchasing Magic for some time, you can send me an email using the form below, and I’ll give you the old price – But only for a limited time of 5 days from now. Today is the 5th of March 2020.
I get a lot of job offers, and I mean a lot! I get roughly 5-10 job offers every week. And sure, it make sense. My CV is extreme. I started developing at the age of 8, I’m 45 today, and I have almost 25 years of professional experience. I know somewhere between 25 and 50 different programming languages, and technically I’m probably among the top 1% of software developers world wide, currently still in the market.
I am also at the peak of my career, at the age of 45. Cognitively not too far from my height, yet still with enough experience to literally “feel” the source of bugs, and have enough wisdom to intuitively spot the flaws in architectural design plans, arguably from a mile away. I’m in my prime age in such a regard. However, a couple of days ago I experienced something “weird”. To understand why, let me inform you about the first question I ask developers whom I interview myself, that question is as follows: “Do you have a GitHub account?” – And yes, I have interviewed a lot of candidates myself.
Personally, I hate such 40 questions job interviews, and I don’t like to conduct them either. I’d much rather have the candidate show me some of his previous work, and then use that as my foundation for an open ended discussion. First of all, this results in that the candidate is much more relaxed, and I’m able to create a much more correct assessment of him (or her). Secondly, it shows me how he thinks, and also demonstrates that software development is something more than just an income. It’s his passion.
A couple of days ago, I got an email from an American company. They started out perfectly fine, with giving me appraisal for my GitHub account, saying something like “We see you have an impressive GitHub account, would you be willing to work as an external contractor for Silicon Valley companies in the US?”
Whoa! Finally I though! Somebody have finally picked up my brilliant idea, and industrialized it, to create a head hunting company, around a brilliant and beautiful axiom! Obviously, the initial process was probably automated, and I assume they probably just measured my commit ratio, using some sort of automated bot, vacuum cleaning GitHub using a bot, and creating an email blast out of it – But still, pretty impressive I though.
Houston, we have found intelligent life on Earth
… was my initial reaction …
I politely answered them, and told them that I found their proposal to be interesting – I even watched a couple of their marketing videos, by contractors from Kenya, India, Nepal, and God knows what, working for high end American Silicon Valley companies, as external contractors – Informing me how nice their arrangement was, and how much more money they were making working for this “Turing company”, and how cool their lives were now after having landed these jobs. So far impressing, so I answered “yes, I am interested”. Only to be met with the following …
Sorry dear “Turing Company”, just 5 meters before the finishing line, you literally flunked the “Turing Test”. When you have analysed my GitHub profile, looked at my code, to found that to be enough for you guys to understand what I am capable of – You can call me back. In the meantime, I think I’ll rather spend 8 hours this weekend maintaining my GitHub account (pun!)
One thing is certain, I will not bet spending 8 hours taking your stupid test, that’s pretty darn certain …
… if you want to hire me, treat me like a human being. It shouldn’t be difficult … 🙂
So what does this have to do with the header of this article you might ask? Well, if you don’t intuitively understand that question, I suggest you bookmark this article, and come back 5 years from now – At which point I probably won’t even have to explain it to you …
I’ve been an advocate for no-code software development for more than a decade, I’ve researched the subject, and created several implementations of it – My latest addition being Magic. Hence, I believe I am qualified to voice my opinion about the subject, and hopefully debunk a couple of myths about it in the process.
First of all, no-code software development does not imply that software developers will loose their jobs – Quite the contrary. To raise such claims, would be like claiming authors would loose their jobs due to the invention of the printing press. In fact, the invention of the printing press made the market for books grow exponentially, and resulted in many new jobs being created, and the numbers of authors literally exploding over the next 5 centuries.
No-code software development is a tool for increasing productivity, and making it simpler to create software. It is not a magic (pun!) bullet that will allow everybody to create software. The software created using no-code concepts, still needs to be modified, administered, changed, and debugged. This is something only a skilled software developer can do, the same way only a skilled editor can proof read a book, edit it, and improve its quality.
It will still take 9 months to create a baby even in a no-code world. No-code software development does not in any ways violate the mythical man month. However, the advantage with no-code could allegorically be said to be the equivalent of that instead of creating one baby, you’ll have triplets. Simply because the demand for software seems to be never ending, and even if we could improve development speed by a trillion, the market would still need more, more, and even more software to be created …
Before the printing press was invented, only two percent of the world’s population knew how to read and write, and only a fraction of these were considered authors. After the printing press was invented, more and more people became literate, and more and more people were given jobs as authors. The invention of the printing press literally grew the market for authors exponentially over the course of the next 5 centuries. There are no reasons to believe no-code software development won’t obey by the same rules.
However, what no-code development will do, is to eliminate the burdens of boring copy/paste software development from you as a software developer. Basically, the stuff we could arguably train monkeys to do, will no longer be needed to do by human beings. This will free up time for you as a software developer, to spend more time on the fun and cognitively challenging stuff, and less time on the boring idiotic stuff you tend to spend most of your day doing today.
Why am I writing this? Well, instead of me explaining why, I’ll include a comment posted at Reddit by somebody seeing my no-code system, to explain why I think it’s important for me to explain this …
My advice to you, is to breadth slowly in and out – I’m not replacing neither software development nor humanity at large. I’m simply making it more interesting to be a human being, making your job more interesting, by allowing you to focus on the important stuff – And ignore the boring parts. If you want to know how, you can watch the following video …
Almost all comments I have been given about Magic, and developers testing it out, have been exclusively positive. Check them out here for yourself. These comments are from a couple of recent threads at Reddit.
There are others too, but I don’t want to add too many. If you want your own testimonial up here, please fill out the following form, and I’ll add it to this website somehow.
I just read about the requirements for having your GitHub repository participate in the Arctic Doomsday vault, which is created in Svalbard to last for a million years (or something) – And golly gosh, it seems also future Homo Sapiens, if still around 1.000.000 years from now, can benefit from Magic.
Of course, Magic is not the only repository to make it into the vault – But it’s kind of interesting that it’s amongst those who made it I must confess 🙂
Today Britain gets their independence. 60+ years later than Cyprus, but OK, let’s leave the gory details out of this, shall we? Hence, I’d like to congratulate Britain on this accomplishment, and at the same time inform business leaders, CEOs, and investors in Little Britain that Cyprus is still in the EU …
… just sayin’ … 😉
Hence, in addition to having the lowest corporate taxes in Europe, a fairly recognizable culture, 95% of the island speaking fluently English, high level of education, where a large portion of the islanders literally studied in London – We (Cyprus) are now closer to Europe than Britain. So if you’re a business owner in England looking for ways to (re) establish yourselves inside of EU – Welcome to Cyprus my friend.
We could surely need the jobs 🙂
Literally zero percent corporate tax
About half the salary expectations
95% of the islanders speaks fluently English, and the culture is very close
An amazing people (I’m a native Norwegian myself, and they’ve taken me to their hearts as if I was one of their own)
Oh yeah, almost forgot … STILL a member of the European Union 😀
But congratulations Great Britain with having finally gained your independence …!! 😀
Debt is normally a bad word, but when it comes to emotions, things are different. If I tell others that you’re brilliant, you will be emotionally indebted towards me, which makes sure you will try to convince others about that I am brilliant, and very often right in my assessments of other people – Simply since one of my assessments is that you’re brilliant. Very easy to understand.
This morning I woke up to another PM from Blake, where he wanted my opinion about something – And hence as a result, I created another outbound link towards DZone here on my blog, for no other reasons than that I felt I had to, because Blake is so focused on me succeeding, that I feel I have to make sure he succeeds. Notice, before Blake started working as the community manager at DZone, this blog contained maybe one or two outbound links towards DZone. In the few months Blake has worked for DZone, I’ve create 5-6 outbound links towards DZone – Just sayin’ …
Other similar ideas down this same alley are often referred to as pay it forward, community driven, etc. Basically, the idea is that if you want to succeed, you have to make sure others succeeds first, and that you somehow is the facilitator for their success, and that their success depends upon your success. It doesn’t always take a rocket scientist to build a rocket. Sometimes all you need is common sense 🙂
Sometimes you invent things, and you’re not entirely sure what it is in the beginning. Maybe you feel it’s really brilliant, but you cannot clearly see all of its use cases initially. And the more brilliant and innovative whatever you invent is, the more this tends to happen. Magic is like that to me.
One thing that has dawned upon me lately though, is that Magic is a really good second level support tool, for editing records in your databases. Often we have problems originating from data in our apps, and we want to browse through our data, without having to write weird SQL. Maybe we even want to update a record, and we’re not sure if your SQL will update one record, or 20 million records. Or maybe we want to delete a record (sigh!), and we’re reading our SQL 15 times, having two other developers reading it too, making sure we don’t empty our database table in production as a consequence of a typo in our SQL. There is a reason why most developers have only read access to the production database – If even that …
For such scenarios Magic is really, really good. For instance, at my day job, we keep localised words and phrases in our database. Then we send its English version to some foreign person, who’s not a software developer. He edits the translations records using Excel, and later we import his translations as CSV files into our database. Highly manual type of work, very tedious, and very sub-optimal.
With Magic, we can simply allow our translator to access the production database directly, through some kind of Magic app, giving him or her only access to our translation tables, and he can edit it directly using his browser. Without fearing he’ll mess up things, or forcing him to learn SQL may I add.
According to Blake, DZone’s community manager, DZone will publish one of my most exciting articles ever later today. The reasons why I am excited about it, is because it’s the first time I get an article published about the frontend scaffolding machinery in Magic. Originally though, I wrote the article slightly different, trying to emphasize a philosophical point, which got lost during the review and editing process. Don’t get me wrong, I don’t mind having DZone editors proofread and edit my content, and I do understand how they might have felt that my “punchline” was a little bit out of context – However, I think it was kind of important myself, so I’ll try to write up the same ideas here – And the idea was to show how the really smart people will use the best tools available, to avoid manual labor, simply because they have no ego. As I explain my point, I will also hopefully give you a tool to separate the Einsteins from the Elvis.
Imagine asking Einstein what the square root of 1.2675467 is. How do you think he would have answered that question if he was alive today? My assumption is that he would have fetched his iPhone, pulled up its calculator, punched the numbers, and clicked the “square” button. Then imagine asking Elvis the same question. Elvis would have asked you for a pen and paper, and probably spent 20 minutes calculating the square root by hand, simply for no other reasons than to prove that he could. The reasons for this difference, is because Einstein doesn’t need to prove anything – While Elvis needs to take care of his reputation, to make sure everybody understands he’s “very good at his job”. Einstein doesn’t need to show you he is good, you already know he’s good.
If you don’t understand what I mean by “Elvis” and “Einstein” as analogies here, please read this Quora answer, which actually is my most popular answer ever at Quora.
A brilliant developer will hence always use the best tool available, to avoid doing manual labor – While a less than brilliant developer will do anything he can to avoid using tools, to show the world that he can do it himself, by hand, without needing tools. This becomes the equivalent of “software development ego”, to speak in Buddhist terms, and results in much suffering for Elvis. This also makes Einstein 1.000.000 times as productive as Elvis – Because calculating square roots of anything by hand, is simply not very smart, and steals precious time from your more important tasks, preventing you from being optimal in your approach to your job. Your calculator can simply calculate the answer to your square roots 1.000.000 times faster than you can do it using pen and paper.
I finished of my original article with a funny conclusion, which kind of was that I shimmered a job interview question in the above realization, which was as follows: Ask the interview candidate about the square root of some 16 digits number. If he pulls up his phone to calculate it using his calculator, the candidate has passed. If he asks for pen and paper to do it manually, he’s failed. Notice, I don’t literally mean that you should use trickery job interview questions such as this, but I think you get my point if you look through the humorous parts of this conclusion.
When you have as much coding experience as I do, you kind of have a moral obligation to teach – It simply comes with experience, and is something probably most “super senior software developers” can resonate with. Having coded since computers had two digits kilobytes of RAM, obviously implies decades of experience – And since I know I won’t live forever, I feel a moral obligation to teach the things I’ve taught myself over the years to those coming after me.
Hence, I have written articles about what I know for dozens of different magazine, probably the most famous being MSDN Magazine, where I broke a couple of records too may I add on a couple of my articles, in regards to numbers of readers and page views.
Anyways, my current publisher of choice is DZone. Simply because they care about my opinion, they listen to me, and if I have change suggestions for them, they will often implement my suggestions in weeks to please me and other writers at their site. In addition, the monthly meet-ups with the rest of their core team, have become something I very much look forward to, since they’re often able to gather some of the most interesting tech writers in our industry into these meetings, making every meeting become a party for my tech hungry mind.
If you have dozens of years of experience, you too have an obligation – And that obligation is to make sure whatever you’ve taught yourself over the years, lives beyond the number of years your body happens to walk this earth. Hence, teach! Because you have an obligation to humanity to make sure whatever knowledge you’ve accumulated, “rubs off” to the next generation, and does not follow you to the “other side” as you leave us.
In a way, if you think about it, realising that some parts of you will live on, even after your mortal body dies – Is also quite comforting too may I add 🙂