1,974 karma · joined January 3, 2021
Have a decade's worth of business analysis & consulting experience.
My industrial experience ranges from steel mill automation, power station and electrical distribution networks down to smart homes.
My business IT experience includes insurance, FMCG, supply chain and manufacturing.
I have a recent PhD in software engineering and have taught postgrad software engineering courses.
Available under contract to create engineered IT solutions for your business.
Email: gian@cyberfonic.com
For those are late to the party: https://en.wikipedia.org/wiki/ELIZA
Musk claiming AI being at a PhD level reveals that he has absolutely no idea as to what gaining a PhD entails. In summary: A significant contribution to the body of knowledge. The antithesis of what can be determined by regurgitating what has already been written about any topic.
This is how VCs destroy businesses by bring in adult supervision. CEOs are not incentivized to play the long game.
The difference between the mobility & transportation industry, whether it by carriage and horse, or motor car, was that it was in demand by 99% of the population. AI, on the other hand, is only demanded by say 5%-10% of the population. How many people truly want an AI fridge or dishwasher? They just want fresh food and clean dishes.
Anecdotally, it doesn't appear to be any good for job searching. Lots of un-directed random messages from recruiters, but no real job sourcing.
It seems to be the fate of all socially oriented networking sites. They devolve into yet another advertising, spam delivery mechanism.
But isn't prompting and iterating another way of instructing the computer to do what you want? Perhaps we could view it as a step up in the level of abstraction we work at.
We had similar arguments when high-level languages were introduced. Experienced programmers of that era maintained that they could write better programs in assembly language than in COBOL/FORTRAN/PL-I/Pascal etc. Yet even today we still need core portions of code written in assembler, but not much.
The industrial scale painting robots work well for painting cars coming off an assembly line, but not for landscapes nor portraits.
Automation (not just AI, but in general) works well for highly structured, repetitious work but not for creative expression.
A sufficiently smart compiler requires ever more clever compiler writers who are deeply knowledgeable about the many quirks of the numerous architectures.
If you look at IT history, it goes something like:
$ -> COBOL & mainframes -> RPG & minicomputers -> RDBMS (DB2, Oracle, Ingress, etc)
-> ERP (SAP, PeopleSoft, etc) -> CRM (Salesforce, etc) -> ... AI/LLM/ML -> $$$$ -> ?Folks who just want to make a lot of money become stock brokers, merchant bankers or venture capitalists and "invest" other people's money in the efforts of the problem solvers.
I find it most irksome that the Australian Labor Party has chosen the USA spelling in spite of being part of the Commonwealth.
B2B sales has always been the problem solving business. Define the problem, demonstrate how your solution makes more money or saves money. Price your solution at some viable fraction of the value you deliver.
So AI is part of your magic sauce. It might make some solutions feasible that require that capability.
Another suggestion: pick up the phone and talk to your prospects. eMails get lost in the volumes being received. The spam filters might be rejecting everything that has AI/ML/LLM etc in it.
Nothing really changed. Ageism is still a hurdle. While I was in academia my industry contacts have gone stale. Agencies that used to source excellent contracts fail to connect with requirements which are overly specific, e.g. Java, or SAP, or whatever. Having a higher level of knowledge together with decades of experience is not competitive in face of outsourced resources from the big international consulting firms.
I have friends who work/worked for top law firms, consulting firms, some are medical doctors. Most are overworked, burnt out, frustrated with increasingly bureaucratic managements, facing relationship issues, nursing a variety of addictions.
My only piece of advice is: optimize your life for quality not income. Prioritize your health, happiness and relationships.
First time is always very difficult. Identify recurring or comparable events. Over time you will meet some people you already know. Remembering some details from earlier encounters will build rapport. Likewise people will remember you from previous encounters. But, beware of the trap of only talking with those whom you already know. For every event, target to form at least a couple of new connections.
We only need to look at how BASIC (MS) and HyperCard (Apple) were eliminated in order to remove easily accessible end-user programming. wrt spreadsheets, only a tiny minority of operators use the macro or language binding features.
I shudder at new motor vehicles being ever more software based. On this basis of any recognized bug to lines of code metric, hundreds of faults are lurking therein.
I wasn't familiar with that connotation of "ambition", yet it immediately rings the bell when thinking of many folks who loudly and frequently talk about their "ambition"; all talk, no walk.
Start looking for a new role that is better aligned with your expectations. You may find it harder than you expect. In which case, you might be glad you didn't burn your bridges in a pique over AI mandates by the CEO & CTO.
>There are doers and there are talkers.
There are those who use their ambition to define a goal and then work tirelessly to achieve it. Think of the mountaineer who plans and trains for decades to eventually ascend Mt Everest.
Then there are those who share their ambition by talking about it. Seeking recognition, etc for "being ambitious". Staying with the mountaineer theme, those who refuse to climb a lesser mountain as not being important enough to expend their precious talents upon. It is these folks that if they somehow make enough money in some form, end up chartering a helicopter and sherpas to climb Mt Everest.
* You need to have experienced SAP *technicians* on board. It is far too big and complex to learn as required.
* In every case one of the Big 5 consulting firms were involved. Learn to work effectively with them. Be mindful of the fact that they might see you as a competitor that cuts into *their* billable hours.
* SAP documentation is horrendous. It is massive. Often misleading. Version and configuration details can easily lead you astray.
* Customization to client's requirements is the norm. These in turn are typically even worse documented (if at all).
* As much as you might wish to avoid it, you need to work with Oracle, DB2, etc database vendors too.
* The hardware configurations are often bizarre. Especially when deployed in clusters with fall-back, etc.
I hope you have a VC with deep pockets and lots of patience. Your first paying client could easily become a huge time and effort sink.Today's tablets are far more convenient to locate where they are needed and portable as well.
Tip note: instead of chucking old (Android) smartphones in a drawer to be forgotten, update Chrome on them, configure WiFi and use them as general purpose thin-clients.