Version control system commit comments are already very useful for many common development tasks, if done right (jira ticket number in ea...
Version control system commit comments are already very useful for many common development tasks, if done right (jira ticket number in each commit, commits divided properly, good commit messages with reasons for change). I wish there was more metadata there (like which tests failed during automatic build after each commit). But I disagree using text as underlying data format is a problem. It's godsend. Text can be grepped, copy-pasted, diffed and versioned easily. I cringe when I have to work with versioned word or excel documents. Working with versioned code is much easier. you may think big red arrow would be nice to put in code, but how do I later search for all red arrows related to X, added by John between 3 and 4 months ago? I have specification divided into 100s of versioned office documents. When I want to grep I have to know where to look (or zipgrep the underlying xml, which sometimes work sometimes doesn't). If it was in a text format I could grep and see real differences, not edit history. If it had embedded video I would need to watch the whole thing. And no - adding keywords isn't much help. I want to be able to search by content.
Posted by ajuc on Nov 28, 2014, 10:14 AM
Tags
Related issues
- Unless it is running on a government issued iPhone, it is not the Individual #1 you are alluding to.
- Great job, will try it.
- I also have a 2014 CR-V and I hate this too.
- I wish there was a setting to make audio and video opt in per site.
- There sure are.
- I feel like it's once a week that HN surfaces some incredibly overhyped, low-on-the-hierarchy-of-evidence ( https://en.wikipedi...
Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments
complaint (Other)
Unless it is running on a government issued iPhone, it is not the Individual #1 you are alluding to.
NewGreat job, will try it.
NewI also have a 2014 CR-V and I hate this too.
NewI wish there was a setting to make audio and video opt in per site.
There sure are.
I feel like it's once a week that HN surfaces some incredibly overhyped, low-on-the-hierarchy-of-evidence ( https://en.wikipedi...
That usually works well enough for risc code.
> The Bulletin calls her Miss Swindell.
Version control system commit comments are already very useful for many common development tasks, if done right (jira ticket number in ea...
Version control system commit comments are already very useful for many common development tasks, if done right (jira ticket number in each commit, commits divided properly, good commit messages with reasons for change). I wish there was more metadata there (like which tests failed during automatic build after each commit). But I disagree using text as underlying data format is a problem. It's godsend. Text can be grepped, copy-pasted, diffed and versioned easily. I cringe when I have to work with versioned word or excel documents. Working with versioned code is much easier. you may think big red arrow would be nice to put in code, but how do I later search for all red arrows related to X, added by John between 3 and 4 months ago? I have specification divided into 100s of versioned office documents. When I want to grep I have to know where to look (or zipgrep the underlying xml, which sometimes work sometimes doesn't). If it was in a text format I could grep and see real differences, not edit history. If it had embedded video I would need to watch the whole thing. And no - adding keywords isn't much help. I want to be able to search by content.
Comments (0)
No comments yet. Start the discussion.