The Big Lie About Hard Work
Image vs Containers for Docker
Not many developers explain technologies clearly, either intentionally or incapably. the post here however is one exception:
from: http://blog.codesupport.info/docker-images-vs-containers/
IMAGE :- An image is an inert, immutable, file that’s essentially a snapshot of a container. Images are created with the build command, and they’ll produce a container when started with run. Images are stored in a Docker registry such as registry.hub.docker.com. Because they can become quite large, images are designed to be composed of layers of other images, allowing a miminal amount of data to be sent when transferring images over the network.
CONTAINER :- To use a programming metaphor, if an image is a class, then a container is an instance of a class—a runtime object. Containers are hopefully why you’re using Docker; they’re lightweight and portable encapsulations of an environment in which to run applications.
The RPC didn’t feel so long ago
It didn’t seems like a century old ago, when the stub and skeleton was widely used, and WSDL2Java & Java2WSDL was pretty convenient and “cool”:
-
A Java program executes a method on a stub (local object representing the remote service)
-
The stub executes routines in the JAX-RPC Runtime System (RS)
-
The RS converts the remote method invocation into a SOAP message
-
The RS transmits the message as an HTTP request
it’s now an Optional in Java EE7, but good to see it’s still there.
Chrome App with AnguarJS & JQuery
There are mainly 3 parts to build an chrome app:
Static Page
- popup.html, would be the popup view when you click on the icon of the app/plugin
here you define the view, and the binding to the controller/service functions
<div ng-controller="shortCutController" ng-model="option" class={...}
/>
<button id="configure" class="btn btn-info" ng-click="option = !option; initMap()">{{ option ? "Hide": "Show"}} Configure</button>
app.js
- which is the place to put your controller/services:
app.controller( 'shortCutController', ['$scope', '$rootScope', 'mapStore', function( $scope, $rootScope,mapStore ) {
}
I am using chrome storage, so did a sync on each update
$scope.update=function(key, value) {//update the storage
//mapStore.update(key, value);
$rootScope.mappers[key] =value;
chrome.storage.sync.set({"mapper":$rootScope.mappers}, function(){
console.log("check the updated mappers: "+$rootScope.mappers);
});
background.js
this is the place, for your plugin to listen to registered actions. for this case, it’s listening omnibox:
chrome.omnibox.onInputEntered.addListener(
function(text) {
vardata= {};
chrome.storage.sync.get("mapper",function(keys){
......
chrome.tabs.query({
.............
}}
Here is the link for the app: https://chrome.google.com/webstore/detail/short-cut-for-url-mapper/lafchflokhmpcoaondfeffplkdnoaelh
Android React native app
Have played around react native, and published an android app earlier.
some thoughts:
-
navigator
this would normally be the entry point, which define the landing page, and how routing to different pages works.
<Navigator
initialRoute={{ title: 'Tap Scene', id: 'default' }}
renderScene={this.navigatorRenderScene}
/>
Scene
2. For each scene, its a Component, where the life cycle of constructor, componentDidMount, componentUnmount, can be used to trigger specific actions. on each scene, you can use JSX to create the page/view, which could link to functions, like normal js binding:
onActionSelected
onIconClicked
handleClick() {
if(!this.state.favnumber)
LocalToastAndroid.show('Please set up your favorite number first', LocalToastAndroid.SHORT);
else
LocalToastAndroid.call(this.state.favnumber);
};
Additional actions
3. native react native modules wont cover all functions you request, to create custom module, you can register additional
ReactContextBaseJavaModule
then exposing the method to JS
@ReactMethod
public void call(String number){
.....
}
module.exports = NativeModules.CustomizedModule;
here is the app: https://play.google.com/store/apps/details?id=com.best2lwjj
AI for system support
Have tried to build an AI bot since almost 3 years back, finally did a prototype, in case anybody would like to do something similar:
Technologies:
Java, Scala, Python, Anaconda, Scikit Learn, EWS, BootStrap, AngularJS/JQuery
Components:
Data Set
- I have built a scala web crawler, to download all historical support issues.
- at the same time, have manually cleaned up/read through each of the thousand of support issues, put in corresponding resolutions corresponding to each
AI
- have leveraged on anaconda & scikit learn, to NLP, to tokenize each support issue (text), remove stop words, stemmed each, remove punctuations
- have leveraged on anaconda & scikit learn, bag each token of the text as feature vs class, to feed into linear regression classifier, tried SLDA, so far working at 72% accuracy
AI Exposer
- have exposed AI as a service
Issue Feeder
- have leveraged EWS to read in all issues, post to AI service
UI
- have built a web user interface, on top of HTML5 + JQuery + Bootstrap, to show the support emails + AI responded resolutions
- have a option on UI, to provide user feedback to AI, to keep its intelligence updated
Notifier
- leverage on Java Mail API, Chat API, to post alerts for critical issues
Datetime issue
The nasty datetime format issue seems like is universal. In c# world, depends on the locale, it would format to string and parse to datetime differently and could wrongly as well.
For example, for cultureinfo (“ja-JP”), datetime.tostring() could be yyyy/MM/d format which not recognized by a lot other systems or places.
While for same locale, it would parse 04Apr16 as 2004-04-16.
To solve and avoid the issues, invariantculture should be the cure. Always use invariantculture for parsing and for formating:
Datetime.parseExact(dateString, format, invariantculture).tostring(format, invariantculture).
