Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Alex Newsgroups: comp.lang.forth Subject: Re: Really? Date: Mon, 13 Feb 2017 09:49:31 +0000 Organization: A noiseless patient Spider Lines: 47 Message-ID: References: <1239a88b-a574-401b-9454-50ac7e000049@googlegroups.com> <20170206233939.70a7ecff@_> <17e4a172-bc40-47e7-b7e1-f2e60f6802de@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Mon, 13 Feb 2017 09:47:42 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="7cbf50e1e5552b951eeb4ec9c42a668e"; logging-data="32256"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1954ji+gfOO+PU8o2ll6aBGISewbCudhSk=" User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 In-Reply-To: Cancel-Lock: sha1:o16ybLqxliHvhX/5Bkt0nJZubyY= Xref: csiph.com comp.lang.forth:54835 On 2/13/2017 00:52, hughaguilar96@gmail.com wrote: > You have repeatedly claimed that you "do standards for a living" --- > how is that working out for you? LOL Very well thanks. Right now, I'm spending some of my time working with a number of companies on developing and promoting new hardware specs and a new programming model that the industry needs to support persistent memories. PM typically has latencies between current flash and DRAM; in the 10s of nS. It's an interesting & challenging development that's changing the way we think about providing and using both memory and storage. PM bridges the gap between them, and treating it as storage (a block based storage device with an I/O stack) or memory (a byte addressable load/store memory) doesn't take full advantge of its capabilities. It's early days though; we're probably nearly a decade away from this stuff being mainstream. For anyone that's interested; https://www.snia.org/forums/sssi http://www.snia.org/tech_activities/standards/curr_standards/npm > The only way this could work, is if there is one team member who is > generally acknowledged to be brilliant, and all of the other team > members cheerfully accept that they are incompetent and can never be > anything except code monkeys who program according to the detailed > spec provided by their brilliant leader. Interesting CV you have. There are several models for organising and managing software development, and I would not claim to be an expert. But I see several models; perhaps the most famous of which is the "benevolent dictator" model employed by Linux. Even there, the scale of the project is such that there are tens of "dictators", for various project parts of the whole. One of the teams with which I am familiar has several members, many of whom are employed by the same company; but some of whom work for other companies and are effectively working remotely. The persona of genius programmer (and presumably genius project manager too) that you describe is one I only see on one-person projects. A few, very few, succeed. Apple's Jobs, Torvald's Linux. Most loners are destined to write software that will be used by them alone. The practicalities of the real world are messy and inefficent and require teamwork and compromise at all levels. -- Alex