Featured post

Google Summer of Code

Google Summer of Code (GSoC) is a global, online program that brings new contributors into open-source software organizations. The program b...

Showing posts with label coder. Show all posts
Showing posts with label coder. Show all posts

Sunday, 5 July 2026

AI vs. Graphics Programmers : Should Software Engineers Be Worried?

 


Over the past few months, I've spoken with several software engineers working at Pune, especially those developing browser-based CAD software . A common question keeps coming up:

"Will AI replace my job? Does graphics programming still have a future? Will companies like PTC, AutoDesk terminate software engineers because of AI? And is it true that Anthropic or other AI companies will replace software engineers within the next few months or years ?"

These are valid concerns. AI is advancing rapidly, and the software industry is changing faster than ever before.

Let's separate facts from fear.

The Reality: AI Is Changing Software Engineering

There is no denying that AI has become incredibly capable.

Today's AI assistants can:

  • Generate code

  • Explain complex algorithms

  • Write unit tests

  • Debug many common issues

  • Create documentation

  • Review pull requests

  • Speed up development significantly

This means software engineers who ignore AI will likely become less competitive over time.

However, this does not mean software engineering is disappearing.

Instead, software engineering is evolving.

Why Graphics Programmers Are Harder to Replace

Working on browser-based CAD software like Onshape is very different from building simple CRUD applications.

Graphics programmers deal with problems such as:

  • 3D geometry

  • Mathematical algorithms

  • CAD kernels

  • GPU rendering

  • WebGL/WebGPU

  • Computational geometry

  • Performance optimization

  • Browser rendering pipelines

  • Large-scale software architecture

These are highly specialized engineering challenges.

AI can certainly help write parts of the code.

But AI still struggles to independently design, debug, optimize, and maintain large graphics systems involving millions of lines of code.

The more specialized your expertise becomes, the harder it is to replace.

Can PTC Replace Engineers Because of AI?

Companies don't generally replace employees simply because AI exists.

Businesses care about:

  • Delivering products

  • Maintaining quality

  • Keeping customers happy

  • Building new features

  • Fixing production issues

AI can increase productivity.

Instead of needing ten engineers for certain tasks, perhaps a team might eventually need fewer people for routine work.

But someone still needs to:

  • Make engineering decisions

  • Understand customer requirements

  • Review AI-generated code

  • Solve production problems

  • Design architectures

  • Handle unexpected bugs

Those responsibilities remain human-led.

The engineers who learn to work effectively with AI are likely to become even more valuable.

Will AI Replace Software Engineers in the Next 6–12 Months?

This is probably the biggest myth circulating today.

No credible evidence suggests that software engineering jobs—especially specialized graphics programming roles—will disappear within the next 6 to 12 months.

Yes, AI companies such as Anthropic, OpenAI, Google, and others are investing heavily in autonomous coding systems.

Their goal is to make software development dramatically more productive.

But productivity improvement does not automatically equal complete replacement.

History offers many examples:

  • Compilers did not replace programmers.

  • IDEs did not replace programmers.

  • GitHub Copilot did not replace programmers.

  • Cloud computing did not replace programmers.

Each innovation changed how engineers worked rather than eliminating the profession.

AI is likely to follow a similar pattern—though its impact may be larger.

Is Anthropic Trying to Replace Software Engineers?

Anthropic is building powerful AI systems capable of assisting with software development.

Like many AI companies, it aims to automate repetitive work and make engineers more productive.

That does not mean software engineers will become unnecessary overnight.

Even Anthropic's own engineers rely heavily on experienced software developers to build, train, evaluate, secure, and deploy these systems.

The software industry is moving toward AI-assisted engineering, not a world without engineers.

Who Should Actually Be Worried?

Not every software engineer faces the same level of risk.

Higher risk:

  • Engineers doing repetitive coding

  • Copy-paste development

  • Basic CRUD applications

  • Minimal system design

  • Low-code tasks

Lower risk:

  • Graphics programmers

  • CAD engineers

  • Rendering experts

  • Distributed systems engineers

  • AI engineers

  • Compiler developers

  • Security engineers

  • Performance optimization specialists

Specialized knowledge creates a strong competitive advantage.

What Should PTC Engineers Do Today?

Instead of fearing AI, prepare for it.

1. Become an AI-Powered Engineer

Use AI every day.

Learn how to:

  • Generate code

  • Review code

  • Debug faster

  • Write tests

  • Document systems

  • Explore unfamiliar APIs

Engineers who effectively use AI will outperform those who don't.

2. Go Deeper into Graphics

Become an expert in:

  • WebGPU

  • GPU programming

  • Geometry algorithms

  • Rendering techniques

  • CAD mathematics

  • Computational geometry

  • Browser graphics internals

Deep expertise is difficult to automate.

3. Learn System Design

Senior engineers are valuable because they make architectural decisions.

Study:

  • Distributed systems

  • Cloud architecture

  • Scalability

  • Performance engineering

  • Design patterns

AI can suggest ideas, but humans still choose the best architecture.

4. Understand AI

You don't need to become an AI researcher.

But every engineer should understand:

  • Large Language Models (LLMs)

  • AI agents

  • Retrieval-Augmented Generation (RAG)

  • Model Context Protocol (MCP)

  • Prompt engineering

  • AI-assisted workflows

The future belongs to engineers who know both their domain and AI.

5. Improve Communication

The most senior engineers aren't just great coders.

They:

  • Mentor others

  • Lead projects

  • Communicate clearly

  • Work with customers

  • Make strategic decisions

These skills remain difficult for AI to replace.

What Will the Future Look Like?

Five years from now, software engineering will almost certainly look different.

Engineers may write less code manually.

Instead, they will spend more time:

  • Designing systems

  • Reviewing AI-generated code

  • Solving difficult technical problems

  • Building innovative products

  • Working closely with AI tools

The role of software engineers will evolve rather than disappear.

Final Thoughts

If you're a graphics programmer working on browser-based CAD software at PTC Pune, panic is not the right response.

Complacency isn't the answer either.

The engineers most likely to thrive are those who:

  • Continuously learn

  • Embrace AI instead of avoiding it

  • Develop deep technical expertise

  • Strengthen system design skills

  • Stay curious and adaptable

Technology has always transformed our profession.

From assembly language to modern programming languages, from desktop applications to cloud computing, every generation of engineers has adapted to new tools.

AI is simply the next major tool.

The future will not belong to engineers who compete against AI.

It will belong to engineers who know how to build, guide, and collaborate with AI.

So, don't ask, "Will AI take my job?"

Ask instead, "How can I become the engineer that AI makes even more valuable?"

Tuesday, 22 March 2022

Google Summer of Code

Google Summer of Code (GSoC) is a global, online program that brings new contributors into open-source software organizations. The program began in 2005.

Since 2005, GSoC has brought together 35,000 students and mentors from over 130 countries worldwide. As of November 2021, 746 open source projects, from areas as diverse as operating systems and community services, have participated as mentoring organizations for the program.

Successful students made them more attractive to potential employers and the GSoC has helped greatly when embarking on their technical careers.

Why Should I Apply?

  1. An absolutely amazing learning experience
  2. Sense of achievement
  3. Hone your developer skills
  4. Get involved and build your network. During the 12 weeks of writing good code, you interact and share ideas with some great people of the Open Source community. At the end of it, you’ve made some great friends from all over the world with whom you can discuss fun projects, get feedback on your code, and just about anything.
  5. Being mentored by highly experienced developers
  6. The stipend and the confidence

Requirements.

  • You can find out where to go for help with technical questions
  • You take and respond well to feedback
  • You can work independently
  • You know when to ask questions
  • You can communicate effectively
  • You can install and configure software packages on your own
  • Pro Tip: Read the organization’s requirements or skills they are looking for in potential GSoC Contributors. Be aware that some requirements are likely to be firm and you must meet those requirements for the organization to consider your application. For example, many organizations require potential GSoC contributors to submit pull requests as part of their application, or they require you to have a chat with someone in the community about your idea before submitting your proposal.

    Finding the Right Project

    Each organization will have a Project Ideas Page linked to from the official Google list of accepted organizations. Browse the list of project ideas for each of the organizations for which you are interested.

    Ask questions

    Consider any questions you might have about the project, how it might be implemented, and what it would entail. Read the FAQs. If there’s still anything unclear about the project and requirements, get your doubts cleared.

    Pro Tip: The earlier you apply, the better. Submitting your proposal early helps you get early feedback.

    Writing a proposal

    This is a competitive program, each year Google turns down many more applicants than it funds. While pre-proposal activities are key to improving your chances of success, a poorly-written proposal is an easy way to fail.

    2022

Popular Posts