hasokeric

#!/bin/bash

# We don't need return codes for "$(command)", only stdout is needed.
# Allow `[[ -n "$(command)" ]]`, `func "$(command)"`, pipes, etc.
# shellcheck disable=SC2312

set -u

abort() {
  printf "%s\n" "$@" >&2

hasokeric

//var x = defaultImpl.CreateEmpty(result);
//this.resultHolder.Attach(QueryResultDataSetUbaqTableset.FromDataSet(result));

ResultsUbaqRow row = (ResultsUbaqRow)result.Results.NewRow();

row.SysRowID = Guid.NewGuid();
row.Calculated_RowStatus = "Meow";
row.RowIdent = row.SysRowID.ToString();
row.RowMod = "A";
var z = ((ResultsUbaqTable)result.Results);

hasokeric

swa deploy .\build\ --env production --app-name swa

hasokeric

var resourceGroupRows = Db.ResourceGroup.Where(x => x.Company == Session.CompanyID
        && x.Inactive == false
        && 
    ).ToList();

var resourceCalRows = Db.ResourceCal.Where(x => x.Company == Session.CompanyID
        && x.SpecialDay >= DateTime.Today
    ).Join(Db.ResourceGroup,
            rc => new { rc.Company, rc.ResourceGrpID, Inactive = false },
            rg => new { rg.Company, rg.ResourceGrpID, rg.Inactive },

hasokeric

// I'm tired of extensions that automatically:
// - show welcome pages / walkthroughs
// - show release notes
// - send telemetry
// - recommend things
//
// This disables all of that stuff.
// If you have more config, leave a comment so I can add it!!

{

hasokeric

As a tech lead, you so frequently get request from above or from other teams to drop what you are doing and work on this thing they need, now.

During my 4 years at Uber after asking these questions, 9 out of 10 times it turned out it wasn't really urgent:

1. "What is the impact of this work you're asking for?" If the impact is unclear: sorry, but we can't do the work. Why would we?

Just this question made the requester realize half the time they just think it's urgent, but don't know what the work will actually result in.

2. "Do you have a spec that is agreed with stakeholders?" A writeup answering the "why" and the "what" that is signed off by relevant business folks.

hasokeric

Microsoft does this a lot, where they assume that rules that apply to their own organisations apply to all organisations in precisely the same way. If a Microsoft IC leaves, they should lose access to all Git repos, including forks.

If Joe Random open-source contributor is removed from an open source repo's access list, their fork shouldn't be wiped.

But Microsoft has One Rule To Rule Them All, so they won't make exceptions for unimportant people like their customers.

I see this a lot. A good example is Azure Active Directory, which is basically "Microsoft 365 Authentication" that they rebranded and sold to developers for their own use, i.e.: Azure AD Enterprise Apps, App Registrations, and B2C.

There are many aspects of the AAD design that make zero sense until you pause for a second and realise that it is not designed for you. It's designed for Microsoft 365!

hasokeric

import { Component, ViewEncapsulation } from '@angular/core';
import {
  ApiModule,
  CustomMethodsService,
  ChangeJobAsmblPartNumInput,
  ErpTablesetsJobAsmblRow,
  ChangeEquipIDInput,
  ErpTablesetsJobEntryTableset,
  ErpTablesetsJobHeadRow,
} from 'app/modules/openapi';

hasokeric

Nx

https://nx.dev/

Nx is a suite of powerful, extensible dev tools to help you architect, test, and build at any scale — integrating seamlessly with modern technologies and libraries while providing a robust CLI, caching, dependency management, and more.

It has first-class support for many frontend and backend technologies, so its documentation comes in multiple flavours.

Principles

hasokeric

Epicor ERP Classic and Epicor ERP Kinetic are two different user interfaces for the same ERP system. Both have their own unique features and capabilities, and the choice between them will depend on the specific needs of your organization.

Pros of Epicor ERP Classic:

Familiarity: Epicor ERP Classic is the traditional user interface for the Epicor ERP system, and many users are already familiar with its layout and functionality. Customization: Classic UI can be customized to a greater extent than Kinetic UI. Third-party Add-ons: Many third-party add-ons and integrations have been developed for the Classic UI and are readily available. Cons of Epicor ERP Classic:

Limited scalability: The Classic UI may not be able to handle the requirements of larger organizations or those with more complex needs.