Oleg Yaroshevych

Random stuff about software development

[yaroshevych]

Valid point about the Mac software ecosystem.

[jamescarlos]

NativeBase | The missing piece of React Native

http://bit.ly/1SSZ4bG

The missing piece of React Native

[yaroshevych]

The only way to do a GC

When is the best time to do a GC?

When nobody is looking.

Use camera to track eye movement, when subject looks away do a GC.

by https://talks.golang.org/2015/go-gc.pdf

[yaroshevych]

Your calendar is a mess

Before you continue reading this, open your calendar and look at it. If you work at a big tech company, there’s an espec…

A full day free of meetings. A Facebook thing. I'm going to join

[yaroshevych]

One Hour Meeting

You likely have to get management approval for a $500 expense ... but you can call a 1 hour meeting with 20 people and no one notices

Problem solved, money saved, once you understand this.

By Vala Afshar

[yaroshevych]

Enterprise tooling

From the Ember.js github thread:

— My only concern here is that you're only building this for node. — How would you run javascript code on ruby, php and asp?

It reminds me recent conversation on my Enterprise project:

— You may write your javascripts all day long, son. — OK, we'll need npm, bower and grunt. It runs on top of node.js, you know. — Use whatever tools you want. Until it runs on Java...

(img by dilbert)

[yaroshevych]

Save Environment Variables in Amazon EC2 User Data

I don’t think it’s new, but it’s new to me. When you launch an instance in Amazon EC2, you have the option of passing User Data to store any text value, or define a script that will be executed on first boot. This is useful for standalone instances, and extremely helpful for Auto Scaling groups, when there is a need to change settings without touching VM image.

There is an important limitation for scripts: they only run during the first boot cycle when an instance is launched. But what if you want to save a command(s) that will run on-demand, or read environment variables to start your app? Just to keep your family and business code and configuration completely separated.

You may use Amazon-specific CLI tools, that retrieve information about current VM. For example, to get instance ID, run ec2metadata --instance-id. ec2metadata retrieves User Data text as well. The text may be parsed with grep or awk, but working with shell variables is much easier. Here is a quick example of storing and reading environment variables:

Example User Data

APP_URL=example.com?id=123 S3_KEY="ABC XYZ" S3_SECRET=ABC

Example bash script

#!/bin/bash eval $(ec2metadata --user-data) echo APP_URL=$APP_URL # start your node app APP_URL=$APP_URL S3_KEY=$S3_KEY node /path/app.js

This is it. It sounds like a weird as-seen-on-TV thing, but you've completely separated your configuration and code. Done.

[nirelbaz-deactivated20210111]

Front end tools benchmark

[yaroshevych]

Using Passport to securely authenticate using your Google Apps Hosted Domain.

[yaroshevych]

your brain will automatically tag this person as someone who may have something to hide

This is something that I've noticed many times

[yaroshevych]

Shyam Sankar, Director at Palantir Technologies:

I’m always personally engaged in our recruiting efforts, often spending time engaging top candidates for all parts of the business.

Truth. So much truth.

[yaroshevych]

It's all about terrible design of Javascript, and how it just gets more and more messy with each new version. What's your "favourite" "feature" - Symbols or Property value shorthands?

[yaroshevych]

Good reminder to always use strict mode

[yaroshevych]

Good thing to add to your Weekly Review. Evernote search:

created:day-7

[yaroshevych]

Mobile Safari in iOS 8 is a new argument in Web vs Native holy war.

[yaroshevych]

The end of single-hand-operational smartphones

[yaroshevych]

Nothing to add...

When services/applications/mainframes/etc... want to integrate (so send messages to each other) you can end up with quite a mess. An ESB hides that mess inside of itself (or itselves) so that an organisation can pretend that there isn't a mess and that it has something manageable. It then wraps a whole load of features around this to make this box even more enticing to the senior people in an organisation who'll make the decision to buy such an expensive product. These people typically will want to introduce a large initiative which costs a lot of money to prove that they are 'doing something' and know how to spend large amounts of money. If this is an SOA initiative then vendors various will have told them that an ESB is required to make the vendors vision of what SOA is work (typically once the number of services which they might want passes a trivial number).

So an ESB is:

A vehicle for vendors to make lots of money; A vehicle for consultants to make lots of money; A way for senior executives (IT Directors & the like) to show they can spend lots of money; A box to hide a mess in; A total PITA for a technical team to work with.