Writing Master thesis proposals for next year. If you're interested in working in RFID and the Internet of Things, send me a message! segunda-feira, 29 de Março de 2010 14:51:54
Learning Groovy, unlearning Java :-) quarta-feira, 24 de Março de 2010 14:35:25
Off to meetings with Master students segunda-feira, 22 de Março de 2010 14:31:30
Worried quinta-feira, 18 de Março de 2010 11:52:47
Once again back in writer mode. This task switching thing is hard. I wonder how computers cope with it 1000 times a second ;-) terça-feira, 16 de Março de 2010 14:08:43
@joanappardal It was worth it! quinta-feira, 11 de Março de 2010 10:59:08 in reply to joanappardal
Good morning! Let's get to work! quinta-feira, 11 de Março de 2010 08:47:24
Paper is finished. Back to dev mode. quarta-feira, 10 de Março de 2010 16:41:56 via Echofon
Listening to Carminho... What a voice! quarta-feira, 10 de Março de 2010 13:13:58 via Echofon
Proofreading a paper quarta-feira, 10 de Março de 2010 11:37:42 via Echofon
It feels so good to have sunshine in Lisbon after all the rain in the past few days. terça-feira, 9 de Março de 2010 17:00:13 via Echofon
Projecto Encruzilhadas http://emprego-projectoencruzilhada.ning.com terça-feira, 9 de Março de 2010 13:33:54
New dolphins http://sparrowflights.blogspot.com/2010/03/from-now-on.html segunda-feira, 8 de Março de 2010 20:19:29
Meeting's over. There will be another one next week. segunda-feira, 8 de Março de 2010 18:00:48
Meeting with MSc students at Sala de Dúvidas do DEI. You can stop by if you're interested in research about the Internet of Things segunda-feira, 8 de Março de 2010 14:56:57
Automating Tomcat testing sexta-feira, 5 de Março de 2010 14:14:11
@joanappardal Loved the wonderful pizza lunch - Da Beppi - on wheels! quarta-feira, 3 de Março de 2010 15:02:18
After a writing break, back to developer mode, working on the STEP framework terça-feira, 2 de Março de 2010 13:48:19
2010-03-31
2010-03-24
My developer workbench
A very dear friend is having a hard time getting back into 'developer shape', so I decided to blog about how I organize my developer work files:
/dev
This is where I keep the current projects I am working on.
It is important to me to keep this folder as clean as possible.
If I have a project that is inactive, I just create a ZIP archive and delete it.
/dev/examples
This is where I keep code examples, historically called the 'grrreat tests' :-) (Miguel and João, you know why)
The idea is to keep small projects, each with a single purpose. It is the best way to test libraries before using them in larger projects.
I get snippets from here all the time. If you don't know, snippets are fragments of code that can be copy-pasted and easily reused.
/devlib
This is a collection of libraries. You can save a lot of time reusing existing code and learning from it.
The collection is organized in 3 sections: dist, doc, and source; for binaries, documentation, and source code, respectively.
I keep multiple versions of libraries, each in a separate subfolder, because sometimes it is useful to compare changes, using a tool like WinMerge.
If you only take away one thing, remember that single-purpose code examples are the way to write quality code, fast!
Feel free to share comments about your development practices. I'm always looking for ways to improve!
/dev
This is where I keep the current projects I am working on.
It is important to me to keep this folder as clean as possible.
If I have a project that is inactive, I just create a ZIP archive and delete it.
/dev/examples
This is where I keep code examples, historically called the 'grrreat tests' :-) (Miguel and João, you know why)
The idea is to keep small projects, each with a single purpose. It is the best way to test libraries before using them in larger projects.
I get snippets from here all the time. If you don't know, snippets are fragments of code that can be copy-pasted and easily reused.
/devlib
This is a collection of libraries. You can save a lot of time reusing existing code and learning from it.
The collection is organized in 3 sections: dist, doc, and source; for binaries, documentation, and source code, respectively.
I keep multiple versions of libraries, each in a separate subfolder, because sometimes it is useful to compare changes, using a tool like WinMerge.
If you only take away one thing, remember that single-purpose code examples are the way to write quality code, fast!
Feel free to share comments about your development practices. I'm always looking for ways to improve!
2010-03-08
Subscribe to:
Posts (Atom)