| User | Post |
|
7:06 am
November 14, 2009
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
In devising the current workgroup structure I was trying hard to minimise the total number of groups to keep things simple. However, I'm really not sure whether or not it would be wise to have a separate group for software engineering. That will be a huge part of this project, requiring strict revision management, code reviews, quality control, benchmarking, etc. A lot of that stuff is quite separate from choosing computer hardware, operating system configuration, networking, data redundancy, etc. Do people think it is worth splitting this group in two?
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
8:19 am
December 24, 2009
|
PKillian
| | Green Bay, Wisconsin | |
| Member | posts 6 | |
|
|
In time as more of the software/hardware systems become defined and materialize, I definitely think 2 highly coupled groups of software engineers and technical people will be very necessary. But at this moment, gauging from the current status of things I witness I do not think it is an immediate concern.
|
|
|
7:52 am
December 26, 2009
|
Ichabond
| | Belgium | |
| Member | posts 4 | |
|
|
I would have to agree with PKillian, in due time it would be easier for development to have the hardware guys separated from the software guys, but they would still need to communicate, so wouldn't it be possible to have a Software and Hardware supergroup, with Hardware and Software, 2 separate subgroups, running next to each other, and reporting on advancements every week/month/whatever, so both can sync up, and adjust where necessary.
|
|
Login 
Register 
Search 
Home
Topic RSS 
