Description | Details |
---|---|
Problem | Happened with dbd template created by Michael; I could not update. Also after we upgraded - since Michael exported and imported all into Prod, he became the "owner" of all dashboards. |
Workaround | IAI Workaround: BPM (see Custom Kinetic Application Base layer not available to another developer). Another option: Add a security group. See Anybody with dashboard developer. |
using System; | |
using System.Linq; | |
public class Program | |
{ | |
public static void Main() | |
{ | |
Func<string, int> GetCheckDigit = _routingNumber => | |
(10 - _routingNumber.Where(char.IsDigit) | |
.Select((digit, index) => (digit - '0') * new[] { 3, 7, 1 }[index % 3]) |
This document serves as a guideline for developing and using good part numbering techniques within a manufacturing company. It addresses accidental and overly complex part numbering schemes which may become unmanageable and highlights that a part number is generally NOT a description of the part.
A part number should not attempt to be descriptive as it could lead to complications over time, such as changes in manufacturing or purchasing processes. The focus is on using the part number as a primary index within an ERP system.
#!/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 |
// Count up the UnderIssuedMtls and UnderReportedOprs to show in the ShipDtl grid on Summary Tab | |
foreach (var row in ttShipDtl.Where(x => x.OurJobShipQty > 0).ToList()) | |
{ | |
// Get all the UnderIssuedMtl Count | |
int UnderIssuedMtlCount = (from jp in Db.JobPart | |
join jm in Db.JobMtl on new { jp.Company, jp.JobNum } equals new { jm.Company, jm.JobNum } | |
where jp.Company == row.Company && | |
jp.JobNum == row.JobNum && | |
jp.PartNum == row.PartNum && |
//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); |
swa deploy .\build\ --env production --app-name swa |
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 }, |
// 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!! | |
{ |
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:
- "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.
- "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.