Virtual bombs and Immersive Reader transform learning intervention
They can repeat scripts or tell you what negotiation means – but when they are having to perform that themselves it can be a real challenge. What the game does is make that meaningful so they understand why they need to do these things – it creates opportunities to teach social skills.
https://devpost.com/software/augmented-reality-treatment-for-autistic-children
Integrate more scenarios, children will have the opportunity to play with others and animals. Expand the product to adolescents be developing more complex scenarios All levels would have different instances to show altruistic behavior some obvious while others being more subtle. At the end of the interaction an empathy score can be obtained.
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5483849/
The BPS collects quantitative data about the user’s environment and interactions through the use of an array of inbuilt sensors and analyzes these data through the use of artificial intelligence (AI), including the use of Affdex emotion AI (Affectiva, Boston, MA, USA) (28).
Collecting data is much easier comparing to human therapists.
Brain Power System applications have been designed with the goal of enhancing social and cognitive skills development in children and adults with ASD.
Two key theories have been put forward to help explain the diminished eye contact in autism, gaze aversion, and gaze indifference. Gaze aversion suggests that the individual with ASD actively avoids eye contact as it is threatening, anxiety-inducing, or linked to physiologic overstimulation (35–37). Gaze indifference, on the other hand, supports the notion that reduced eye contact in ASD may be a passive phenomenon, where the eyes of others are not seen as being engaging or a relevant stimulus (38). Certainly, given the heterogeneity seen in ASD, different theories may hold true for different individuals.
Face Game provides for multiple different levels, and as the user progresses, the digital elements gradually become more subtle, while real-world interactions are emphasized.
Smartglasses may offer a number of distinct advantages compared to applications delivered via smartphones. With smartglasses, users are heads-up as opposed to immersed in a screen, and they remain hands-free, thus able to use their hands to engage in both non-verbal social communication and undertake educational/occupational tasks. This type of mobile and lightweight technology allows users to coach themselves in the privacy of their own home, and whenever is most convenient. Finally, such technology can be rapidly scaled to meet demands.
https://link.medium.com/LSCnr0TjA0
As you can see the Scrum Master is NOT the person to update people on the progress. This is for the Product Owner and the Development Team to do and they make use of the artifacts and the Sprint Review to achieve this. This makes other types of progress reporting redundant.
Extra report may be the single most visible sign of a team not being truly agile.
https://mp.weixin.qq.com/s/xARKh-YMUtNsrJUd1ZUJzA
就此，很多人归因为华人不肯交际，英语不好，不善于沟通，不参与社区活动，等等五花八门的原由。
其实找个反例很容易。
那就是半导体行业。
一个有趣的现象是硅谷的主要大型半导体公司的老总，目前都是华裔。
不去思考理解行业变迁背后的群体行为特征，试图以个人看得见的努力，和看不见的群体规律做对，往往被玻璃天花板碰得头破血流，代价巨大。
理工科做技术的人，类似古代的武将，虽然出活出力流血流汗，但是如果不能掌握产业链各个环节上关键资源的控制力，则往往悲催的沦为他人的工具，其下行的风险远远大于上行的回报。
有些理工科背景者长期唯技术论，对于整个产业链的架构/市场定位等等，缺乏基本理解，迷恋于一种对于硬核技术的自我陶醉 （类似于天天慷慨悲歌，打打杀杀的武将），对自己的弱点和短板缺乏基本认识，对于非技术人员有一种（出于无知而导致的）鄙视情绪，其状态和这些武将非常类似。
该埋头苦干的时候别到处看。抬起头来看的时候看清楚自己的位置。
不要看不起一些现象，只要不毁三观，大概率是自己有认知漏洞，就算毁三观，也有一半可能性是自己三观过时了。
10 Signs You Don’t Do Continuous Delivery
My take away is, all those things created throughout decades to help smoothen the process of pushing code once in a “long” while become evils in the CD world.
By “long”, it could be a day, a week, a month, or a year.
Those things include release management, feature branches, dedicated deployment team, village exercise, etc.
The right way to deal with those evils is undo it.
All the planning, meetings, approvals, tickets, politics, and general BS associated with managing “releases” will actually slow you down or kill your business in today’s world.
Go to market team can do whatever “release” they want. But engineering team should not care. In this case, a “release” should be no more than a summary of what have been gone live in the past.
万维钢的这一课的内容，让我想到或许自闭症的人难以进入默认模式网络，很多表现都能和文中提到的类似。如果真是，那就很讽刺了，所谓自闭，恰恰是他们对“自”（me）无感，把自己跟世界一起“闭”于门外。而屋内热闹的人们，大部分时间活在自己的小屋里，只有不感到恐惧的片刻，偶尔开窗看看外面的世界，同时却忧心门外的他们，除了拥有整个世界，似乎只有孤独。
而现在一个最新的认识，说默认模式网络，是“自我”的来源 —— 你可以叫它 “Me Network”。
我理解，当你专注地做一件事的时候，会进入“心流”状态，它的特征恰恰是“忘我” —— 这也正好是默认模式网络活动降低的状态。
自闭症的人进入“心流”，那是分分钟的事。
科学家认为人在刚出生的时候并没有默认模式网络，是长大了慢慢才形成。
他们就是难以甚至无法形成默认模式网络。
科学家曾经猜想，既然致幻剂让人的感情都变得更强烈了，是不是说致幻剂能增强大脑的活动呢？结果发现不是。使用致幻剂后，大脑的供血量和供氧量都下降了。
很好奇他们的大脑供血量跟一般人是不是有区别？
但是使用了迷幻蘑菇之后，大脑的各个网络之间就增加了很多横向的、全局性的交流。现在的大脑“全球化”了 ——
视觉和听觉直接对话，你会感到颜色是有声音的。听觉和触觉直接对话，你会感到声音有质感，可以触摸。
他们的确有不同程度的通感能力，而且不限于五官之间，而是在同一感官，也能产生抽象和形象之间的融合。例如不少自闭算数天才，每个数字对于他们都是一种颜色和图案。对于Temple Grandin，物品在时间轴上可以随意切换。至于波子，过去的事件和日历的对标对于他稀松平常。
从这里脑科学角度来说，就是当你的默认模式网络开启、你有自我意识的时候，你的大脑会自动过滤外界信息。
比如走路，你只会注意路的方向、有没有障碍物、有没有行人，你会把鸟叫的声音、树叶的颜色都忽略掉。再比如读书，你会注意文字的意思，而不会一直观察墨水和纸张的细微结构。过滤增加了你的效率，但同时也给你带上了有色眼镜，你不能客观地去体验这个世界。
对这些跟目标动作无关的“多余”细节的注意，正是自闭者的一大特征。其实细节是客观存在的，之所以多余，是因为常人的默认模式网络开启之后，根据立场，不自觉过滤掉的。而自闭者没有这种“功利心”。
https://serverless.com/blog/strategies-implementing-user-authentication-serverless-applications/
Typically, you would store session data in either Redis or Memcached. But for Serverless projects, it makes sense to use hosted datastores instead—Amazon ElastiCache or DynamoDB, Google Cloud Datastore, etc.
AWS Lambda offers a convenient way to perform authentication outside of your core functions. With API Gateway’s Custom Authorizers, you can specify a separate Lambda function that is only going to take care of authenticating your users.
Still a lot of heavy-lifting. The whole point of going serverless is to focusing more on coding the business logic. 😦
Agility – What to do
1) find out where you are
2) take a small step towards your goal
3) adjust your understanding based on what you learned
4) repeat
Agility – How to do it
When faced with two of more alternatives that deliver roughly the same value, take the path that makes future change easier.
That applies to most of the design decisions.
http://www.carlopescio.com/2011/04/your-coding-conventions-are-hurting-you.html
Alan is very explicit about the idea of methods as goals, something you want to happen, unconcerned about how it is going to happen.
The fundamental reason behind TDD.
If we can’t find a good name, we obviously don’t know enough about either the problem domain or the solution domain.
I would suggest that you focus on class/interface names first. If you can’t find a proper name for the class, try naming functions. Look at those functions. What is keeping them together? You can apply them to… that’s the class name :-).
When Peter wrote that (1993), the idea of an Helper class was mostly unheard of. But as more people got into the OOP bandwagon, they started creating larger and larger, uncohesive classes. The proper OO thing to do, of course, is to find the right cooperating, cohesive concepts. The lazy, fake OO thing to do is to take a bunch of methods, move them outside the overblown class X, and group them in XHelper. While doing so, you often have to weaken encapsulation in some way, because XHelper needs a privileged access to X. Ouch.
Wow, I’ve never paid attention to that since helper class is so much “needed” for every project. Lol
Handler, again, is an obvious resurrection of procedural thinking. What is an handler if not a damn procedure? Why do something need to be “handled” in the first place? Oh, I know, you’re thinking of events, but even in that case, EventTarget, or even plain Target, is a much better abstraction than EventHandler.
Again, eye opening!
Still, at some point people thought it was fine to look at an interface (or at a class), see if there was some kind of “main method” or “main responsibility” (which is kinda obvious if you only have one) and name the class after that. Which is a very simple way to avoid thinking, but it’s hardly a good idea. It’s like calling a nail “Hammerable”, because you known, that’s what you do with a nail, you hammer it. It encourages procedural thinking, and leads to ineffective abstractions.
Unusual perhaps, but that’s because of the common drift toward the mechanics of things and away from concepts (because the mechanics are usually much easier to get for techies).
Sort of calling a concept IDollar instead of Currency.
A List is an IEnumerable (what??) A List is a Sequence (well, all right!)
Weiran's Recycle Bin 