Keeping track. Something I do with professional projects
-
I typically keep a /notes folder under my professional work such that I can write down pertinent things that come up as the project progresses such as technical points from a phone conversation relevant to the completing the software project (what hardware driver ICs are being used for example) It does a few things. It keeps me organized, and keeps my notes safely in source control. It also keeps things handy for other people I work with to go through. It's very simple to do, and it has proven invaluable to me time and again.
To err is human. Fortune favors the monsters.
You are doing what many professionals do, i.e. Lawyers, doctors, engineers, etc. do whatever style format etc that works for you. I try to summarize from time to time for clarity of purpose and the look at next stages. It is also important to note that they are not just for you.
"A little time, a little trouble, your better day" Badfinger
-
I typically keep a /notes folder under my professional work such that I can write down pertinent things that come up as the project progresses such as technical points from a phone conversation relevant to the completing the software project (what hardware driver ICs are being used for example) It does a few things. It keeps me organized, and keeps my notes safely in source control. It also keeps things handy for other people I work with to go through. It's very simple to do, and it has proven invaluable to me time and again.
To err is human. Fortune favors the monsters.
Heck, at my age I keep notes to remind me which room I last visited.
Will Rogers never met me.
-
Heck, at my age I keep notes to remind me which room I last visited.
Will Rogers never met me.
-
Must be nice. I work from home with minimal development infrastructure. It works for me, but it does mean being flexible and willing to work with rough tools.
To err is human. Fortune favors the monsters.
Sorry, I forgot. I get used to my company paying for everything because they have the budget. I imagine there are less expensive/enterprisey tools out there.
-
DevOps provides our team this ability. One single user story or bug is tied to all code reviews, work tasks, and deployments, testing, etc. Notes are usually added to the user story or bug. We also have Wikis as part of our individual repos so that developers can add/edit/view dev related resources regarding that particular repo code, etc.
Slacker007 wrote:
One single user story or bug is tied to all code reviews
Just noting that that is somewhat of a short term solution. Saying that because I have seen the same thing. What happens is that 5 years or perhaps 10 years from now they will change systems. And now that story/bug is gone. Or they might decide to re-org the original ticketing system. So now there is a location for the 'new' story/bugs and different one for the 'old' ones.
-
(and don't forget the string on your finger)
Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver
-
DevOps provides our team this ability. One single user story or bug is tied to all code reviews, work tasks, and deployments, testing, etc. Notes are usually added to the user story or bug. We also have Wikis as part of our individual repos so that developers can add/edit/view dev related resources regarding that particular repo code, etc.
That's how I work as well. Usually working in a team, I first describe in the wiki what I'm going to implement and how. This then serves as a "discussion board" and as later documentation.
Check out my blog at http://msdev.pro/
-
I typically keep a /notes folder under my professional work such that I can write down pertinent things that come up as the project progresses such as technical points from a phone conversation relevant to the completing the software project (what hardware driver ICs are being used for example) It does a few things. It keeps me organized, and keeps my notes safely in source control. It also keeps things handy for other people I work with to go through. It's very simple to do, and it has proven invaluable to me time and again.
To err is human. Fortune favors the monsters.
Same, I'm a bit more messy so I keep a handful of plain text diaries and all the e-mails pertinent to the requirements / technical part of the stuff plus a transcript of the chats or phone calls.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
-
I typically keep a /notes folder under my professional work such that I can write down pertinent things that come up as the project progresses such as technical points from a phone conversation relevant to the completing the software project (what hardware driver ICs are being used for example) It does a few things. It keeps me organized, and keeps my notes safely in source control. It also keeps things handy for other people I work with to go through. It's very simple to do, and it has proven invaluable to me time and again.
To err is human. Fortune favors the monsters.
Absolutely. Each client has their own folder, each project has its own subfolder. In there is an
/adminfolder which contains invoice PDFs, contracts, a "WIP" document so I know what I'm actually working on, and anotes.txtfile. I open that up in Notepad and hitF5(to date/timestamp the entry) then make a brief note of a meeting actions, personnel changes, strategic stuff they client discusses etc. Periodically I will clear out defunct / superseded stuff. It's in Notepad so I can access it really fast, andF5is so useful. For support stuff (which is about all I do these days) I also have atasks.txtfile; againF5timestamped and a very quick summary of time spent and task undertaken. That gets transcribed into an invoice at month-end. I should really do it direct into Excel (which I use for invoicing) but have a single Excel file for all the invoice spreadsheets for everyone, and with ~ 1000 invoices (each is a separate sheet) it's taking too long to open! :laugh:Telegraph marker posts ... nothing to do with IT Phasmid email discussion group ... also nothing to do with IT Beekeeping and honey site ... still nothing to do with IT
-
Absolutely. Each client has their own folder, each project has its own subfolder. In there is an
/adminfolder which contains invoice PDFs, contracts, a "WIP" document so I know what I'm actually working on, and anotes.txtfile. I open that up in Notepad and hitF5(to date/timestamp the entry) then make a brief note of a meeting actions, personnel changes, strategic stuff they client discusses etc. Periodically I will clear out defunct / superseded stuff. It's in Notepad so I can access it really fast, andF5is so useful. For support stuff (which is about all I do these days) I also have atasks.txtfile; againF5timestamped and a very quick summary of time spent and task undertaken. That gets transcribed into an invoice at month-end. I should really do it direct into Excel (which I use for invoicing) but have a single Excel file for all the invoice spreadsheets for everyone, and with ~ 1000 invoices (each is a separate sheet) it's taking too long to open! :laugh:Telegraph marker posts ... nothing to do with IT Phasmid email discussion group ... also nothing to do with IT Beekeeping and honey site ... still nothing to do with IT
You're more organized than I am, but I am a big proponent of people using what works for *them* in this case. Note taking shouldn't interfere with workflow or the development cycle in general, IMO. So for me I keep the organization relatively ... coarse I guess?
To err is human. Fortune favors the monsters.
-
I typically keep a /notes folder under my professional work such that I can write down pertinent things that come up as the project progresses such as technical points from a phone conversation relevant to the completing the software project (what hardware driver ICs are being used for example) It does a few things. It keeps me organized, and keeps my notes safely in source control. It also keeps things handy for other people I work with to go through. It's very simple to do, and it has proven invaluable to me time and again.
To err is human. Fortune favors the monsters.
I use OneNote and put in things like SQL queries I'm using, software setup etc. Writing down design decisions are also usefull since this solves a lot of the WTFs that come along later.
I doubt therefore I am.
-
I typically keep a /notes folder under my professional work such that I can write down pertinent things that come up as the project progresses such as technical points from a phone conversation relevant to the completing the software project (what hardware driver ICs are being used for example) It does a few things. It keeps me organized, and keeps my notes safely in source control. It also keeps things handy for other people I work with to go through. It's very simple to do, and it has proven invaluable to me time and again.
To err is human. Fortune favors the monsters.
Seriously - doesn't everyone do this?
-
I typically keep a /notes folder under my professional work such that I can write down pertinent things that come up as the project progresses such as technical points from a phone conversation relevant to the completing the software project (what hardware driver ICs are being used for example) It does a few things. It keeps me organized, and keeps my notes safely in source control. It also keeps things handy for other people I work with to go through. It's very simple to do, and it has proven invaluable to me time and again.
To err is human. Fortune favors the monsters.
-
I typically keep a /notes folder under my professional work such that I can write down pertinent things that come up as the project progresses such as technical points from a phone conversation relevant to the completing the software project (what hardware driver ICs are being used for example) It does a few things. It keeps me organized, and keeps my notes safely in source control. It also keeps things handy for other people I work with to go through. It's very simple to do, and it has proven invaluable to me time and again.
To err is human. Fortune favors the monsters.
-
Historically I've been a bad note taker. Recently I've started using Microsoft One Note and really like it.
Greetings, I've used everything from 3 ring binders (IBM Mainframes) to "Note" filling a folder with a scary amount of entries to OneNote, Excel and a home grown DB. And all of that was stored on my workstation as well as being emailed to my personal email account. (USB drives were verboten.) In many cases, the USB drive was disabled except for certain tech support logins. The built-in CD/DVD drive was limited to read-only. We had Dev Ops but after some notes 'disappeared' I carried on with my system (was told it wasn't needed :suss:) The person who deleted the entries claimed it was a 'mistake'. :doh: :rolleyes: :wtf: What ever...
Cegarman document code? If it's not intuitive, you're in the wrong field :D
-
I typically keep a /notes folder under my professional work such that I can write down pertinent things that come up as the project progresses such as technical points from a phone conversation relevant to the completing the software project (what hardware driver ICs are being used for example) It does a few things. It keeps me organized, and keeps my notes safely in source control. It also keeps things handy for other people I work with to go through. It's very simple to do, and it has proven invaluable to me time and again.
To err is human. Fortune favors the monsters.
I've been using Azure DevOps for all my code work, so I have my repo, tasks and other documentation altogether. I especially like that I can tie a commit to a particular story or task, so if I forget why I made a change, it's easy to follow the links...
-
I've been using Azure DevOps for all my code work, so I have my repo, tasks and other documentation altogether. I especially like that I can tie a commit to a particular story or task, so if I forget why I made a change, it's easy to follow the links...
It's nice when you have that kind of infrastructure. Currently I work for myself from home, so I am not similarly equipped. Nor do I work routinely but rather in spurts, so it doesn't really pay for me to have a subscription to anything major since I'll take a month sabbatical here and there. Necessity is the mother of invention, and I find keeping everything simple works well enough for me. :)
To err is human. Fortune favors the monsters.
-
It's nice when you have that kind of infrastructure. Currently I work for myself from home, so I am not similarly equipped. Nor do I work routinely but rather in spurts, so it doesn't really pay for me to have a subscription to anything major since I'll take a month sabbatical here and there. Necessity is the mother of invention, and I find keeping everything simple works well enough for me. :)
To err is human. Fortune favors the monsters.
I work from home to, as an independent contractor. And there is no cost to using Azure DevOps for small teams. I have several large repos there that I maintain. And it does make it easier when I can share the stories I am working on with my clients...
-
I work from home to, as an independent contractor. And there is no cost to using Azure DevOps for small teams. I have several large repos there that I maintain. And it does make it easier when I can share the stories I am working on with my clients...
Oh, i thought it was pay to play for professional stuff. thanks! :)
To err is human. Fortune favors the monsters.
-
Oh, i thought it was pay to play for professional stuff. thanks! :)
To err is human. Fortune favors the monsters.
It is certainly worth looking at it. I believe you can have up to 5 people who can access your AzDo site. And having a VS license doesn't count to that limit. Mind you, I haven't looked if any of this has changed. And there are services on it they they do charge for. But for the most part I have no problems with just using the free services