3 ms·
The problem is, the feature is never actually "users should be able to select multiple receipts". It's "users should be able to select multiple receipts, but no
by prewett 2y ago
The problem is, the feature is never actually "users should be able to select multiple receipts". It's "users should be able to select multiple receipts, but not receipts for which they only have read access and not write access, and not when editing a receipt, and should persist when navigating between the paginated data but not persist if the user goes to a different 'page' within the webapp. The selection should be a thick border around the receipt, using the webapp selection color and the selection border thickness, except when using the low-bandwidth interface, in which case it should be a checkbox on the left (or on the right if the user is using a RTL language). Selection should adhere to standard semantics: shift selects all items from the last selection, ctrl/cmd toggles selection of that item, and clicking creates a new, one-receipt selection. ..." By the time you get all that, it's clearer in code.
I will observe that there have been at least three natural-language attempts in the past, none of which succeeded in being "just write it down". COBOL is just as code-y as any other programming language. SQL is similar, although I know a fair amount of non-programmers who can write SQL (but then, back in the day my Mom taught be about autoexec.bat, and she could care less about programming). Anyway, SQL is definitely not just adding phrases and it just works. Finally, Donald Knuth's WEB is a mixture, more like a software blog entry, where you put the pieces of the software inamongst the explanatory writeup. It has caught on even less, unless you count software blogs.
- CamperBob2 2y agoI will observe that there have been at least three natural-language attempts in the past, none of which succeeded in being "just write it down". COBOL... I think we're done here.
- guappa 2y agoPlease ping me in 5 years to reassess. I'm ready to bet 1 month of my salary that human software developers will still exist then.
- fragmede 2y ago1 months salary now, or then? You'll be 5 years further into your career, so it'll hopefully be higher, but also, the industry is changing. Even if ChatGPT-5 never comes out, it's already making waves on developer productivity where there's enough training data. So in five years will it still be a highly paid $300k/yr at a FAANG position, or will it pay more like being the line cook at a local diner. Or maybe it'll follow the pay rate for musicians - trumpet players before cheap records came out made a decent living. Since then, the rise of records, and then radio and CDs and now the Internet and Spotify means that your local bar doesn't need to have a person come over to play music in order to have music. or visuals for that matter. The sports bar wouldn't exist without television. So maybe programming will be like being a musician in five years, with some making Taylor Swift money, and others busking at subway entrances. I'm hoping it'll still be a highly paid position, but it would be foolish of me not to see how easy it is to make an app by sitting down with Claude and giving it some high level directives and iterating.
- guappa 2y agoYou have to make a PRODUCT, not an hello world app :)
- fragmede 2y agoUsing an advanced programming technique called modularization, where you put the code into multiple different files, you may find it possible to get around the LLMs problem of limited context window length and find success building more than a trivial todo app. Of course you'd have to try this for yourself instead of parroting what you read on the Internet, so your mileage may vary. =p
- guappa 2y agoWe both know it won't work, but please make a youtube demo about this.
- CamperBob2 2y ago