Groups | Search | Server Info | Login | Register
Groups > sci.electronics.design > #739913
| From | Don Y <blockedofcourse@foo.invalid> |
|---|---|
| Newsgroups | sci.electronics.design |
| Subject | Re: good post on LinkedIn |
| Date | 2026-01-30 09:56 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <10linsv$28d57$1@dont-email.me> (permalink) |
| References | (2 earlier) <a466fba3-4f96-5968-faef-db94f1e721a5@insomnia247.nl> <10j77ll$12g8$1@paganini.bofh.team> <10lfqlq$3ji9g$1@paganini.bofh.team> <10li54l$21j3m$2@dont-email.me> <bmepnkpikq74292em8uqlimgfakspqanvr@4ax.com> |
On 1/30/2026 7:24 AM, legg wrote: > >> I can't comment on LinkedIn as no one that I know uses it. >> My understanding (?) is that it is a networking site -- a >> way to "get jobs". > > You may be thinking of InDeed. No, LinkedIn. AFAICT, it just lets folks advertise other people that they know/endorse. The practical effect of that is referrals (which is another way of saying "get jobs"). >> Most of my colleagues have more than enough work without >> any sort of "advertising" or "job mining". Makes you wonder >> what the folks using it are lacking... (REAL contacts??) > > Networking is just keeping track of co-workers and professional > acquaintances - but there's no real controls on spam. And, you need a third-party "site" to do that? Don't you *personally* interact with your colleagues -- even if only sporadically? If I'm contacted about a potential job, I think about the people that I know who might be appropriate (because anyone that I *refer* for a position is a reflection on me!). Who (if anyone) I contact is based on my knowledge of where their interests lie and what they might be doing, presently. I know those things because of communications with them *directly* -- not by "reading about them" on a site. They are more than "business relationships" but, rather, *personal* relationships (e.g., knowing when someone is in ill health, having a baby, planning a vacation, etc.) It also lets you share things in the strictest of confidence; things that you (or a business relationship of yours) may not want discussed or disclosed "publicly". > It has groups, similar to Facebook, where an administrator can > keep things relatively clean. The longer running of these usually > has some commercial incentive for the admin. > > 20yrs ago it was pretty useful. These days ~ 'Power Electronic > Management' is a style of managment. Most groups are heavily > burdened with 'user-posted' advertizing. Interacting directly with colleagues doesn't suffer from these sorts of problems. No one is going to "pitch" anything to me or expect me to pitch something to them. Because "contact" is an intrusion (of sorts) and should be worth that "burden". > Tapping into 20 year old threads (where all the good references > and articles were being discussed)in such a group is well-night > impossible. > > Like Facebook, it is heavily dependent on your machines' RAM and > is unfriendly to non-google, non-chrome browsers. This may be > why Edge is having issues: it would serve MS right. Another way to waste resources (in this case, your time!).
Back to sci.electronics.design | Previous | Next — Previous in thread | Next in thread | Find similar
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-29 14:26 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-29 09:04 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-29 17:57 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-29 10:59 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 00:48 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-29 17:01 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 01:28 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 15:14 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 11:52 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:05 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 12:34 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:29 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 20:59 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 03:06 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-02 00:17 +1100
Re: Excel and accountants, good post on LinkedIn John Levine <johnl@taugh.com> - 2026-01-31 23:21 +0000
Re: Excel and accountants, good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 16:22 -0800
Re: Excel and accountants, good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-02-01 02:13 +0000
Re: Excel and accountants, good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 19:31 -0700
Re: Excel and accountants, good post on LinkedIn albert@spenarnc.xs4all.nl - 2026-02-01 21:58 +0100
Re: Excel and accountants, good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-02-01 14:36 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 03:56 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 15:23 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 14:36 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 21:31 +1100
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-30 14:59 +1100
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 10:15 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 00:06 +1100
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-30 13:43 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 02:18 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 08:04 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 03:51 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 09:46 -0800
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 20:00 +0000
Re: good post on LinkedIn Jeroen Belleman <jeroen@nospam.please> - 2026-01-30 22:49 +0100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-30 22:52 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:02 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 13:33 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 01:31 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 19:16 +0000
Re: history of Fortran, good post on LinkedIn John Levine <johnl@taugh.com> - 2026-01-31 23:10 +0000
Sorry re history of Fortran, good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 23:25 +0000
Re: Sorry re history of Fortran, good post on LinkedIn John Levine <johnl@taugh.com> - 2026-02-01 02:43 +0000
Re: Sorry re history of Fortran, good post on LinkedIn OrangeFish <OrangeFish@invalid.invalid> - 2026-02-01 18:00 -0500
Re: history of Fortran, good post on LinkedIn albert@spenarnc.xs4all.nl - 2026-02-01 22:11 +0100
Re: history of Fortran, good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-02-01 14:42 -0700
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 21:36 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 15:53 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:14 +1100
Re: good post on LinkedIn Jeroen Belleman <jeroen@nospam.please> - 2026-01-31 11:21 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:34 -0800
Re: good post on LinkedIn Jeroen Belleman <jeroen@nospam.please> - 2026-01-31 21:42 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 13:36 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 21:57 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 03:10 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-02 00:37 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 07:36 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-03 16:27 +1100
Re: good post on LinkedIn albert@spenarnc.xs4all.nl - 2026-02-01 22:21 +0100
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-31 09:00 +0000
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 15:45 +1100
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 14:26 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 13:53 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-01-31 16:25 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:41 -0800
Re: good post on LinkedIn Gerhard Hoffmann <dk4xp@arcor.de> - 2026-01-31 17:33 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 10:07 -0800
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 11:26 -0700
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-01 22:04 +1100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-02-01 07:38 -0800
Re: good post on LinkedIn Bill Sloman <bill.sloman@ieee.org> - 2026-02-03 16:37 +1100
Re: good post on LinkedIn Gerhard Hoffmann <dk4xp@arcor.de> - 2026-01-30 15:06 +0100
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 11:55 -0800
Re: good post on LinkedIn wmartin <wwm@wwmartin.net> - 2026-01-30 11:27 -0800
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 18:54 -0800
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 23:26 -0700
Re: good post on LinkedIn liz@poppyrecords.invalid.invalid (Liz Tuddenham) - 2026-01-31 09:22 +0000
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 02:50 -0700
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 04:36 -0700
Re: good post on LinkedIn legg <legg@nospam.magma.ca> - 2026-01-30 09:24 -0500
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 09:56 -0700
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 10:05 -0700
Re: good post on LinkedIn legg <legg@nospam.magma.ca> - 2026-01-30 14:22 -0500
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 19:09 -0700
Re: good post on LinkedIn legg <legg@nospam.magma.ca> - 2026-01-30 22:16 -0500
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 22:27 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 03:40 +0000
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-30 22:46 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 15:20 +0000
Re: good post on LinkedIn Don Y <blockedofcourse@foo.invalid> - 2026-01-31 08:44 -0700
Re: good post on LinkedIn Nioclás Pól Caileán de Ghloucester <thanks-to@Taf.com> - 2026-01-31 17:13 +0000
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-31 07:55 -0800
Re: good post on LinkedIn john larkin <jl@glen--canyon.com> - 2026-01-30 08:15 -0800
csiph-web