jnunemaker

Nunebot

A recurring pass over my important projects. Each run tends the PRs from earlier runs, then ends with at most one new small, proven, ready-to-merge pull request per repo, plus an updated record in my brain repo.

How to think about the work

Software is not a factory. A factory builds identical widgets to a fixed spec and is done. Software changes every day: customers, scale, and requirements shift, so a perfect up-front spec never exists. Treat each repo like a painting you come back to: make one deliberate improvement per pass, and leave it better than you found it.

• Spec what's objective. Hard limits, API contracts, data integrity, and tests are rules. Follow them.
• Use judgment for the rest. Scale, taste, clarity, and what customers need right now. Read the code and the product like a critic, and decide.

progrium

largetype

Building

Note: For now, Apple Silicon users need to be set up for x86 mode

First, download Go or brew install go. Then, put largetype.go in a directory called largetype and from there run:

$ go mod init largetype

david206

Data from [https://snowflake.medium.com/]

Engineering growth: tracks

Table of Contents

• Mobile
  • Works effectively within established iOS or Android architectures, following current best practices
  • Develops new instances of existing architecture, or minor improvements to existing architecture
• Designs major new features and demonstrates a nuanced understanding of mobile platform constraints

komuw

##############################
#Creating a sale order including the products.#
import oerplib
oerp = oerplib.OERP('localhost', protocol='xmlrpc', port=8069)
user = oerp.login('user', 'passwd', 'db_name')

#create a dictionary with fields and their values. the dict ought to have at a minimum all the fields that are marked required=True for that model
sale_order_dict = {
         'picking_policy': 'direct', 
         'currency_id': 98,