New Windows 10 Insider Preview Skip Ahead Build 18836 (20H1) -Feb. 14 Insider

Page 15 of 27 FirstFirst ... 5131415161725 ... LastLast
  1.    #140

    slicendice said: View Post
    @cereberus

    That is normal practice in software development. There could be multiple branches working on different things completely separate from each other. At some point a part from one branch merge with another when that particular part is done.

    I see absolutely no issue with this.

    This is MS we are talking about - many have been critical of their QA when relatively simple one development path. To have TWO development teams at different stages will definitely lead to Left Hand not knowing what the Right Hand is doing or vice versa - you are obviously more confident about the management ability of MS than I am - lol.
      My ComputerSystem Spec

  2. slicendice's Avatar
    Posts : 4,084
    Windows 10 Pro x64 v1809 Build 17763.379 (Branch: RS5 Release Preview)
       #141

    cereberus said: View Post
    This is MS we are talking about - many have been critical of their QA when relatively simple one development path. To have TWO development teams at different stages will definitely lead to Left Hand not knowing what the Right Hand is doing or vice versa - you are obviously more confident about the management ability of MS than I am - lol.
    I hear you on that! But the whole point of multiple forks, is that the left hand does not have to know anything about what the right hand is doing. It's when the forks join, when the teams comes together.
      My ComputersSystem Spec

  3. Brink's Avatar
    Posts : 37,060
    64-bit Windows 10 Pro build 18860
    Thread Starter
       #142

    I'm noticing the Microsoft Family icon showing in the notification area on the taskbar with this build even though I'm not in a family group.

    No process is running for it, and the icon doesn't do anything when clicking on it, hovering over it, or right clicking on it.

    Restarting the explorer process sorts it though.

    Click image for larger version. 

Name:	Microsoft_Family_icon.jpg 
Views:	71 
Size:	15.7 KB 
ID:	224617
      My ComputersSystem Spec

  4. magilla's Avatar
    Posts : 2,221
    Windows 10 and windows insider
       #143

    Brink said: View Post
    I'm noticing the Microsoft Family icon showing in the notification area on the taskbar with this build even though I'm not in a family group.

    No process is running for it, and the icon doesn't do anything when clicking on it, hovering over it, or right clicking on it.

    Restarting the explorer process sorts it though.

    Click image for larger version. 

Name:	Microsoft_Family_icon.jpg 
Views:	71 
Size:	15.7 KB 
ID:	224617
    On my computer, it is in the hidden area of my taskbar - along with Skype. So not displayed.
      My ComputerSystem Spec

  5. magilla's Avatar
    Posts : 2,221
    Windows 10 and windows insider
       #144

    My printers did not get installed in this build. Both are network printers.
      My ComputerSystem Spec

  6.    #145

    slicendice said: View Post
    I hear you on that! But the whole point of multiple forks, is that the left hand does not have to know anything about what the right hand is doing. It's when the forks join, when the teams comes together.
    I disagree somewhat. Suppose Team L rewrites some code to do L stuff and Team R rewrites same code for R stuff.

    When R and L merge, they will get all sorts of bugs arising from this and spend ages sorting it. On the other hand, if they worked together, things would be a lot smoother.

    BTW - I am talking from personal experience on this from my software development days - LOL!!

    It is basically the same as two people working on a report independently and not communicating - a blooming nightmare!
      My ComputerSystem Spec

  7.    #146

    cereberus said: View Post
    I disagree somewhat. Suppose Team L rewrites some code to do L stuff and Team R rewrites same code for R stuff. When R and L merge, they will get all sorts of bugs arising from this and spend ages sorting it. On the other hand, if they worked together, things would be a lot smoother.BTW - I am talking from personal experience on this from my software development days - LOL!!It is basically the same as two people working on a report independently and not communicating - a blooming nightmare!
    Absolutely agree. They can be working on completely different things, but need to collaborate to make sure not to screw up what is already working, or even help make their separate things play nice together down the road.
      My ComputerSystem Spec

  8. slicendice's Avatar
    Posts : 4,084
    Windows 10 Pro x64 v1809 Build 17763.379 (Branch: RS5 Release Preview)
       #147

    @cereberus

    That is what software engineers and lead programmers are for. You have a set of features that need to be implemented. Those features are then converted into APIs and specifications. At this stage there only exists a skeleton that does nothing. Now one programmer can take a single feature and make that API work according to the specification and another programmer can take another feature and focus on that. Neither have to ever worry about what the other does because the specification is already in place. The features are already separated by design, so there is a minimal risk that they will conflict once they merge into one code base.

    This is how I've done it and rarely have I had any issues. Although sometimes it is possible there exists a bug that can only be detected at runtime in a very specific workload. But this is what beta testing is for.
      My ComputersSystem Spec

  9. kado897's Avatar
    Posts : 24,607
    Windows 10 Home 64bit
       #148

    slicendice said: View Post
    @cereberus

    That is what software engineers and lead programmers are for. You have a set of features that need to be implemented. Those features are then converted into APIs and specifications. At this stage there only exists a skeleton that does nothing. Now one programmer can take a single feature and make that API work according to the specification and another programmer can take another feature and focus on that. Neither have to ever worry about what the other does because the specification is already in place. The features are already separated by design, so there is a minimal risk that they will conflict once they merge into one code base.

    This is how I've done it and rarely have I had any issues. Although sometimes it is possible there exists a bug that can only be detected at runtime in a very specific workload. But this is what beta testing is for.
    You are assuming that Win 10 is designed to allow for this separation.
      My ComputerSystem Spec

  10. slicendice's Avatar
    Posts : 4,084
    Windows 10 Pro x64 v1809 Build 17763.379 (Branch: RS5 Release Preview)
       #149

    kado897 said: View Post
    You are assuming that Win 10 is designed to allow for this separation.
    I'm not assuming, I know. Why else would Windows contain about 200k files? Just to have all files do the same thing?

    Besides, this is exactly what MS promotes themselves.

    Edit: One example: Anyone ever wondered why there are sometimes running 10-25 RuntimeBroker processes at the same time? That process does a lot of things useful for many applications.
      My ComputersSystem Spec


 
Page 15 of 27 FirstFirst ... 5131415161725 ... LastLast

Related Threads
UPDATE 9/12: New Windows 10 Insider Preview Skip Ahead Build 18237 - September 11 Insider - Windows 10 Forums Source: Announcing Windows 10 Insider Preview Build 18234 - Windows Experience Blog 1037747918785011712
UPDATE 8/10: New Windows 10 Insider Preview Skip Ahead Build 18214 - August 10 Source: Announcing Windows 10 Insider Preview Build 17723 and Build 18204 - Windows Experience Blog 1022226119003492357 1022226591999389696
994262202268860418 Source: Announcing Windows 10 Insider Preview Build 17666 - Windows Experience Blog Flight Hub | Microsoft Docs
UPDATE 4/4: Announcing Windows 10 Insider Preview Skip Ahead Build 17639 - April 4 Insider - Windows 10 Forums 979403654867296256 Source: Announcing Windows 10 Insider Preview Build 17634 for Skip Ahead - Windows Experience Blog
UPDATE: 9/27: Announcing Windows 10 Insider Preview Skip Ahead Build 17004 for PC Insider - Windows 10 Forums 908013519697616896 Source: Announcing Windows 10 Insider Preview Build 16362 for PC (Skip Ahead) - Windows Experience Blog
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:19.
Find Us