Skip to main content

Posts

Ai Code or AI Chaos? - ReInventing the Wheel

  Solving coding problems was one of my responsibilities as a Sytems Programmer in the 80th of the previous century.    The programs were written in COBOL .   A programmer had a probelm in a simple Program which copied File to File, probably omitting some of the fields.  She complained about the need to write her program. "It is better that the Systems Programmers will write a general purpose  program copying file to file and we will have to supply only the parameters" she said.  The Wheel was invented long ago I told her that there is no need that we will write such a program, as well as there is no need that she will code her program.  IBM already supplied a free utility called IEBCOPY which is performing the task she asked for. The Chaos of AI Coding Stories like the old bizzar story depicted in the previous section will become common stories in the AI coding age.  It is easy to ask Claude or ChatGPT to code simple programs. It is no...
Recent posts

Lessons Learned on AI Agents and AI Coding from Spooling Systems of 1970th

  The capabilities of IBM's Mainframe Operating Systems of the early 1970s were limited .  Lack of Spooling system was one of the limitations.  Group of four expert Programmers offered IBM a Spooling System which could be integrated into IBM's Operating System. IBM was ready to pay for that Spooling System because it would enhance significantly the Multi Tasking capabilities. IBM's managers asked them: How long it will take to code the Spooling System and integrate it with the Operating System?  The answer was: 6 months. How long it will take if we will add 70 programmers to your team? The answer was: 2 years. Only the 4 experts participated in writing HASP the first Spooling System in IBM Mainframe Operating System. Later versions evolved from HASP were Jes2 and Jes3. Lessons Learned on AI Coding Code created by AI probably is in the level of code created by the 70 programmers mentioned in the previous paragraph. The code built by the four experts is a lot better....

Legacy Systems Modernization is not simple : is Claude Code COBOL Modernization a useful tool or Hype?

In previous posts titled  Anthropic code or Hypethropic code?  and  Anthropic code: No Revenues Plan as Immaturity i ndicator  I was very  skeptical  about current Anthropic code capabilities.  This post is about the unrealistic dream of transforming Legacy Mainframe COBOL Systems to modern systems by using Claude code COBOL tool.   More than 50 years ago I was a COBOL Programmer. Afterwards I was a Systems Programmer and a CTO. I participated in Mainframe systems architecture changes, replacement  and maintenance, as well as   Mainframes migration projects and Modernization projects.  The main issues are not pure coding issues. Some of the major obstacles will be dwelled upon in the following paragraphs.  Functionality and flow of the System Usually nobody knows and understands it completely.  Claude code COBOL tool will create System which is not downward compatible. The systems were written decades ago and...

Vendors Survival: Will OpenAI Survive until 2036?

The vendors Survival posts are about the long time survival probability of leading IT vendors and Risks threatening their Long Term existence.    I wrote posts about IBM , HP . Apple , Facebook etc.   The most relevant posts related to Open AI are the posts about Google and Microsoft .  It is possible to compare the AI Revolution to two previous revolutions. The first is the  Industrial Revolution . The second is the Internet .  Bubble Comparing current AI market to the Internet of  the beginning of this century may be useful.  I remember the dot-com bubble .  A Seed Venture Capital rejected my proposal to  extend the Scalability and Robustness of  Microsoft's Windows operating system. The reason for rejecting it was "It is not pure Internet solution" i.e. it is applicable to Web Server but also applicable to internal Data Center systems.  Currently AI is the Hype stage of Gartner's Hype Cycle.  Probably, the curre...

Anthropic code: No Revenues Plan as Immaturity indicator

In previous post titled   Anthropic code or Hypethropic code?  I wrote that currently Anthropic code is not a Real World solution to Legacy Systems modernization, Security or SaaS applications.  If the Modernization tool of Legacy COBOL systems transformation to Modern languages such as Java, is capable of accomplishing this task in weeks or months Anthropic should sell it to users in very high price and the users will gladly pay that price.    The same is true about the Security code. In both cases the code is not the main issue.  These issues will be discussed in posts following this post. Tom Smith's article in Devops.com describes some of the issues.  The most important sentence in his article is " The market is in “sell first, ask questions later” mode on AI disruption". 

Anthropic code or Hypethropic code?

On 1978 I participated in an International computers conference in Jerusalem.  I was a young Systems Programmer and a good Chess player playing in tournaments. A main attraction was an Artificial Intelligence related event. It was a Chess Tournament between the best programs in the world. The leading programs of that time played better than ChapGPT 5 and other general purpose Ai Chatbots.  After the tournament people played against the Chess Programs. I won  easily  a game against one program. I do not remember if I defeated the program which won the tournament  or against the program which won the 2nd place. On 1997 IBM's Deep Blue defeated world champion Gary Kasparov . Today no human being is able to win against leading dedicated Chess programs.  Anthropic code Anthropic code solutions is the reason of  shape decline of stocks of other companies providing SaaS software, Security software and COBOL programming language Legacy systems. My Take Cur...

Is it Viable?

  As a Independent IT Consultant I often used Analysts Groups Services.  I read Research Notes written by Gartner Inc., Forrester, IDC , Meta Group, GIGA Group etc. and I asked them questions behalf of my clients. On 1998 my customer and me, as a CTO, tried to select a proper Enterprise IDE.  The headline describes exactly what i asked Gartner Inc. about one of the products in our list in order to decide whether it is a candidate to be included in our short list.  As usual I included a background description in my Query.  I received a one word written answer: Yes.  I thought that the answer was not good enough.   The Analyst had to take into consideration the question:  Why I asked the question on one software product and I did not ask the same question on any other of the other ten products ?  The reason for asking was information about the horrible financial situation of the company which developed this software product.  Selec...