Every 5 minute conversation I have in Teams means I need to spend 10 minutes documenting it across different channels since their search sucks. That said, I dislike Teams for all of the same reasons. Then they have to do it for different locales, examine their contracts with governments (they can't provide a function in one language that isn't available in another in order to keep up their Thai contract, for instance- so how do they deal with Japanese/Spanish lexeme search functions?) I can't imagine how many use cases I'd have to write up for that. This could be a few hundred feature request / bugs. The line items have not yet been distilled into feature request / bugs. This process would occur for each feature request / bug. I agree that there are many features that could be done in parallel. I only wanted to point out the complexity of adding a well-defined feature. None of these take very long individually, but they add up, and this is for a simple feature.You'll note that I haven't added all the things that Joe talks about, like what if there is a bug in those five lines of code? That initial five minutes of dev time translates into many person-weeks of work and enormous costs, all to save one person a few minutes of whipping up a one-off VB6 control that does what they want.
#Salesforce acquires slack update#
One documentation manager to integrate the new documentation into the existing body of text, update tables of contents, indexes, etc.One copy editor to proofread the documentation.One technical reviewer to proofread the documentation.One technical writer to write the documentation.Three or four testers to participate in an ad hoc bug bash.One tester to write the test cases and add them to the nightly automation.One test lead to update the test schedule.One PM to add the security model to the specification.At least one dev, tester and PM to brainstorm security vulnerabilities.One usability expert to review the specification for accessibility and usability issues.One localization expert to review the specification for localizability issues.
One program manager to write the specification.One dev to spend five minutes implementing ChangeLightBulbWindowHandleEx.But how many Microsoft employees does it actually take to change a lightbulb?
#Salesforce acquires slack code#
I'd always tell these people the same thing - if it is only five lines of code then go write your own ActiveX object! Because yes, you are absolutely right - it would take me approximately five minutes to add that feature to the VBScript runtime library. This link gave me perspective on what it costs to implement a single feature at Microsoft: Are you interested in promoting your own content? STOP! Read this first.For posting job listings, please visit /r/forhire or /r/jobbit.Do you have something funny to share with fellow programmers? Please take it to /r/ProgrammerHumor/.Do you have a question? Check out /r/learnprogramming, /r/cscareerquestions, or Stack Overflow.Direct links to app demos (unrelated to programming) will be removed.If there is no code in your link, it probably doesn't belong here. Just because it has a computer in it doesn't make it programming.That means no image posts, no memes, no politics.Please keep submissions on topic and of high quality.r/programming is a reddit for discussion and news about computer programming
0 kommentar(er)
