November 13, 2025 at 6:10 pm
You often need a bigger team to build a system than you do to keep it running once implemented, so it makes sense for some of that team to be hired from outside so that they can leave at the end of the project. Of course you also need a few people from inside the company working on the project otherwise you'll have no-one left who understands the system/platform. Knowledge transfer from the external experts to the internal learners is key during the build phase.
People leaving is hard. I find most orgs don't have a good way to manage people out.
November 14, 2025 at 4:36 am
<snip />
I'm just curious, what skills do they have that they are not sharing? I keep thinking I need to future proof my career by adding some expertise in open source, but I never seem to have time.
Two come to mind. They have worked together using React, which if you don't know about it is a JavaScript approach to doing web development. It is very popular. I'm not particularly good at JavaScript. The second skill is Microsoft's Blazor. Its similar in approach and style to Reach, but using C# instead of JavaScript and relies upon WebAssembly to enable writing C# on the client (the web browser). (That is what I do and use.) Anyway, they don't share any of that with anyone else. I'm teaching myself Blazor, because I cannot break into their clique.
Rod
Viewing 2 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply