About Thanush BD

What I write about

The blog is for students and early-career engineers who want practical answers, and for developers working on backend systems. It covers:

• Software engineering and problem-solving: approaching unfamiliar problems, debugging and testing.
• Careers: projects, internships and interviews, for people starting out.
• Backend development and system design: data models, PostgreSQL, caching, APIs, scheduled jobs and alerting.
• Environmental technology: software for monitoring and compliance, and the sensor data behind it.
• AI and data: what it takes to put a model into a system people rely on.

Where the examples come from

Most of what I write comes from building production software. At Ecologic Engineering I work on environmental audit, compliance, monitoring and water-treatment systems: BioGraph, Digital Logbook, PCB Dashboard and CEMS. The work is mostly backend — PostgreSQL data models, APIs, Redis caching, sensor-data pipelines, scheduled jobs and alerts — with React dashboards and Flutter field apps on top.

Before that, I worked on industrial device communication and live sensor dashboards in the defense division of L&T Precision Engineering, and on computer-vision safety monitoring at Inventron Technologies.

Experience

• Full-Stack Developer, Ecologic Engineering (Sep 2024 – present). Environmental audit, compliance, monitoring and water-treatment software, including BioGraph, Digital Logbook, PCB Dashboard and CEMS.
• Software Development Intern, L&T Precision Engineering, Defense Division (Feb 2024 – Oct 2024). Modbus TCP/IP device communication, a data-ingestion and alerting pipeline, and real-time dashboards for live sensor streams.
• Software Engineering Intern, Inventron Technologies (Aug 2022 – Sep 2022). Computer-vision safety monitoring for PPE compliance with YOLO v5 and OpenCV.

The full timeline is in the experience section of the homepage and in my résumé.

Education

I studied Computer Science Engineering at Malnad College of Engineering, Karnataka, and graduated in 2024.

How I write

• Every article shows when it was published, and when it was last meaningfully updated.
• Where a claim depends on documentation, a book or a paper, the article links to that primary source.
• Code examples are run before an article is published. When a result depends on a version, the article names it.
• Nothing on this site is sponsored, and links to courses and books are not affiliate links.
• If you find a mistake, email me. I will correct it and note the change in the article.