1598452620
The U.S. Military Is Turning to Science Fiction to Shape the Future of War
In 2030, a severe drought triggers a refugee crisis, which in turn sparks a war between two African nations. The UN steps in, deploying U.S. and French soldiers to keep the borders secure. An information warfare specialist is sent in when a disinformation campaign depicts U.S. forces destroying religious sites and infecting refugees with tainted vaccines and moves to help mitigate attacks from state actors looking to destabilize the region. Just as support for intervention in the conflict erodes in the United States, violence begins to rise, and the team is forced to work quickly to prevent the crisis from growing into a larger conflict.
It may sound like it could be the plot of a new Netflix series, but it’s actually one of the U.S. Army’s “science fiction prototypes,” a teaching tool designed to imagine what the near future of warfare might look like and to prompt military personnel to think creatively about conflicts they might end up fighting. This one takes the form of a 71-page graphic novel called Invisible Force: Information Warfare and the Future of Conflict, produced by the Army Cyber Institute at West Point and Arizona State University’s Threatcasting Lab.
As digital technologies and robotics have opened up the kinds of futures once imagined by pulp science fiction writers, a loose network of national security professionals, military officers, and training organizations are working to try to predict the future of war — by generating science fiction stories of their own.
These stories aim to address some of the biggest questions about the fast-changing nature of modern warfare: How will artificial intelligence change how decisions are made on the battlefield? What does the introduction of UAVs and autonomous robotic systems mean for the rules of engagement? These problems are difficult to test in the real world. So, in the past decade, various groups within or adjacent to the military have increasingly turned to science fiction, using anthologies, graphic novels, and books to visualize the battlefields we might someday find ourselves fighting in.
Nike and Boeing Are Paying Sci-Fi Writers to Predict Their Futures
Welcome to the Sci-Fi industrial complex
Science fiction has leaned into the future of warfare throughout its history, frequently depicting futuristic soldiers and the weapons they wield — and the conditions that beget conflict. Classics like H.G. Wells’ The War of the Worlds envision alien invaders attacking civilians with advanced ray guns and poison gas canisters. And the prospect of nuclear war in the 1950s prompted Robert Heinlein to write Starship Troopers, a novel that featured soldiers in power armor killing alien “bugs” for a militaristic regime that looks a lot like future fascism.
In turn, the military too has used science fiction off and on for more than 100 years. One very early example dates back to 1871, when British Army Colonel Sir George Tomkyns Chesney published a novella called The Battle of Dorking in Blackwood’s Magazine. Chesney was alarmed at Germany’s aptitude for mechanization and movement on the battlefield during the Franco-Prussian War and wrote his story as a warning against complacency. Others followed: Ernest Dunlop Swinton’s 1904 book, The Defence of Duffer’s Drift, is about a soldier named Lieutenant Backsight Forethought, who is ordered to defend a river crossing during the Boer War. He has a series of six dreams in which he fails in different ways but learns from his mistakes each time. Designed as an instructive read for junior officers learning about small-unit tactics, the story was originally published in the British United Service Magazine, and later in the Journal of the United States Infantry Association.
The Cold War proved to be fertile ground for strategists looking to write about the future of warfare. British General Sir John Hackett imagined how a Soviet invasion of West Germany might snowball into a global conflict in his 1979 novel, The Third World War: August 1985, while an insurance agent named Tom Clancy published his obsessively detailed and technically oriented novel about a rogue Soviet submarine, The Hunt for Red October, with the Naval Institute Press in 1984_. _Hawkish mainstream science fiction authors also contributed, setting up an institute called SIGMA — the self-described “science fiction think tank” — which has aimed to provide insights and technical expertise for the U.S. government since 1992.
#technology #future #science-fiction #military #books
What is GEEK
Buddha Community
1598452620
The U.S. Military Is Turning to Science Fiction to Shape the Future of War
In 2030, a severe drought triggers a refugee crisis, which in turn sparks a war between two African nations. The UN steps in, deploying U.S. and French soldiers to keep the borders secure. An information warfare specialist is sent in when a disinformation campaign depicts U.S. forces destroying religious sites and infecting refugees with tainted vaccines and moves to help mitigate attacks from state actors looking to destabilize the region. Just as support for intervention in the conflict erodes in the United States, violence begins to rise, and the team is forced to work quickly to prevent the crisis from growing into a larger conflict.
It may sound like it could be the plot of a new Netflix series, but it’s actually one of the U.S. Army’s “science fiction prototypes,” a teaching tool designed to imagine what the near future of warfare might look like and to prompt military personnel to think creatively about conflicts they might end up fighting. This one takes the form of a 71-page graphic novel called Invisible Force: Information Warfare and the Future of Conflict, produced by the Army Cyber Institute at West Point and Arizona State University’s Threatcasting Lab.
As digital technologies and robotics have opened up the kinds of futures once imagined by pulp science fiction writers, a loose network of national security professionals, military officers, and training organizations are working to try to predict the future of war — by generating science fiction stories of their own.
These stories aim to address some of the biggest questions about the fast-changing nature of modern warfare: How will artificial intelligence change how decisions are made on the battlefield? What does the introduction of UAVs and autonomous robotic systems mean for the rules of engagement? These problems are difficult to test in the real world. So, in the past decade, various groups within or adjacent to the military have increasingly turned to science fiction, using anthologies, graphic novels, and books to visualize the battlefields we might someday find ourselves fighting in.
Nike and Boeing Are Paying Sci-Fi Writers to Predict Their Futures
Welcome to the Sci-Fi industrial complex
Science fiction has leaned into the future of warfare throughout its history, frequently depicting futuristic soldiers and the weapons they wield — and the conditions that beget conflict. Classics like H.G. Wells’ The War of the Worlds envision alien invaders attacking civilians with advanced ray guns and poison gas canisters. And the prospect of nuclear war in the 1950s prompted Robert Heinlein to write Starship Troopers, a novel that featured soldiers in power armor killing alien “bugs” for a militaristic regime that looks a lot like future fascism.
In turn, the military too has used science fiction off and on for more than 100 years. One very early example dates back to 1871, when British Army Colonel Sir George Tomkyns Chesney published a novella called The Battle of Dorking in Blackwood’s Magazine. Chesney was alarmed at Germany’s aptitude for mechanization and movement on the battlefield during the Franco-Prussian War and wrote his story as a warning against complacency. Others followed: Ernest Dunlop Swinton’s 1904 book, The Defence of Duffer’s Drift, is about a soldier named Lieutenant Backsight Forethought, who is ordered to defend a river crossing during the Boer War. He has a series of six dreams in which he fails in different ways but learns from his mistakes each time. Designed as an instructive read for junior officers learning about small-unit tactics, the story was originally published in the British United Service Magazine, and later in the Journal of the United States Infantry Association.
The Cold War proved to be fertile ground for strategists looking to write about the future of warfare. British General Sir John Hackett imagined how a Soviet invasion of West Germany might snowball into a global conflict in his 1979 novel, The Third World War: August 1985, while an insurance agent named Tom Clancy published his obsessively detailed and technically oriented novel about a rogue Soviet submarine, The Hunt for Red October, with the Naval Institute Press in 1984_. _Hawkish mainstream science fiction authors also contributed, setting up an institute called SIGMA — the self-described “science fiction think tank” — which has aimed to provide insights and technical expertise for the U.S. government since 1992.
#technology #future #science-fiction #military #books
1656151740
Test_cov_console: Flutter Console Coverage Test
Flutter Console Coverage Test
This small dart tools is used to generate Flutter Coverage Test report to console
How to install
Add a line like this to your package's pubspec.yaml (and run an implicit flutter pub get):
dev_dependencies:
test_cov_console: ^0.2.2
How to run
run the following command to make sure all flutter library is up-to-date
flutter pub get
Running "flutter pub get" in coverage... 0.5s
run the following command to generate lcov.info on coverage directory
flutter test --coverage
00:02 +1: All tests passed!
run the tool to generate report from lcov.info
flutter pub run test_cov_console
---------------------------------------------|---------|---------|---------|-------------------|
File |% Branch | % Funcs | % Lines | Uncovered Line #s |
---------------------------------------------|---------|---------|---------|-------------------|
lib/src/ | | | | |
print_cov.dart | 100.00 | 100.00 | 88.37 |...,149,205,206,207|
print_cov_constants.dart | 0.00 | 0.00 | 0.00 | no unit testing|
lib/ | | | | |
test_cov_console.dart | 0.00 | 0.00 | 0.00 | no unit testing|
---------------------------------------------|---------|---------|---------|-------------------|
All files with unit testing | 100.00 | 100.00 | 88.37 | |
---------------------------------------------|---------|---------|---------|-------------------|
Optional parameter
If not given a FILE, "coverage/lcov.info" will be used.
-f, --file=<FILE> The target lcov.info file to be reported
-e, --exclude=<STRING1,STRING2,...> A list of contains string for files without unit testing
to be excluded from report
-l, --line It will print Lines & Uncovered Lines only
Branch & Functions coverage percentage will not be printed
-i, --ignore It will not print any file without unit testing
-m, --multi Report from multiple lcov.info files
-c, --csv Output to CSV file
-o, --output=<CSV-FILE> Full path of output CSV file
If not given, "coverage/test_cov_console.csv" will be used
-t, --total Print only the total coverage
Note: it will ignore all other option (if any), except -m
-p, --pass=<MINIMUM> Print only the whether total coverage is passed MINIMUM value or not
If the value >= MINIMUM, it will print PASSED, otherwise FAILED
Note: it will ignore all other option (if any), except -m
-h, --help Show this help
example run the tool with parameters
flutter pub run test_cov_console --file=coverage/lcov.info --exclude=_constants,_mock
---------------------------------------------|---------|---------|---------|-------------------|
File |% Branch | % Funcs | % Lines | Uncovered Line #s |
---------------------------------------------|---------|---------|---------|-------------------|
lib/src/ | | | | |
print_cov.dart | 100.00 | 100.00 | 88.37 |...,149,205,206,207|
lib/ | | | | |
test_cov_console.dart | 0.00 | 0.00 | 0.00 | no unit testing|
---------------------------------------------|---------|---------|---------|-------------------|
All files with unit testing | 100.00 | 100.00 | 88.37 | |
---------------------------------------------|---------|---------|---------|-------------------|
report for multiple lcov.info files (-m, --multi)
It support to run for multiple lcov.info files with the followings directory structures:
1. No root module
<root>/<module_a>
<root>/<module_a>/coverage/lcov.info
<root>/<module_a>/lib/src
<root>/<module_b>
<root>/<module_b>/coverage/lcov.info
<root>/<module_b>/lib/src
...
2. With root module
<root>/coverage/lcov.info
<root>/lib/src
<root>/<module_a>
<root>/<module_a>/coverage/lcov.info
<root>/<module_a>/lib/src
<root>/<module_b>
<root>/<module_b>/coverage/lcov.info
<root>/<module_b>/lib/src
...
You must run test_cov_console on <root> dir, and the report would be grouped by module, here is
the sample output for directory structure 'with root module':
flutter pub run test_cov_console --file=coverage/lcov.info --exclude=_constants,_mock --multi
---------------------------------------------|---------|---------|---------|-------------------|
File |% Branch | % Funcs | % Lines | Uncovered Line #s |
---------------------------------------------|---------|---------|---------|-------------------|
lib/src/ | | | | |
print_cov.dart | 100.00 | 100.00 | 88.37 |...,149,205,206,207|
lib/ | | | | |
test_cov_console.dart | 0.00 | 0.00 | 0.00 | no unit testing|
---------------------------------------------|---------|---------|---------|-------------------|
All files with unit testing | 100.00 | 100.00 | 88.37 | |
---------------------------------------------|---------|---------|---------|-------------------|
---------------------------------------------|---------|---------|---------|-------------------|
File - module_a - |% Branch | % Funcs | % Lines | Uncovered Line #s |
---------------------------------------------|---------|---------|---------|-------------------|
lib/src/ | | | | |
print_cov.dart | 100.00 | 100.00 | 88.37 |...,149,205,206,207|
lib/ | | | | |
test_cov_console.dart | 0.00 | 0.00 | 0.00 | no unit testing|
---------------------------------------------|---------|---------|---------|-------------------|
All files with unit testing | 100.00 | 100.00 | 88.37 | |
---------------------------------------------|---------|---------|---------|-------------------|
---------------------------------------------|---------|---------|---------|-------------------|
File - module_b - |% Branch | % Funcs | % Lines | Uncovered Line #s |
---------------------------------------------|---------|---------|---------|-------------------|
lib/src/ | | | | |
print_cov.dart | 100.00 | 100.00 | 88.37 |...,149,205,206,207|
lib/ | | | | |
test_cov_console.dart | 0.00 | 0.00 | 0.00 | no unit testing|
---------------------------------------------|---------|---------|---------|-------------------|
All files with unit testing | 100.00 | 100.00 | 88.37 | |
---------------------------------------------|---------|---------|---------|-------------------|
Output to CSV file (-c, --csv, -o, --output)
flutter pub run test_cov_console -c --output=coverage/test_coverage.csv
#### sample CSV output file:
File,% Branch,% Funcs,% Lines,Uncovered Line #s
lib/,,,,
test_cov_console.dart,0.00,0.00,0.00,no unit testing
lib/src/,,,,
parser.dart,100.00,100.00,97.22,"97"
parser_constants.dart,100.00,100.00,100.00,""
print_cov.dart,100.00,100.00,82.91,"29,49,51,52,171,174,177,180,183,184,185,186,187,188,279,324,325,387,388,389,390,391,392,393,394,395,398"
print_cov_constants.dart,0.00,0.00,0.00,no unit testing
All files with unit testing,100.00,100.00,86.07,""Installing
Use this package as an executable
Install it
You can install the package from the command line:
dart pub global activate test_cov_consoleUse it
The package has the following executables:
$ test_cov_console
Use this package as a library
Depend on it
Run this command:
With Dart:
$ dart pub add test_cov_consoleWith Flutter:
$ flutter pub add test_cov_consoleThis will add a line like this to your package's pubspec.yaml (and run an implicit dart pub get):
dependencies:
test_cov_console: ^0.2.2Alternatively, your editor might support dart pub get or flutter pub get. Check the docs for your editor to learn more.
Import it
Now in your Dart code, you can use:
import 'package:test_cov_console/test_cov_console.dart';example/lib/main.dart
import 'package:flutter/material.dart';
void main() {
runApp(MyApp());
}
class MyApp extends StatelessWidget {
// This widget is the root of your application.
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
// This is the theme of your application.
//
// Try running your application with "flutter run". You'll see the
// application has a blue toolbar. Then, without quitting the app, try
// changing the primarySwatch below to Colors.green and then invoke
// "hot reload" (press "r" in the console where you ran "flutter run",
// or simply save your changes to "hot reload" in a Flutter IDE).
// Notice that the counter didn't reset back to zero; the application
// is not restarted.
primarySwatch: Colors.blue,
// This makes the visual density adapt to the platform that you run
// the app on. For desktop platforms, the controls will be smaller and
// closer together (more dense) than on mobile platforms.
visualDensity: VisualDensity.adaptivePlatformDensity,
),
home: MyHomePage(title: 'Flutter Demo Home Page'),
);
}
}
class MyHomePage extends StatefulWidget {
MyHomePage({Key? key, required this.title}) : super(key: key);
// This widget is the home page of your application. It is stateful, meaning
// that it has a State object (defined below) that contains fields that affect
// how it looks.
// This class is the configuration for the state. It holds the values (in this
// case the title) provided by the parent (in this case the App widget) and
// used by the build method of the State. Fields in a Widget subclass are
// always marked "final".
final String title;
@override
_MyHomePageState createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
int _counter = 0;
void _incrementCounter() {
setState(() {
// This call to setState tells the Flutter framework that something has
// changed in this State, which causes it to rerun the build method below
// so that the display can reflect the updated values. If we changed
// _counter without calling setState(), then the build method would not be
// called again, and so nothing would appear to happen.
_counter++;
});
}
@override
Widget build(BuildContext context) {
// This method is rerun every time setState is called, for instance as done
// by the _incrementCounter method above.
//
// The Flutter framework has been optimized to make rerunning build methods
// fast, so that you can just rebuild anything that needs updating rather
// than having to individually change instances of widgets.
return Scaffold(
appBar: AppBar(
// Here we take the value from the MyHomePage object that was created by
// the App.build method, and use it to set our appbar title.
title: Text(widget.title),
),
body: Center(
// Center is a layout widget. It takes a single child and positions it
// in the middle of the parent.
child: Column(
// Column is also a layout widget. It takes a list of children and
// arranges them vertically. By default, it sizes itself to fit its
// children horizontally, and tries to be as tall as its parent.
//
// Invoke "debug painting" (press "p" in the console, choose the
// "Toggle Debug Paint" action from the Flutter Inspector in Android
// Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
// to see the wireframe for each widget.
//
// Column has various properties to control how it sizes itself and
// how it positions its children. Here we use mainAxisAlignment to
// center the children vertically; the main axis here is the vertical
// axis because Columns are vertical (the cross axis would be
// horizontal).
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
Text(
'You have pushed the button this many times:',
),
Text(
'$_counter',
style: Theme.of(context).textTheme.headline4,
),
],
),
),
floatingActionButton: FloatingActionButton(
onPressed: _incrementCounter,
tooltip: 'Increment',
child: Icon(Icons.add),
), // This trailing comma makes auto-formatting nicer for build methods.
);
}
}Author: DigitalKatalis
Source Code: https://github.com/DigitalKatalis/test_cov_console
License: BSD-3-Clause license
1598445300
The Man Whose Science Fiction Keeps Turning Into Our Shitty Cyberpunk Reality
Why I Made This Future_ is a recurring feature that invites speculative fiction authors, futurists, screenwriters, and so on to discuss how and why they built their fictional future worlds._
T
here is nothing boring about Tim Maughan’s works of speculative fiction, which concern, for example, the total destruction of the internet as we know it, the insidious possibilities of monetized augmented realities, and the full collapse of global supply networks. He writes such dramatic devastations, he says, to better examine the digital injustices that are perpetrated on ordinary people every day, and which can look rather boring on paper: data profiling and automated trade networks and surveillance capitalism and other drab inflections of our shitty cyberpunk present.
Maughan’s three books, the short story collection Paintwork,the novel Infinite Detail,and the newly released collection, Ghost Hardware, all take place in the same near-future world — the TMCU, as I like to call it. Therein, hyper-accelerated digital capitalism has thrust us all into a world that is perpetually and wholly online, and accessed via spex, augmented reality glasses that are as common as cellphones. Then, the internet is destroyed. It’s 15 minutes into the future, with the rug pulled out from under it. Maughan uses the conceit to investigate the consequences of having so much of our lives hosted, controlled, and in thrall to for-profit digital platforms and systems.
The Guardian called _Infinite Detail _thebest science fiction book of 2019 for a reason — it gets under the skin of the future to expose the ugly guts of the present. Maughan is, above all, a critic — he writes to expose the disturbing trajectories of the technologies, prejudices, and corporate impulses today. I’ve worked with Tim for years, editing his fiction, barging into his audiobook recordings, and lamenting the future on various corporate social media platforms. So, as prediction after prediction of his has glitched into being this year, it seemed a fine time to talk about surveillance, communication breakdown, and resistance to all of the above.
This may be the second installment of Why I Made This Future, but it could as well be called Why I Warned Against This Present.
The interview has been edited for length, clarity, and obscenity reduction.
**Brian Merchant: **So, Tim Maughan—
Tim Maughan: That’s me.
Brian Merchant: Wonderful. Let’s start with the big one: Why did you feel compelled to create the future of Infinite Detail and Ghost Hardware — and what are, in your mind, its key cornerstones?
**Tim Maughan: **For me, I’m creating a fictionalized version of the world that we live in. The three books I’ve published so far, ironically, in a very science fictional kind of way, are all set in the same world. In Paintwork, I was wanting to talk about technology and the privatization of public space — so augmented reality became this really good tool for doing that. So that spills on into another story I wrote that’s set in the same setting, and augmented reality is a key theme in Ghost Hardware.
**Brian Merchant: **I appreciate your critique of pervasive digital consumerism through the spex. In both _Infinite Detail _and Ghost Hardware,spex are basically the new iPhones — ubiquitous AR glasses that have their own operating system — everyone’s got one, before the world collapses.
**Tim Maughan: **They were very fictionalized but very… I would call it generic. I’m certainly not the first person to write about these technologies. They’re AR glasses that you put on that overlay a digital network over the reality you exist in, which is not an alien concept to most people. For me, it’s a really exciting literary device because a lot of the stuff I’m interested in talking about — network culture, digital systems, social media, even supply chains — these are not things that are easy to write about in literature. They’re incredibly boring to write about. So generating a very visual metaphor for dealing with them was what I was looking for in using AR.
**Brian Merchant: **And spex are a useful mechanism to interrogate surveillance practices, digital commerce, and so on. There’s a memorable scene that takes place after the city updates its policy so that you need spex to get credits for recycling cans. Can you talk a little bit about that, and then what all this mass digitalization and commoditization ultimately leads to?
**Tim Maughan: **Anybody who lives in the city has seen canners. They go through recycling, both the public and the residential recycling, and take items that need recycling, go and recycle them and get micropayments for each one. You glance at them and you think they’re homeless, which, as a matter of fact, the majority of people doing this work are not homeless, it turns out. In New York, many are cab drivers struggling to compete with Uber.
And the idea in the book is that this new technology that’s being brought in where RFID tags on every bottle and some facial recognition and machine learning is going on in stores. The system, the network, which is in New York in the book, knows when a can has been bought, who it’s been bought by, and who puts it in a recycling bin. And then it gives that payment directly to that person, the idea being it streamlines recycling and it gives people more of an incentive to recycle.
It’s a cool idea, but with these really horrible implications. I actually originally got the idea, and you’ll probably remember this — it was in the Bay Area, it was in San Francisco, maybe like 2013, 2014. There was a story about a bunch of guys, Latino guys in the neighborhood, who every Sunday would get together and play five-five soccer on these five-by-five soccer field pitches in their neighborhood. And they’d do that, it was a tradition that had been going on for decades.
One Sunday they turned up there, and the field was completely overrun by white guys wearing Dropbox T-shirts. And they were like, “Well, this is our field.” And the guy turned to them and said, “No, but we booked it.” And he said, “Well, what do you mean? What do you mean you booked it?” And he pointed at the sign, a flyer that had been stuck up at some point in the previous week saying, “In the future if you want to use these playing fields you have to book them. You can do it by downloading this app to your smartphone.” And the guy that was talking to him goes, “I haven’t got a smartphone. This is my culture. This is what we do.” And the guys go well, I’m sorry, but that’s how it works now. You need a smartphone.”
#future #books #why-i-made-this-future #cyberpunk #science-fiction #data science
1618449987
How To Build A Data Science Career In 2021
For this week’s data science career interview, we got in touch with Dr Suman Sanyal, Associate Professor of Computer Science and Engineering at NIIT University. In this interview, Dr Sanyal shares his insights on how universities can contribute to this highly promising sector and what aspirants can do to build a successful data science career.
With industry-linkage, technology and research-driven seamless education, NIIT University has been recognised for addressing the growing demand for data science experts worldwide with its industry-ready courses. The university has recently introduced B.Tech in Data Science course, which aims to deploy data sets models to solve real-world problems. The programme provides industry-academic synergy for the students to establish careers in data science, artificial intelligence and machine learning.
“Students with skills that are aligned to new-age technology will be of huge value. The industry today wants young, ambitious students who have the know-how on how to get things done,” Sanyal said.
#careers # #data science aspirant #data science career #data science career intervie #data science education #data science education marke #data science jobs #niit university data science
1624601340
From Science to Data Science
- Introduction and Hypothesis
I loved to work as a scientist. There is a deep feeling of completion and happiness when you manage to answer why. Finding out why such animal would go there, why would they do this at that time of the year, why is that place so diverse… This applies to any kind of field. This is the reason why I want to advocate that if you are a scientist, you might want to have a look at what is called Data Science in the technological field. Be aware, I will not dwell in the details of titles such as Data engineer, data analyst, data scientist, AI researcher. Here, when I refer to Data Science, I mean the science of finding insights from data collected about a subject.
So, back to our **_why. _**In science, in order to answer your why, you will introduce the whole context surrounding it and then formulate an hypothesis. “The timing of the diapause in copepods is regulated through their respiration, ammonia excretion and water column temperature”. Behaviour of subject is the result of internal and external processes.
In marketing, you would have to formulate similar hypothesis in order to start your investigation: “3-days old users un-suscribes due to the lack of direct path towards the check-out”. Behaviour of subject is the result of internal (frustration) and external (not optimized UE/UI) processes.
Although I would have wanted to put that part at the end, as for any scientific paper, it goes without saying that your introduction would present the current ideas, results, and hypotheses of your field of research. So, as a researcher, you need to accumulate knowledge about your subject, and you go looking for scientific articles. The same is true for techs as well. There are plenty of scientific and non-scientific resources out-there that will allow you to better understand, interpret and improve your product. Take this article, for instance, Medium is a wonderful base of knowledge on so many topics! But you could also find passionating articles on PloS One on Users Experience or Marketing Design and etc.
2. Material and Methods
As a Marine biologist and later an Oceanographer, I took great pleasure to go at the field and collect data (platyhelminths, fish counts, zooplankton , etc…). Then we needed to translate the living “data” into numeric data. In the technological industry, it is the same idea. Instead of nets, quadrats, and terrain coverage, you will setup tracking event, collect postbacks from your partners and pull third-parties data. The idea is the same, “how do I get the information that will help me answer my why”. So a field sampling mission and a data collection planning have a lot in common.
#ai #data-science #science #tech #data science #from science