omeid

We are not going anywhere.

This might sound obvious, but it is worth putting it down, Software Development going forward will be largely done by AIs, you might find the quality subpar, but in terms of cost ratio, it is commercially good enough. Business will accept 99.99 at fraction of cost of 99.999. It is all about general consumer expectations, which will shift.

But most of all, not just that we are not going back, we are also not going anywhere. Software Engineering as science will be largely dedicated to AI development and outside of this discipline, it will slow down to a grinding halt.

No one is going to write new UI libraries if SOTA models know React best, no one is going to bother with new languages if SOTA models know Python, Go, JavaScript, and so on the best.

Yes, it will be easier for people to build new libraries and languages, but they won't gain traction. This might be different for large corporations who can afford to train and finetune models on their new fangled technology, but that

omeid

Death By A Thousand Efficiencies: Why You Too Should Be Afraid of Automation

When the question of “automation caused job losses” comes up, most people think of industry jobs where production-line or humanoid robots take over jobs whole or at most talk about virtual assistants or other entry level knowledge-worker positions getting replaced by Artificial Intelligence or how Neural Networks can compose news articles from a set of facts; the common theme here is bots taking over jobs whole; while ‘bots taking over jobs at the production-line is old news and vending machines that replace pizza restaurants from the cashier to chef is no longer something to speculate, I think a much more deadly and silent job killer is often overlooked: tools that makes workers more efficient.

As a general rule, efficiencies that reduces work-hours by any given percentage, it also reduces the overall number of position by the same percentage.

omeid

Folder Structure

Motivations

• Clear feature ownership
• Module usage predictibility (refactoring, maintainence, you know what's shared, what's not, prevents accidental regressions, avoids huge directories of not-actually-reusable modules, etc)

omeid

package api

import (
	"net/http"

	"github.com/ORG/PROJECT/user"
)

func accessControl(level user.AccessLevel) func(handler) handler {
	return func(handler handler) handler {

omeid

package main

import (
	"log"
	"net/http"
	"time"
)

type Handler func(rw http.ResponseWriter, r *http.Request, next http.HandlerFunc)

omeid

Submitted By: Andrew Bradford <andrew@bradfordembedded.com>
Date: 2013-10-14
Initial Package Version: 4.7.3
Origin: Gregor Richards' musl-cross
Upstream Status: None
Description: Patches to gcc to build for musl-libc.

# HG changeset patch
# Parent f50bb54f331f73405131a30b4f353cfda1c70304
Use the generic implementation of libstdc++ primitives when we're on musl, not the glibc one.

omeid

" Vim indent file
" Language:	    CSS
" Maintainer:	    Nikolai Weibull <now@bitwi.se>
" Latest Revision:  2010-12-22

if exists("b:did_indent")
  finish
endif
let b:did_indent = 1

omeid

package main

import (
	"fmt"
	"log"
	"net/http"

	"github.com/gorilla/mux"
)

omeid

package main

import (
	"crypto/md5"
	"crypto/rand"
	"encoding/hex"
	"encoding/json"
	"io"
	"net/http"
)

omeid

package main

import(
    "fmt"
     "github.com/go-martini/martini"
)

func main() {
	m := m := martini.Classic();
	m.NotFound(func(w http.ResponseWriter, r *http.Request) {