Re: [OT] node.js and express

Oh yes Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com _ From: David Connors mailto:da...@connors.com>> Sent: Monday, November 28, 2016 12:1

Re: [OT] node.js and express

IMO these "influential technical people" and vendors just see it as an opportunity to add their name to something new and therefore keep their jobs a bit longer. Plus doing the same old thing is boring so anything new can be a good change even if the old thing was "better". On Monday, 28 November

Re: [OT] node.js and express

On Mon, 28 Nov 2016 at 10:56 Scott Barnes wrote: > "...Everytime I see a developer use multi-threading I think to myself, > thank you for keeping future consultancy billables alive" - Anonymous > Most developers who create messes don't know what a thread is. Personally, I thank whoever invented

Re: [OT] node.js and express

> > I **think** Greg Keogh started with this with some investigations on how > hard it was to implement something using framework/technique X. Cool. You > have learnt what not to do, not how to do something with the latest tech > just because Scott Hanselmann mentioned it. > Yeah sorry, it started

RE: [OT] node.js and express

Whilst, as consultants, we might like the mess that the unqualified/naïve/incompetent generate, in the sense that it creates more work for the rest of us, I do fear that customers don’t like that sort of environment. Other professional industries have become regulated, standardised and/or comm

Re: [OT] node.js and express

To your point about unqualified devs Dave :- "...Everytime I see a developer use multi-threading I think to myself, thank you for keeping future consultancy billables alive" - Anonymous The more chaos the web devs breed the more the seasoned devs can pick up the win falls from that. --- Regard

Re: [OT] node.js and express

On Mon, 28 Nov 2016 at 10:13 Mark Hurd wrote: > This is getting an off-topic post even more general, but this thread > also suggests to me part of why we're a hard industry to get proper > engineering-level standards applied. > I had a great chat about this with one of our engineers last week as

Re: [OT] node.js and express

This is getting an off-topic post even more general, but this thread also suggests to me part of why we're a hard industry to get proper engineering-level standards applied. We might start to apply standards, but then the technology shifts from under us and the standards are out of date. We then n

RE: [OT] node.js and express

If you were to start a new Enterprise Web Project which has the potential to be continually developed and enhanced over 5 to 10 years what web technology frameworks would you choose? Regards Adrian Halid From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On B

Re: [OT] node.js and express

On Sun, 27 Nov 2016 at 20:32 Paul Glavich wrote: > You have learnt what not to do, not how to do something with the latest > tech just because Scott Hanselmann mentioned it. > This made me chuckle. David. -- David Connors da...@connors.com | @davidconnors | LinkedIn | +61 417 189 363

RE: [OT] node.js and express

Yeah pretty much :) I am a web guy through and through and I don’t mean to hack on people specifically, but as an industry it still manifests as real immaturity. I also don’t mean to suggest we don’t use and play with the new stuff either but the level of acceptance, particularly from people

Re: [OT] node.js and express

So Paul, you're basically saying "The standard we walk past, is the standard we accept" hehe :) --- Regards, Scott Barnes http://www.riagenic.com On Sun, Nov 27, 2016 at 8:31 PM, Paul Glavich wrote: > Ahh the recurring thread about how immature the JS/Web dev community is > and how hard it is t

RE: [OT] node.js and express

Ahh the recurring thread about how immature the JS/Web dev community is and how hard it is to do anything “right”. All I will say is we asked for it. If we didn’t ask for it, we accepted it. If we didn’t accept it, we assumed that the new was good and ran with it. We make a whole lot of a