Srinivas Tamada Interview: Career and Projects

An older description of a web project can leave you unsure whether it still reflects the product today. The Srinivas Tamada interview records what Tamada said about his career, advice and projects at the time.

I’ll explain what he said about his work and projects, and how to read those descriptions as historical accounts.

TL;DR: Srinivas Tamada’s Interview in Brief

Srinivas Tamada’s interview connects his early PHP work, the 9lessons programming blog and WallScript, a social-network project he described through the technology and goals of its time.

  • The original interview records Tamada’s own career advice and project descriptions.
  • Its WallScript description is historical, not a specification of the product currently presented on the official site.
  • His central advice was to understand documentation and focus on delivering a useful result.

What Is the Srinivas Tamada Interview About?

The interview includes Tamada’s advice for developers and descriptions of his projects.

His later 9lessons biography adds career milestones for readers who want a later account.

For present-day product details, the publisher’s current page is the better source.

What Did Tamada Say About His Work and Projects?

Tamada described PHP as important to his early career and said he liked working on the web. He also discussed blogging, product work and roles such as UI architect.

PHP and a career built around implementation

He credits PHP with helping his career and describes blogging as one way he explained web concepts.

His advice centers on choosing a tool for the work and delivering the intended result, since clients care about the finished output.

The 9lessons blog and the value of explaining web development

Tamada called 9lessons his part-time blog and described its purpose as explaining complicated programming problems in approachable terms. His later About page says he began the blog soon after his first PHP job.

For developers who write, a feature can give them a concrete problem to explain. Explaining it also requires clear language. This reading connects the blog and projects Tamada discussed.

A reader following his coding advice can also use CodeForGeek’s guide to learning coding for a separate discussion of practice and expectations.

The interview’s reference to Hacker News is best understood as one source he said he followed, rather than a complete learning plan. A news feed can reveal new tools and discussions, while official documentation explains how a specific tool behaves. Pairing those sources is a practical way to check whether a short update applies to the version or system in front of you.

WallScript as a social-network learning project

Tamada presented WallScript as software for building a social-network site and as a way to understand social-networking concepts. The interview lists PHP, jQuery, REST-style interfaces, oEmbed, PDO and OAuth among the technologies used in the version he described.

The interview lists PHP and jQuery for server and browser work. It also names PDO for database access. OAuth covered delegated sign-in, while oEmbed represented linked media.

The Wall Script 7 post describes groups, notifications, photo albums and private conversations. It records a dated release and gives context for the project’s features at that point.

The official WallScript site now describes a product built with Angular, Firebase and PHP RESTful services, and labels a version 8 offering. That stack differs from the one named in the interview. If you are evaluating the product today, use the official page for its present feature list and pricing rather than copying the interview’s older technology list.

OAuth Login, MailXEngine and WallChat

The CodeForGeek OAuth2 and Auth0 guide gives readers a practical next step on sign-in concepts mentioned alongside Tamada’s projects.

His 2019 About page lists MailXEngine among his side projects. The interview describes it as a bulk-email tool, but that does not establish its present availability or features. Check the project’s own site before relying on it.

Tamada mentioned WallChat as a project he was focusing on at the time of the interview.

Read the interview’s date and question before applying a statement about goals, tools or project status. Those details describe the moment captured in the interview, not a guarantee that a service remains available.

When evaluating software, check its documentation for maintenance status, endpoint behavior and product terms.

OAuth is an authorization framework that lets an application request limited access through a separate identity provider. The name alone does not identify the provider, scopes, token lifetime or callback configuration. A developer implementing sign-in should check the provider’s current instructions and distinguish authentication, which identifies who signed in, from authorization, which controls what the app may access.

PDO is PHP’s database access interface. It can provide a consistent way to prepare and execute statements across supported drivers, while connection settings and query behavior depend on the database in use. The interview’s mention of PDO is useful context, but not enough to reproduce a deployment.

jQuery is a JavaScript library used for browser-side work. When maintaining an application, inspect its source and dependency files before deciding whether to preserve or replace it.

oEmbed lets a site request an embeddable representation of a URL from a provider. The consumer needs a supported provider and valid resource URL. A label in an interview does not establish which providers were configured or whether a service is reachable now, so verify both before building around it.

What Should Readers Treat as Historical?

Use first-party product pages to check details that may have changed.

Interview detailHow to read itWhere to check next
WallScript technology listHistorical description in the interviewOfficial WallScript site for the current product description
WallChat as a new projectA statement of focus at interview timeLook for a current first-party product announcement
MailXEngine as a bulk-email projectWhat the interview said about the project thenIts current official service information
PHP career adviceTamada’s personal viewUse it as perspective for a specific choice

The desk-setup answer refers to a setup shown with the interview. It gives context for that page.

His About page gives a self-reported career timeline, including his education, first PHP job and later engineering-management work. It adds context to the interview’s discussion of development and public writing.

Conclusion: Read the Interview in Its Time

His advice about documentation and finished work offers a useful lens when choosing tools.

For more context, read Tamada’s biography, his dated Wall Script 7 announcement and the current WallScript product page. Together, they separate his interview answers from later biography and product information.

FAQ

These answers distinguish the interview’s historical statements from later source material.

Who is Srinivas Tamada?

Srinivas Tamada is a developer and blogger associated with the 9lessons programming blog and web products including WallScript. This interview records his own description of his work at the time.

What is WallScript?

The interview describes WallScript as social-network software and lists PHP, jQuery, oEmbed, PDO and OAuth for the version discussed. The official WallScript site now describes a later product stack, so consult it for current details.

What advice did Tamada give developers?

He said developers should understand documentation fully and focus on delivering useful work rather than judging a project only by its programming language.

Pankaj Kumar
Pankaj Kumar

Pankaj Kumar is the founder and CEO of CodeForGeek, with more than 14 years in IT. He is an open-source enthusiast who enjoys sharing what he learns through CodeForGeek and YouTube, with a focus on Python, data analytics, machine learning, Angular, Node.js, and Kafka.

Articles: 337