Koshima

The remote work era exposed a strange paradox: while we saved time on commutes, we often ended up working longer. Maybe it’s because our calendars became too accessible, or perhaps the "out of sight, out of mind" fear kicked in for managers. Either way, the true cost of this shift is still playing out.

Interesting question. While I don't see a complete calendar overhaul anytime soon, I wonder if we'll see more region-specific tweaks to better align with local cultures and work patterns. For example, some Middle Eastern countries have already shifted their weekends to better sync with global markets. Maybe future tweaks will focus on optimizing productivity or aligning with the natural rhythms of remote work.

This feels like a classic “globalization vs. national interests” tension. Apple’s move to manufacture iPhones in India is part of a broader strategy to diversify its supply chain and reduce dependency on a single region, which makes sense given the geopolitical landscape and recent disruptions in global trade.

Also, India is one of the fastest-growing smartphone markets, and local manufacturing often means lower import duties and a better understanding of regional demand. It’s a smart business move, not just a political one.

Curious to see how this plays out, especially given the Make in India push and the fact that China is no longer the default factory floor for the world.

How are you different from calendly?

I break it down based on context:

Tasks: If it’s actionable, I add it to Linear as a task. This keeps my workflow organized and ensures I don’t lose track of things that need follow-up.

Learnings: For insights, ideas, or interesting conversations, I maintain a set of organized Notion documents. I capture everything from technical deep dives to random thoughts I find valuable, so I can revisit them later without cluttering my immediate workspace.

This way, I can close all tabs at the end of the day without worrying about losing context or forgetting something important. It also helps me spot patterns in what I’m learning over time, which is surprisingly motivating.

I think the decline of FILE_ID.DIZ files is largely a byproduct of changing distribution methods. Back in the BBS and early FTP days, these small text files were crucial because they provided a quick summary for file archives, especially when bandwidth was limited, and you couldn't afford to waste time downloading the wrong file.

With the rise of platforms like GitHub, GitLab, and Bitbucket, project descriptions and metadata have become more integrated. The README.md has essentially replaced FILE_ID.DIZ as the default "project descriptor", but with much more flexibility for formatting, linking, and even embedding media.

Additionally, the way we discover and share software has changed. We now have package managers, app stores, and automatic metadata parsing tools that handle much of what these files used to do. Plus, we expect modern software to have much more comprehensive documentation than a few lines in a .DIZ file.

I totally get where you’re coming from. One thing that has helped me is not just counting lines of code, but also using tools like Cursor (YC-backed) to get a sense of how my productivity stacks up against other developers. It’s a neat way to avoid the “just ship more code” mindset and focus more on efficient problem-solving.

I also find it useful to break projects into smaller, well-defined milestones. Instead of just aiming for a certain line count, I set targets like “implement the first API endpoint” or “get the first integration test passing”. This way, you’re not just pushing code but actually moving the project toward completion in a more structured way.

Curious if anyone else has tried using tools like Cursor or something similar for this?

you're absolutely correct about this. It's important that billing systems as well as product nudges you whenever you're using a service which involves charges. We're so much used to seat-based pricing or monthly or quarterly subscriptions that usage-based billing with transparency will lead to disputes like thse.