Sujet : Re: Serial, concurrent, parallel
De : jl (at) *nospam* glen--canyon.com (john larkin)
Groupes : sci.electronics.designDate : 17. Jan 2025, 00:36:09
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <qs5joj56ihh1h3okjoisi13tf58b7bpu8t@4ax.com>
References : 1 2 3 4
User-Agent : ForteAgent/8.00.32.1272
On Thu, 16 Jan 2025 23:02:28 +0000, brian <
nospam@b-howie.co.uk>
wrote:
In message <rraiojlip0hl9vjaa742fmtq9dpmo2v2l1@4ax.com>, john larkin
<JL@gct.com> writes
On Thu, 16 Jan 2025 15:10:37 +0000, brian <nospam@b-howie.co.uk>
wrote:
>
In message <vm69a2$2h52d$1@dont-email.me>, Don Y
<blockedofcourse@foo.invalid> writes
I am surprised (disturbed?) at the problems people seem to have
sorting these things out in their thought processes. I don't
*believe* people think strictly "serially" but I am beginning to
question that belief as I witness smart/capable people stuck in
that mindset!
>
It's simple project engineering and resource management . PERT ,
Critical path analysis, lead times , Gantt charts, even Microsoft
Project if you must. You must be talking to non-engineers.
>
Brian
>
The more such management tools that you use, the slower a project will
go.
>
The key observation is that when things are serialized, they happen
sequentially.
>
>
PERT and the like handles parallel processing paths , in fact it almost
forces you do it . When things are concurrent they happen in parallel .
>
B .
More software management tools not only slow down a design project,
you need people to drive the tools too.
Date | Sujet | # | | Auteur |
14 Jan 25 | Serial, concurrent, parallel | 35 | | Don Y |
14 Jan 25 |  Re: Serial, concurrent, parallel | 9 | | Liz Tuddenham |
14 Jan 25 |   Re: Serial, concurrent, parallel | 8 | | Don Y |
14 Jan 25 |    Re: Serial, concurrent, parallel | 7 | | Liz Tuddenham |
15 Jan 25 |     Re: Serial, concurrent, parallel | 6 | | Don Y |
16 Jan 25 |      Re: Serial, concurrent, parallel | 5 | | Liz Tuddenham |
16 Jan 25 |       Re: Serial, concurrent, parallel | 4 | | Don Y |
16 Jan 25 |        Re: Serial, concurrent, parallel | 3 | | Liz Tuddenham |
16 Jan 25 |         Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |         Re: Serial, concurrent, parallel | 1 | | ehsjr |
16 Jan 25 |  Re: Serial, concurrent, parallel | 20 | | Martin Brown |
16 Jan 25 |   Re: Serial, concurrent, parallel | 19 | | Don Y |
16 Jan 25 |    Re: Serial, concurrent, parallel | 16 | | Liz Tuddenham |
16 Jan 25 |     Re: Serial, concurrent, parallel | 13 | | Don Y |
16 Jan 25 |      Re: Serial, concurrent, parallel | 12 | | Liz Tuddenham |
16 Jan 25 |       Re: Serial, concurrent, parallel | 5 | | Don Y |
17 Jan 25 |        Re: Serial, concurrent, parallel | 4 | | Liz Tuddenham |
17 Jan 25 |         Re: Serial, concurrent, parallel | 3 | | Don Y |
17 Jan 25 |          Re: Serial, concurrent, parallel | 1 | | Don Y |
17 Jan 25 |          Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |       Re: Serial, concurrent, parallel | 6 | | Edward Rawde |
17 Jan 25 |        Re: Serial, concurrent, parallel | 5 | | Don Y |
17 Jan 25 |         Re: Serial, concurrent, parallel | 4 | | Edward Rawde |
17 Jan 25 |          Re: Serial, concurrent, parallel | 3 | | Don Y |
17 Jan 25 |           Re: Serial, concurrent, parallel | 2 | | Edward Rawde |
17 Jan 25 |            Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |     Re: Serial, concurrent, parallel | 2 | | Martin Brown |
16 Jan 25 |      Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |    Re: Serial, concurrent, parallel | 2 | | Martin Brown |
16 Jan 25 |     Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |  Re: Serial, concurrent, parallel | 5 | | brian |
16 Jan 25 |   Re: Serial, concurrent, parallel | 3 | | john larkin |
17 Jan 25 |    Re: Serial, concurrent, parallel | 2 | | brian |
17 Jan 25 |     Re: Serial, concurrent, parallel | 1 | | john larkin |
16 Jan 25 |   Re: Serial, concurrent, parallel | 1 | | Don Y |