micimize

" https://github.com/jistr/vim-nerdtree-tabs

" display list of buffers like tabs
Plugin 'ap/vim-buftabline'

" claims to solve w/wq edge cases and I believe them
Plugin 'mhinz/vim-sayonara'

" automatically enter/exit paste on inhuman input speed
" added because paste disables abbreviations,

micimize

My Model of Language

My current model of natural language is that it could and should be modeled as a programming language, and that this modeling could prove fruitful, and possibly vital for producing AGI

Expression Rewriting Interpreter

If language is code, it is fundamentally a pure expression rewrite system, like Wolfram. This is the root of the "signs only point to signs" problem, concretion is only possible at runtime. Looseness can be afforded because of the robustness and extensibility of its interpreter.

All language concepts available present in their final form. The haskell type system has nothing on our type system. Expressions can be curried, transformed, inverted, dereferenced. None of this is surprising – programming languages constructs are mostly formalized derived from natural language (mostly english).

Evalation at Runtime

micimize

* "traveral" here is from Lazy Depth First Traversal
* "lazily take each" here is from Iterators

To lazily group the connected components given a collection of nodes:
    First, mark all nodes unseen.
    Then, with a traversal that can stop early when unmarkable
    lazily take each node from unseen,
    grouping the traversal of that node into a component

micimize

micimize

extension FetchMore on GraphQLClient {
  /// fetch more results and then merge them with [previousResult]
  /// according to [FetchMoreOptions.updateQuery]
  Future<QueryResult> fetchMore(
    FetchMoreOptions fetchMoreOptions, {
    @required QueryOptions options,
    @required QueryResult previousResult,

    /// rebroadcast other queries unless caching is disabled
    /// for this query via `options`

micimize

My #1 piece of advice here is that if you're an independent app developer using a personal apple id, put CI/CD off for a while and just release from local. Just because something can be automated doesn't mean it should

In hindsight, implementing CI before feeling the crunch to scale was not worth the time and was a premature optimization. Being [enrolled as an Organization][enroll] also allows for easier and more idiomatic setups.

• Read the [fastlane CI best practices][best_practices] and these tips before getting started, not just for troubleshooting

• You're in a very slow troubleshooting loop where you need to push-to-test.

micimize

Loose Lockbot Thoughts

Closed issue threads, even very old ones, have a great deal of utility to project communities. They are a common place for users to share workarounds, caveats, and link to related issues.

Instead of simply locking a thread, if we could:

• automatically unsubscribe maintainers (and comment "tag {maintainer} if and only if this is still an issue")
• comment and label the issue accordingly

micimize

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      debugShowCheckedModeBanner: false,

micimize

// version of auth link with overrideable header key
// https://github.com/zino-app/graphql-flutter/blob/master/packages/graphql/lib/src/link/auth/link_auth.dart
import 'dart:async';

import 'package:graphql/src/link/link.dart';
import 'package:graphql/src/link/operation.dart';
import 'package:graphql/src/link/fetch_result.dart';

typedef GetToken = FutureOr<String> Function();

micimize

description=$(gcloud sql instances describe $DB 2>&1)

if [ $? -ne 0 ]
then
    if [[ $description == *HTTPError* ]]
    then
      gcloud sql instances create $ \
             --database-version=POSTGRES_12 \
             --cpu=1 --memory=614MB \
             --region=us-central1