Home

Joseph Jude

Cover photo
Profile photo
Joseph Jude @jjude

I use Twitter as a commonplace note: https://t.co/vPr6DeA0d4 CTO In Sales • Homeschooling dad Building @siteaudittools & @thoughttonote

India Joined Feb 1, 2008
Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Vembu was able to build Zoho precisely because of globalization - sales offices across the world and ODC at TN. He is able to set up office in Tenkasi and service the world because of globalization, which is Ranjan's point too.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

> the production of these services can be distributed across a country > It will also generate a source of income and a reliable stock of human capital to seed rural communities that would otherwise lack the economic capacity to survive the loss of agricultural incomes.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

> Emission mitigation will require an enormous increase in production, investment, financing, and innovation to replace existing emission-intensive capital stock with climate-friendly stock. Continued globalization will facilitate all this.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

> elites are talking about the end of the world, we are talking about the end of the month He puts climate action into 3 buckets: - mitigating - adapting - migrating > each bucket bears more of the burden of adjustment as less is done on previous buckets.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Rajan says: > continued growth of cross-border flows of trade, capital, technology, information, and people, which is what I mean by globalization, will be needed to tackle climate change > Climate action and continued globalization are joined at the hip

Joseph Jude
Joseph Jude @jjude
In reply to @cvkrishnan

@cvkrishnan @rravi It all depends on the theme of the conferences. Most often what is spoken in one context is so out of line for another context.

Joseph Jude
Joseph Jude @jjude
In reply to @samridhisukhani

@samridhisukhani @YellowVisuals > The identity is certain , however the Process is uncertain and keeps changing. Exactly how it should be. Thanks for sharing. BTW, Hampi is awesome. Don't forget to see the sunset from the hills.

Joseph Jude
Joseph Jude @jjude
In reply to @jackerhack

@jackerhack Unfortunate fall out would be any future expose by wire (on anything) and anyone on meta. Will be no credibility.

Joseph Jude
Joseph Jude @jjude
In reply to @jithamithra

@jithamithra I understand the #jtbd framework but has hard time implementing it. Because everything will level up to - “buyers are buying piece of mind” Like most beauty queens say - “world peace”

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Like any change programs, modernizing legacy apps is hard; But most often the options before the businesses are: Do or Die Hope this thread has been useful. If so, would you mind following @jjude for more business & technology threads?

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Others steps in modernizing the legacy apps • Choose outsource vs in-house • Assemble a project team • Implement • Support

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Transform • Redesign the application from ground-up for the changed business context • Not just technology changes, but business models too • Hardest to convince internal teams

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Replatform • No change in functionalities and API signatures • Dependent applications will work as is • Use cloud technologies • Deploy DevOps practices to deploy automatically • Use monitoring facilities of the cloud platform

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Lift & Shift • containerize the application • no change in functionality • need either the code or at least the executable(s)

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Evaluate modernization methods • Lift & Shift • Replatform • Transform More info on each of these methods 👇

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Choose applications for modernization • Don't go with all applications • Choose low-hanging fruits to test the waters • Build a cross-functional team to manage portfolio of applications

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Needed Compliances • Geographical compliance (like GDPR) • Financial compliance (like SOX) • Domain specific compliance (like HIPPA)

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Complexity of change • Does the domain knowledge exists within the company • Does the knowledge of the application exists within the company • Is there a documentation of the existing application

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Cost of change • In-house vs outsourcing • Time & Effort needed • Ability to manage with existing members vs need to hire new members

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Cost of status-quo • Missed opportunities • Escalating support costs • Risks of non-compliance to regulations • Ability to run on aging hardware

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Fit for changed business context • Ability to match competition in offering services • Agility in releasing new services • Stability of the platform for more users

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Steps to build a business case • Fit for changed business context • Cost of status-quo • Cost of change • Complexity of change • Needed Compliances More details on each👇

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Building a business case Toughest to sell changes internally; so better to build a business case to sell to the board. If direction comes from the top, higher chances the initiative will succeed How can you build a solid business case? 👇

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Steps to modernize legacy applications • Build a business case • Select apps to modernize • Evaluate methods • Choose outsource vs in-house • Assemble a project team • Implement • Support

Joseph Jude
Joseph Jude @jjude
In reply to @kandansudhakar

@kandansudhakar @svembu @SundarSvga @sumanthraman Most these countries have healthy local market (talking only abt IT services), unlike in India the margins are very low. We can’t aim for fatty dollars margins and want to speak only local language. Let’s not forget Indian IT grew because of our knowledge of English.

Joseph Jude
Joseph Jude @jjude
In reply to @ReggieG71833945

@ReggieG71833945 @BharatVarma3 @Ravisutanjani Cons of UPI: • easy spending of money (unlike earlier have to go to bank, withdraw money, stop spending once cash runs out) • impulsive buying (you can buy as soon as you have a desire) These are not technical or policy issues. They are cognitive / behaviour issues.

Joseph Jude
Joseph Jude @jjude
In reply to @RohitKuttappan

@RohitKuttappan Still Bangalore; Not just in terms of the opportunities and exposure, but travails of the city too; will prepare them for all kinds of scenarios life will throw at them.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

- What is your take on MACH? - What other applications will embrace MACH architecture? - Should MACH be the default architecture for all new applications?

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

Also, since many startups are dismantling monolithic enterprise services, enterprises will demand more and more options to compose their offerings.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

I expect all B2B products will be forced to embrace MACH architecture as customers will demand it as a default option.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

MACH is headless Buyers of the service are not bound by the inflexible frontend by the developers. They can design their own front-end; even compose a front-end borrowing from multiple services

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

MACH is cloud-native MACH softwares are developed using cloud services and hosted wholly on cloud. No on-prem or local installations ⇒ no maintenance hell of thousands of installations.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

MACH is API-first APIs masks complexity of underlying business logics and exposes only signatures. APIs make it easy to build tools on top of reliable black-boxes.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

MACH is micro-services Business functionalities developed, deployed, and managed independently. Key phrase - "Business functionalities"; not 100s of independent technical services - like sending emails.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

MACH isn't a new concept. Remember Jeff Bezoz's 2002 memo: - Teams must communicate with each other through these interfaces That is API-first If every team has API, that is microservices It is Amazon, so runs on AWS ⇒ cloud-native Since everything is API, it is headless

Joseph Jude
Joseph Jude @jjude
In reply to @ashwinmahesh

@ashwinmahesh This is where TN fared better. This is what @ptrmadurai & @mkstalin put forward as holistic growth of a state - not just one silo but every aspect & everyone grows. Hope more parties talk about it and all state demand such growth.

Joseph Jude
Joseph Jude @jjude
In reply to @jjude

@monikahalan @lukeburgis @GurmanBhatia You can ignore 90% of what you learn in school & college (unless you are in law/medicine...) and you'll be ok. (you should forget 90% of them) Master these skills, you'll get ahead of most • Multi-disciplinary learning • Structured thinking • Structured communication