evolve-maz

5 ms·

1.
by evolve-maz 4d ago
It's interesting to see how over the span of just a few years a lot of people went from: > Architecture astronauts are out of touch and shouldn't give any advice because they haven't written code in ages. Only the hands on
2.
by evolve-maz 5d ago
Only in the last few years did I start using SQL properly. Before that my pipelines would live in python. Now I offload as much to the db as possible, and keep my python simple glue. I'm very happy with this compared to other methods i
3.
by evolve-maz 9d ago
I also really enjoy programming, and relate to your comment below about sometimes waking up in the middle of the night because your brain figured out how to code a hard problem. Sorry to hear you're having a rough time with work. I do
4.
by evolve-maz 24d ago
I've spent many years doing work in compliance for airlines. Hundreds of pages of documentation to describe the different rules and regulations which must be followed in specific scenarios. We'd convert those documents into a prog
5.
by evolve-maz 1mo ago
I use this pattern for my makefiles. First item is for "help", and it dynamically scrapes all the other commands (assuming format <command>: ## <description>). So if I do 'make help' it'll list all the c
6.
by evolve-maz 1mo ago
Yep, the poke pattern is additionally nice because it means my state reconciliation function is the same when running on cron interval vs event driven. On the flip side, it helps to have endpoints which have a query param linking to some so
7.
by evolve-maz 2mo ago
Anthropic releasing things like Cowork explains why they wouldn't want you to host the model and retain your data. They need that data so they can push into wider job automation, displacing the SaaS companies who used Anthropic in the
8.
by evolve-maz 2mo ago
Here's a common workflow: - Ask cursor to summarize your existing repo to write you a nice readme - Cursor opens repo - Cursor looks at current code - Because it's going above and beyond, it also wants to give you some metadata ab
9.
by evolve-maz 2mo ago
I've been a manager for some years. Without sounding too up myself, what made me good at management was the fact that I knew how to do the things I asked people to do. It allowed me to critically evaluate the work, set realistic timeli
10.
by evolve-maz 2mo ago
I wouldn't accept that junk from any engineer in my team. My experience with good developers has been: - Create something a bit ugly which works - As more use cases come in, refactor code and clean up old gnarly bits LLMs tend to work
11.
by evolve-maz 2mo ago
A lot of rules like "some fields are hidden / shown based on other fields" come from restricting users to only expressing valid object states. E.g. I have a form where a user can pick a "notifier". They get a first
12.
by evolve-maz 2mo ago
I haven't seen a code base which hasn't fallen into degradation from that loop. From personal experience, any "correction" leads to an LLM writing more code, or stripping apart interfaces and mixing logic poorly, or addi
13.
by evolve-maz 3mo ago
That's because the assumption is the new product can already do what their current product can, so the things customers ask for is the extras. It's really easy to forget that a lot of work went into "baseline" features w
14.
by evolve-maz 3mo ago
If I flag every line in your PR as a potential security bug then I have 100% recall. Obviously you need a mixture of high recall and low false positive rate. If 7/8 flagged items are fine its much more likely people will ignore the war
15.
by evolve-maz 4mo ago
My advice would be to only use HTMX for data state related operations. For something like an intelligent back button, unless it depends on resource state do not use the backend to calculate it. The recommended htmx way would be to hook up a
16.
by evolve-maz 4mo ago
All the talking points and techniques are those which were used when pushing outsourcing: give better specs, write detailed tests, accept bad code because it works so who cares, we can just rewrite from scratch later, and my favorite "
17.
by evolve-maz 5mo ago
Nice write-up. Did you try the problem out against a MIP method?
18.
by evolve-maz 5mo ago
Presentation of data and a story is a very important part of the service. That's why we have a mix of pictures, tables, paragraphs, etc. It's why UX is so important in general.
19.
by evolve-maz 7mo ago
Expertise isn't there because people are outsourcing that sort of work to companies. I didn't know how to do much of anything, until I had to do it for work. Then learning everything became way easier.
20.
by evolve-maz 8mo ago
Htmx has events you can listen to like htmx after response. You can think of it almost like a middleware. After the response comes in, your callback is triggered and you can make the callback look up some attribute given the calling parents
21.
by evolve-maz 8mo ago
FYI I had a similar problem to yours in terms of having jobs I wanted to run on a schedule. I also had an extra layer where I wanted to let users to define jobs with their own special parameters etc. Maybe what I did is helpful for you: - F