rorytbyrne

At that point I think the case for a tool like git-plan is pretty strong.

The site has a Let's Encrypt cert so it should be fine. I made some DNS changes to it yesterday though so maybe that has something to do with it.

That is not how it works, but it's an interesting idea. My worry is that it's a little fragile in the same way that vanilla git is fragile - you can accidentally start working on a new task and mess up your stack.

In reality, git-plan just keeps a directory of draft commit messages for you, and when you run `git plan commit` you can choose one of them to use as the template for your commit message. Essentially, it runs `git commit -t <YOUR_PLAN_FILE>`.

(I'm the author)

Hey folks, I'm the author.

Context-switching is hard. Having the discipline to prioritise effectively is hard, using git branches effectively is hard, and building tools to magically make it easier is...hard.

Git-plan doesn't solve this problem outright, but I hope it moves in the right direction.

I do think that once you have draft commit messages in your workspace, it is possible to build new tools that consume them to help you context switch. For example, a tool could automatically stage hunks for you, based on the draft commit message you wrote.

There are some great thoughts and criticisms here and I'll be taking them all onboard for the next couple of versions of the tool. If anyone wants to contribute, PRs are welcome and I can help out as needed.

Oops, good point. I totally forgot about Show HN (I'm not on here very often). It's still in development for now, so when the first "release" version is ready I'll post it as a Show HN.

I agree about the declarative approach, I like the idea of simply annotating your source code and then having Codeline process that for you. For example you could annotate several hunks as being part of the same commit, and then when you run Codeline it would reconcile and make the commit for you.

It may be possible to support both declarative and procedural (i.e. unix pipes) paradigms together, but they may have to be two distinct parts of the SDK to avoid confusion.

Hi folks, I'm the creator. Codeline aims to combine the context-aware power of IDE extensions with the expressiveness of command-line tools.

To that end, Codeline will give commands read & write access to the source-code context, and will make it possible to pipe commands together like in unix.

Right now I'm looking for people to try out v0.1.0 of the SDK for building commands, help me design v0.2.0 of the SDK, and maybe contribute to the core functionality as well (once it settles down a bit)

Thanks for checking this out!

Anyone interested in this concept should read The Innovator's Dilemma. It covers the idea innovation suffocation within big organizations very well and is just an overall fantastic book.

I feel like a handbook for startups shouldn't start with a guide on how to hire.

Hi guys, Metro is a new way for companies to collect data. It works by allowing your users to generate useful data on any website, and share it with your company. It's mutually beneficial, and ethical by design.

Feel free to ask me any questions.

You have full control. Data generation is opt-in, on a per-project basis, and you can pause data generation whenever you want.

The data is generated by plugins called DataSources, which are community-made and open-source. Since the community owns the data generation code, there is less of an incentive to make something untrustworthy, and it's a lot more difficult since the code is open source.

Transparency is key here. I think that once we have a transparent and fair foundation for sharing user-generated data, we can build some really cool stuff with data that was never possible before.

Yeah unfortunately we aren't UX experts (this is the first website I've made actually) and we've been focused on building the backend and desktop site, so we haven't made the website responsive yet.

Hi HN, we're Rory and Conor - two undergrads in Dublin. Metro lets you write your own data-collection plugins which others can install to donate/sell data to your project. The DataSources are dynamically plugged into our Chrome Extension when you press "enable DataSource" on a Metro project's page.

Metro is just 3 months old and we just opened the site for public signups this morning, but hopefully it works okay and you can do some useful stuff with it. We're full-time students and learning as we go, so keep an open mind (and let us know!) if you find any bugs or problems.

The feature you might like best is Open Data projects, which are projects which give every contributor access to all of the data.