ian0

Tracks historical changes on google sheets. A lot of small businesses use sheets as a DB, editing/adding/removing rows & cells in realtime (eg orders, customers, tickets etc). The tool records change, like how average order value or backlog size is trending.

"Best tool for x", "book recommendations" etc etc

Its such a shame the genuine good information is so hard to find and where you do its in some walled garden.

Enough of course until someone shows them better results and then they will switch search engines just as we switched from altavista to google all those years back.

The discussions are very good, surprised you can get the responses to stay on track like that.

Anyone know what the rational for this is? I understand the not-rushing aspect, but would have thought if your enjoying it and "in the zone" it would be good to see it through

But your right and in fact found a great one for science for my son just now!

PS Just noticed its missing a favicon btw at least for me

https://www.sheetmonitor.com/ - Time-based-analysis on aggregated google sheet data. You can point it at a google sheet and define what data you want to track. It then grabs aggregate data from the sheet at regular intervals so you can see how the sheet is changing over time. Its something thats not possible to do within the sheets themselves for a lot of circumstances. Nodejs, sheets api & a time series DB.

https://dafr.ink/ - Simple Goal orientated project tracking. Wanted to create a tool that was really really fast, sharable without anyone having to login, but with optional lazy authentication. Svelte & cloudflare functions.

Places that seem full are quiet and have a different character completely. You can hear echos of footsteps. Weather seems to be accentuated. Your going the opposite direction to everyone at the start and end of your shift. Its strange at a low level and everyone you meet is "in it" too.

We made the switch to cross functional teams at around the same stage as you. I think a lot of lessons are really org-dependant, but highlights from me:

- Team/Pod effectiveness varies hugely. When most team-members "get" what they are trying to do and actively participates, it works amazingly well. Where there is gaps in communicating things tanked. The early symptoms were usually the team adopting more complex org frameworks, more detailed specs, obsessing over QA processes, meeting schedules etc. It was initially tempting to view this as a problem with the org structure, definitely seemed like it at the time. But after a bit of time the root cause was obvious. The nice thing is it manageable as isolated as long as you don't overreact

- Relatedly, you need to put a lot of effort into making sure everyone knows what the goals are for a team and its very clear what a win/loose looks like. Also since most people will be taking on more responsibility, mentoring becomes very critical. So you need good mentors with time to dedicate to it. Its easy for a team to get stuck in limbo and for people to feel frustrated.

- Since more junior people are put in positions of responsibility, gotta watch out for overly theoretical approaches & lets use framework-of-the-month behaviour. Both on the product & engineering side. Another reason for goals & win/loose being clear and mentoring.

- It really helps for teams to broadcast updates & lessons learned to other teams periodically. People knowing who helped to build what was good for everyone.

- QA people turned out to be some of the best "glue" for teams

- People jumping around different teams was surprisingly practical. Some people like doing this. Obviously didn't force the people who don't like it.

- People currently struggling but just maybe under your radar will suddenly feel the heat if they are letting their team down. It can be traumatic for them. Its worth keeping an eye out and jumping in to assist.

- Black Cat, White Cat (1998), serbian comedy

- Brother (1997), russian revenge flick

- Kontroll (2003), hungarian sci-fi/fantasy

- The Return (2003), russian drama

- Dead Man (1997), US western/art

- Three colours Blue (1993), french drama

- Paris, je t'aime (2006), short film compilation

As a bonus if you like smoking with friends Darby o Gill and The little People (1959) is an (inadvertent?) slapstick-comedy/horror from disney.

Obviously pretty dystopian and my experience there were close to zero ethics. They used to try and bribe the smartest young kids by offering company cars if they quit school and trained as managers. The owner even tried removing the small change from the tills as most people don't complain if they are short a tiny amount so he could squeeze that little extra (not a viable strategy btw as a tiny minority will freak out publicly).

We would stay after hours, well into the night, with film nerds and random people with nowhere else to go. Our boss, the manager of the branch was a nuclear physicist turned asylum seeker - who had our backs, brought us take outs and was an all around gent.

This was during college for me. I had some great, interesting, jobs afterwards both in tech and other random things. But I think this will always be my favorite. Those I keep in touch with seem to agree.

With recurring billing you may see some users churn who "forgot" about the charge in the first place and were likely not using the product.

FWIW This past year ive been stung so much by SAAS price hikes its fundamentally changed my internal equation of "when to SAAS VS when to self-host/build". Messaging apps have been the worst offenders, adding new features that we don't use and using this as an excuse to up prices to ridiculous levels. Overall positive perhaps, now using more self-hosted OS software.

The goal is to allow teams to see, in the very simplest way:

- What goals everyone is working towards

- Whats been done (or not done) to get there

The experiment part was trying to make it so its easy to get started (no login required, share via url), and make it really quick (Lazy updates to server, cloudflare functions).

Im not a fan of client side JS apps / frameworks and have avoided them for years, but for this particular use case it was the only way to go. I ended up using svelte, some hickups along the way but overall positive.

Any feedback welcome!

www.linkedin.com###ember69 > div

www.linkedin.com##.pb3.pt2.learning-top-courses

www.linkedin.com##.clear-both.text-align-center.t-normal.t-12.global-footer-compact__content

www.linkedin.com###ember131 > div

www.linkedin.com###voyager-feed

www.linkedin.com##.msg-overlay-bubble-header

www.linkedin.com##.msg-overlay-list-bubble__content--scrollable.msg-overlay-list-bubble__content

www.linkedin.com###msg-overlay

www.linkedin.com###messaging-nav-item

Speed is one mentioned below, but also cadence in responses could be measured similar to looking at keystrokes. This could be by token/word or perhaps answer-cadence, for example asking a challenge-response mix of complex questions and simple questions and measuring response times.

Whatever you choose it would need to be done constantly in the background or mixed with regular traffic while interacting with your site though as a human could use an AI to get through the front door but then take over.

Really cool question!

It also means you waste future-you's time too. For example when you want to integrate apps into your books (sheets is not reliable at scale), when you want to train a junior accountant to look after your books. When you want have to send a copy of financial statements to banks/tax-offices/investors whatever and they are used to a particular format.

All we need now is for boston dynamics to release their mech-warrior line...

Ok a bit tongue in cheek :P But honestly for most things you can use a web server in a language of your choice and spit out HTML. For the HTML design there are templates and frameworks responsive out of the box (bootstrap etc). If you need any in-page wizardry there are well documented javascript libs you can drop in. This approach still works for most applications.

This mirrors what happened with the rise of coding bootcamps. Another similarity between the two is the whole framework marketing machine.

I think its more related to tech becoming mainstream. A long time ago a lot of the people you met had a genuine interest in computing and then sort of fell into it as a career. Nowadays its fairly well plotted out like other fields, with all the baggage that comes along with that.

Paying for someone who can increase the efficiency of a bunch of other highly paid people is a sound investment. Not that this happens often in reality! A shit show is a shit show even with a paid cat-herder. But it can work very well given the right circumstances.