| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| background [2025/06/15 20:41] – admin | background [2025/06/17 16:58] (current) – admin |
|---|
| But the real world, especially when it comes to an individual is quite hazy and scruffy. So most individuals (when you pin them down to extract an honest answer) would really want their own control over the way things are organized for them. Given a choice, they don't want to keep filling up form after form-- they would rather get to the job itself. | But the real world, especially when it comes to an individual is quite hazy and scruffy. So most individuals (when you pin them down to extract an honest answer) would really want their own control over the way things are organized for them. Given a choice, they don't want to keep filling up form after form-- they would rather get to the job itself. |
| |
| The "law of the excluded middle" can even be seen in reductionist philosophy, which is evident in so many software. It is high time we now try an //Indian// way of tying a //lungi// holistically around the waist: The end user is in control. It is not dictated by power-point bullet points or forms with a horde fields or a sharp salesman selling a pair of Western trousers. | The "law of the excluded middle" can even be seen in reductionist philosophy, which is evident in so many software. It is high time we now try an //Indian// way of tying a //lungi// holistically around the waist: The end user is in control. It is not dictated by power-point bullet points or forms with hordes of input-fields or a sharp salesman selling a pair of Western trousers and force you to fit into slots. |
| |
| ====Lessons from Konkan Railway==== | ====Lessons from Konkan Railway==== |
| When an officer had to take a decision for a sub-project for some part of it -- say settling a contractor's bills, or approving the architect's drawing... the box-folder was retrieved from the central file storage and plonked on the officer's desk. The box-folder had all the papers received from various agencies for the sub-project arranged chronologically. | When an officer had to take a decision for a sub-project for some part of it -- say settling a contractor's bills, or approving the architect's drawing... the box-folder was retrieved from the central file storage and plonked on the officer's desk. The box-folder had all the papers received from various agencies for the sub-project arranged chronologically. |
| |
| The officer then locates the file relevant for his decision. That paper is flipped over and on the back of the paper (which is usually blank) the office would write his comments and sign and date that comment. The box-file then goes back to the central file-storage. | The officer then locates the file relevant for his decision. That paper is flipped over and on the back of the paper (which is usually blank) the officer would write his comments and sign and date that comment. The box-file then goes back to the central file-storage. |
| |
| The advantage of such as system is that it was not //reductionist.// The entire holistic of the sub-project are almost completely available in that box-file. If the officer had to search side-ways into other areas before taking a decision. Say the contractor's work was impinging on some conditions of the contract; there is no problem: The officer can shuffle thru the file and get the contract documents there itself. | The advantage of such as system is that it was not //reductionist.// The entire holistic of the sub-project are almost completely available in that box-file. If the officer had to search side-ways into other areas before taking a decision. Say the contractor's work was impinging on some conditions of the contract; there is no problem: The officer can shuffle thru the file and get the contract documents there itself. |
| When you work with //Git Winch// you would notice you can see shades of why some features were implemented the way they have been. And why is that //Git Winch// has such minimal features. But it can make an enormous difference in the way people and data are handled. | When you work with //Git Winch// you would notice you can see shades of why some features were implemented the way they have been. And why is that //Git Winch// has such minimal features. But it can make an enormous difference in the way people and data are handled. |
| |
| What Konkan Railway achieved with physical box files — clarity, completeness, and speed — Git Winch brings to the digital workspace. No scattered forms or hidden data; the whole story is available to those who need it, when they need it. At the same time, it does //not disrespect Western approach either// You can "divide-and-conquer" and setup separate repositories for sub-groups to work on a need to know basis. | What Konkan Railway achieved with physical box files — clarity, completeness, and speed — Git Winch brings to the digital workspace. No scattered forms or hidden data; the whole story is available to those who need it, when they need it. At the same time, it does //not disrespect Western approach either!// |
| | |
| | You can "divide-and-conquer" and setup separate repositories for sub-groups to work on a need-to-know basis. |
| |
| Git Winch isn't just another tool — it's an invitation to rethink how your team works: holistically, humanely, and without clutter. I hope you enjoy discovering this difference. | Git Winch isn't just another tool — it's an invitation to rethink how your team works: holistically, humanely, and without clutter. I hope you enjoy discovering this difference. |