HN user

shehjar

29 karma

Product Manager and Software Developer. B2B SaaS Product and Design. Located in Mumbai.

Blog https://belowwaterlevel.com/

Work https://www.linkedin.com/in/shehjar/

Side Project https://fortmapper.in/

X: https://x.com/shehjart

Posts5
Comments30
View on HN

This was a major gap waiting to be filled. After my experience with GH CodeSpaces, I've been wanting a system that simply provided the shell experience in the browser without the IDE. This should help I think.

Thank you.

Is Python support on the cards?

Growth can be achieved with small teams. But, small team size must become a leadership skin so it cannot be taken off when it feels inconvenient.

Us tech people being tech people, we look at this as a systems design problem but no one seems to be considering what conditions lead to such massive demand for this show in particular. I can bet inadequate supply in general is a major cause, part of which is regulatory issues and red tape.

I never said theres a catch all meaning to difficult situations. Every one has to draw their own lines about it. I understand its in fashion to talk about RTO as a difficult situation and it certainly is for a large segment of employees but would it also be a difficult situation for a developer if they are asked to follow a coding style at work that does not conform to their own personal style?

Some might say yes, thats a difficult situation while others might say how stupid that is to make a situation out of that.

The point was, the difficulty levels can vary and employers would like to know where an employee stands so as to gauge fit with the ups-and-downs of a particular context of that particular organization.

The recruiter perspective has some relevance too.

A question in their minds is whether candidates have the tenacity to stick through ups and downs of a company. This happens very frequently and I guess the employers are trying to gauge whether people will up and leave the moment things get difficult.

it may merit some nuanced explanation when such a question comes up.

They started out with places to stay and now throw experiences into our faces on the home page.

Compare that to booking.com home page that has stuck to “place to stay” as the entry point for the user for ten years since I’ve been using them both. That consistency means a lot and ends up occupying a space in the user’s mind.

Aibnb cannot make up its mind on what it is.

You are right and I am simply putting myself in the shoes of the late stage investors. Perhaps they have been sold a story the drives confidence in a 2X return. When the story doesn’t hold up, there isn’t much of a multiples buffer to prevent losing money.

Demand and supply is playing a big role in the valuations.

One could argue that absent a MnA ecosystem, investors only have a handful of opportunities to multiply their investment. It leads to simple handing-off to next round investors as the one and perhaps only opportunity to get returns on the funds.

Only recently has the ecosystem understood the potential for IPO in India as a potential for exit.

The degree of specialists that current tech stacks encouraged is not helping prevent creation of such heroes.

It’s no wonder that we now have software developers working under the assumption that one person can run the whole show.

In case theres further interest in reading about Purpose as a way to bring immense motivation and clarity, please see Deep Purpose by Ranjay Gulati(HBS Professor)

Religious ones help. Especially the parts About regulating and observing your own emotions. Bhagwad Gita was helpful to me as a Hindu.

Deliberate Calm is another one that helped understand on a more scientific level now our emotions are created and how that leads to our behavior.

Prioritization conflicts are exactly the situations when Product Managers must step away from traditionally accepted management tools and frameworks and look deeper into Purpose.

I don't think the issue is one of big repo versus small repos. IMO, the crux of the issue lies in your last sentence:

My issue is with ambiguity, vision, ownership, and having the big picture of the project in my head.

One could make the argument that the above are issues of leadership and the systems in place(or lack thereof), which could help navigate ambiguity, ownership and clarity of vision. If that is so, perhaps a system would create high quality onboarding plans for new people to grok that structure quickly enough to make a difference, or have adequate cross-squad synchronization and knowledge sharing, busting of siloes etc.

I don't think this one is about individuals but more about the system. Although, if the motivation and incentives are encouraging for you personally, you could try creating a system of record so that subsequent new folks can have similar questions answered as you did when you joined.

Gathering such feedback is extremely high value so it helps to consider it as a core part of the app’s user experience.

If you are really interested in offloading the underlying dev and management effort, consider using API based services around which to wrap your own experience.

I guess it comes down to respecting the users strong intent in providing feedback and showing what follow up action Has been taken on it.

The issue with starting with a label like “foolish” for others is that it’s more a reflection of one’s own assumptions about the other person. This is when we are lacking empathy and understanding.