Burin Asavesna burin

When to Use Each Version

claudette-mimir.md ⭐ NEW!!!

✅ Full integration with Mimir's memory bank
✅ Graph functions enable multi-hop reasoning

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

query
mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

	function* runTimer(getState) {

	while(yield take('START')) {
	while(true) {
	const {stop, tick} = yield race({
	stop : take('STOP'),
	tick : call(wait, ONE_SECOND);
	})
	if ( !stop ) {
	yield put(actions.tick());

	Disclaimer: The instructions are the collective efforts from a few places online.
	Nothing here is my original. But I want to put them together in one place to save people from spending the same time as I did.

	First off, bundle.
	==================

	1. cd to the project directory
	2. Start the react-native packager if not started
	3. Download the bundle to the asset folder:
	curl "http://localhost:8081/index.android.bundle?platform=android" -o "android/app/src/main/assets/index.android.bundle"

	@import WatchKit;

	@interface CachingInterfaceController : WKInterfaceController

	- (void)updateLabel:(WKInterfaceLabel )label withString:(NSString )string;
	- (void)updateLabel:(WKInterfaceLabel *)label asHidden:(BOOL)hidden;
	- (void)updateImage:(WKInterfaceImage )image withImageNamed:(NSString )imageName;
	- (void)updateImage:(WKInterfaceImage )image withBaseNameForAnimation:(NSString )baseName withRange:(NSRange)range duration:(NSTimeInterval)duration repeatCount:(NSInteger)repeatCount;
	- (NSString )currentImageNameForImage:(WKInterfaceImage )image;

	* {
	font-size: 12pt;
	font-family: monospace;
	font-weight: normal;
	font-style: normal;
	text-decoration: none;
	color: black;
	cursor: default;
	}

	public enum NotificationKey: String {
	case UserSignedIn = "UserSignedInNotification"
	case UserSignedOut = "UserSignedOutNotification"
	case SomeOtherEvent = "SomeOtherEventNotification"
	}

	extension NSNotificationCenter {

	func addObserver(observer: AnyObject, selector aSelector: Selector, key aKey: NotificationKey) {
	self.addObserver(observer, selector: aSelector, name: aKey.rawValue, object: nil)

	@interface CLKTextProvider (NNNCompoundTextProviding)

	+ (nonnull CLKTextProvider )nnn_textProviderByJoiningProvider:(nonnull CLKTextProvider )provider1 andProvider:(nonnull CLKTextProvider )provider2 withString:(nullable NSString )joinString;

	@end