iovrthoughtthis

apologies, the names is a little tongue in cheek. the goals of this is:

1. create an abstract syntax tree over the tree sitter trees for queries that work across language (function) @f matches functions in any supported language

2. create a smaller (in text) query language based on the semantics of css selectors e.g. in the 'c' language id#Validate -> [((function_definition declarator: (function_declarator declarator: (identifier) @_n0)) @_root2 (#eq? @_n0 "Validate")) ((call_expression function: (identifier) @_n1) @_root3 (#eq? @_n1 "Validate"))]

3. provide some useful commands on top of this to allow humans (and llms) to be able to quickly learn about codebases from the cli

i made this for myself, just sharing it because i probably should

yes i used claude code for most of this

Code review should be a separate function

Nah, theres not a technical or business solution to this. Music is cultural and we'll develop new cultural technology to solve it. Vision + regulation would help things move a little faster but the pendulums swing is inevitable.

We have to let go of old artists stuck in these patterns and find new, ideally local artists.

Yes

A local search indexer that indexes every page I visit (with tools for obvious exceptions) and lets me full text search them.

Is this some sort of paid for PR to divide the category of social media in the face of governments gearing up to regulate social media apps?

html encodes a tree of objects

css applies attributes to objects via graph queries

the queries are tightly coupled to the tree. you must work hard to avoid scatter gun edits now. it doesn't make much sense to have attributes stores in a separate location to their use

it would be like assigning all of your instances attributes using decorators

I suppose its a bit like winning a first person shooter game with aim assist on

It is not an authentic display of pure skill

the law of shitty click-throughs strikes again

I think what breaks first is team / org dependent but ime: alignment & quality standards

I found a mixture of shoehorning the vision into as many conversations as possible and occasional in person meetups (we die roughly yearly) helped with vision. I dont have measurements but my concern for teams decision making dropped a lot and disagreements in smaller discussion settings also dropped.

Standards dropping was secretly alignment too but more around why than what. I found building a culture of excellence helped e.g. "we're here to build software we're proud of, from the code to the experience, and you are the right people do it, so lets build something we're proud of.". You or who ever has to actually believe they are the people to so it though.

Im sure people have more concrete and technical examples.

Agree, there is a watered down product vision

As I've experienced getting older I've found it's more about the lack of available time and focus.

I don't have the hours of time a young person does and I don't have the focus, there are a lot of other thoughts, emotions and responsibilities competing for my attention.

Would love someone who's aware of the literature to throw their hat in the ring though.

We iterate.

You have a lot of comments that start with "OBSERVATION"

What are you trying to communicate here?

Location: Eastbourne, UK

Remote: Yes

Willing to relocate: No

Technologies: ruby, javascript (js,jsx,ts,tsx), python, golang, docker, sql, cloud

Resume: https://drive.google.com/file/d/1KCGrf3abcL3L9za3GjMizBaODGr... Email: jasper (dot) lyons (at) gmail (dot) com

I'm a senior engineer and serial technical co-founder with 15 years experience. I've started 6 companies, raised some monies and built teams of up to around 50 people. Looking for short intense projects to pay bills while I focus on building Eastbourne's Music scene!

budget based economics may be the worst thing to happen to large organisations

this is hilarious

c# (and the project i was working on) destroyed my love of programming

at least 10x better than a human

this could also be the reason humans notice changes

This will push streaming services to lobby governments to crack down harder on pirating.

The issue is that the service users don't exist in a cohesive and aligned bloc, whereas rights owners, rights licensers and streaming service providers sort of do.

Anyone that attempts to change licensing laws will experience way more friction than those who advocate for using the existing infrastructure of law enforcement to reduce pirating.

Things will only get better if streaming companies lobby for changing the way licensing works to support delivery to end users and/or government departments advocate for end user experience.

this isn't individual devs fault

this is bad practice by service integrators

this is crazy

cant help but consider that fujitsu is an SI that competes with infosys and this really undermines fujitsu in the minds of british tac payers...

1. list all the people you know in each of these sorts of roles 2. ask them to either join you or if they know anyone who might be up for it or if they would help you hire someone by being your capability sense checker 3. if you can't drag together a rag tag team then you need to go out and meet more people

previous places you've worked are great sources, as are alumni networks, friends and family.

failing that, go become a part of a community like a runner club, rock climbing gym, music scene, maker space, game jam. ideally you do these thing because you enjoy the though.

be prepared to pay people. don't hire anyone you're not confident in (if you're not sure on someone because of pay then go out and find the money [yes, i am aware this is v hard])

imo we've not settled on a meta as the game is relatively new, has been changing a lot over the decades, they take a long time to play and lots of the learnings are fairly hidden in companies.

I suspect it will be used in generality haha

is this science to support back to the office?

I find this too concrete to be useful. I have a more principals / tradeoffs approach to code review:

Areas:

  - Readability - how understandable the code is
  - Maintainability - how the code enables the project to evolve
  - Risk - security, regulatory and other vulnerabilities
  - Correctness - whether the code does what you intended
  - Robustness - how well the code handles unintended circumstances
  - Performance - how resource efficient the code is

## Readability

Code is readable if it meets your expectations and surprises you only when there's something you don't yet know about the technology. We expect code to look like the code around it. To follow most, if not all of the technologies idioms. To use clear and informative names. To explain why deviance exists. To be as abstract as the concepts being abstracted are crystallised.

## Maintainability

Maintainability is the code's relationship with the wider team and time. You should be able to learn all you need to know to change, test and deploy code. You should be confident that any changes you make will not cause unintended changes elsewhere in the code. To make a change, you should have to touch as little code as the concepts being changed are crystallised. You should be able to debug an issue as easily as, the system the issue is in, is old. You should be able to track down and alter the changes that introduce a bug quickly. You should be able to learn why a change exists.

## Risk

Code is low risk if it accounts for, and where possible, mitigates the various risks to a project.

## Correctness

Correct code does as you expect and surprises you only when there something about the system you didn't yet understand. Validating correct code is as automated as the validations are frequent. Correct code is only as complicated as the concepts it models. Correct code is only as abstract as the concepts it models are crystallised.

## Robustness

Robust code handles unexpected circumstances safely, quickly and predictably. Validating robust code is as automated as the validations are frequent and as comprehensive as the failures are risky.

## Performance

Performant code is as resource efficient as the resources are expensive, but also as efficient as the development costs are cheap.

thus pattern divorces the code from the program ime

i appreciate that using an ide makes code navigation easier but i reject the notion that you should need one to navigate the code