---
id: 2026-02-28T12:02:03-05:00
aliases: []
title: "2026-02-28 12:02:03"
tags:
  - authorship/original
  - destiny/permanent
  - status/draft
  - type/timestamped
dg-publish: true
date-created: 2026-02-28T12:02:03-05:00
daily: "[[2026-02-28]]"
weekly: "[[2026-W09]]"
monthly: "[[2026-02]]"
quarterly: "[[2026-Q1]]"
yearly: "[[2026]]"
---
# 2026-02-28 12:02:03

It is difficult to express how _little_ Accubid does for the user.
Except for LiveCount and SupplierLink
(which are separate programs anyhow)
100% of its functionality could be replicated with database queries.

This trait is not unique to Accubid,[^1]
what is unique (and uniquely frustrating)
is how little the workflow would change if it was. 

[^1]: Programs like this are called CRUD (Create Read Update Delete) apps.

If you were to replace the Takeoff tab with a command prompt,
this is what it would look like to take off (2) receptacles:

```sql
INSERT INTO Takeoff (drawing,area,phase,system,bid_item,labor_factor,assembly,length,count)
VALUES ('E1.01','Level 01','BOH','Electrical','Building','Standard','DUPLEX REC',0,2);
```

Given the option, I'd already pick the console;
but I'm aware I'm an outlier.
Consider though, that ...
Not to mention that such a schema would allow mouse-less takeoff,
a considerable boon for [[ergonomics]].

***

I get strange looks when I suggest that construction estimating could be fun.
Truly I believe it _would_ be fun,
except for the total absence of [skeuomorphism](https://en.wikipedia.org/wiki/Skeuomorph),
interfaces designed to resemble their physical counterparts.

> ![[level-selector.jpg|400]]
> Mock-up of a level selection interface,
> perhaps for quickly creating typicals.

%%

```
   |     Roof     |
   |   Level 15   |
   ⭍ Levels 04-14 ⭍
   |   Level 03   |
   |   Level 02   |
___|   Level 01   |___
   |   Level G1   |
```

%%