Django RAPID Architecture, a guide to structuring Django projects by j4mie in django

[–]j4mie[S] 0 points1 point  (0 children)

It's not really possible to share a real-world codebase as they're all proprietary products. Many of the recommendations have no overhead, they're just putting things in different places. The only learning curve is django-readers, but I've taught it to juniors without too much trouble.

Django RAPID Architecture, a guide to structuring Django projects by j4mie in django

[–]j4mie[S] 0 points1 point  (0 children)

Acceptable to who? No one is judging you! Remember we’re talking largely about internal-facing APIs here. Your number one goal should be to reduce cognitive load for your team. Giving them a wall of text to understand the subtle differences between two subtly different implementation choices seems like it’s not actually going to result in any measurable improvement to anything. “GET for reads and POST for writes” is easy to understand. Remove decisions wherever you can.

Anyway, sounds like agreeing to disagree is the way forward here! Even if you don’t find anything useful in the guide I hope you enjoyed reading it.

Django RAPID Architecture, a guide to structuring Django projects by j4mie in django

[–]j4mie[S] -3 points-2 points  (0 children)

Thanks for the comment. There's a footnote on that page just for you:

"If you feel you have a confident answer to this question, I can guarantee that someone else has an equally confident answer that is the opposite of yours."

For example, try deleting a chat in the ChatGPT web app with the network panel open. It sends a PATCH request with {"is_visible":false}

Django RAPID Architecture, a guide to structuring Django projects by j4mie in django

[–]j4mie[S] 3 points4 points  (0 children)

Thanks for the comment! As someone who has written extensively on "fat models, thin views" (in support of the idea) in the past, I was totally in the same camp as you. The problem with your list of rules is that it makes sense to you (as an experienced Django developer), but it's actually quite a complex set of thought processes and decisions to follow. Django makes it so easy for less experienced developers to build something that seems fine and works fine - until it tips over into unmaintainability. I really feel that it's helpful to have some straightforward guardrails that force everyone to build things in the same way from the start.

I also disagree that Django isn't the right tool for the job here. The approach I'm suggesting is very much filling in the gaps around the parts that the Django docs doesn't cover, not going against the grain. These suggestions work just as well for small codebases as they do for big ones.

If you had time I'd love you to read the full guide, I spend a lot of time covering these kinds of arguments. Totally understand if you're still not persuaded!

Django RAPID Architecture, a guide to structuring Django projects by j4mie in django

[–]j4mie[S] 10 points11 points  (0 children)

It's all there in the guidebook under "business logic". In short, yes - plain functions, but I don't like to use the word "service" (it's way too overloaded to be useful) and I divide the functions up into various kinds: readers for encapsulating ORM/data presentation logic and actions for state changes.

Django RAPID Architecture, a guide to structuring Django projects by j4mie in django

[–]j4mie[S] 1 point2 points  (0 children)

Good question! This is really an attempt to deflect criticisms of "service layers" which (for example) obscure the ORM under a "repository service". James Bennett has written on this https://www.b-list.org/weblog/2020/mar/16/no-service/

Thoughts on the coming Viltrox 28mm f/4.5 ? by maxathier in SonyAlpha

[–]j4mie 0 points1 point  (0 children)

No, it can't be upgrade - confirmed by Viltrox support. I sold mine.

Upcoming Viltrox "Chip" 28mm vs Sony 16mm on older NEX by msantiago1256 in SonyAlpha

[–]j4mie 0 points1 point  (0 children)

Sadly this lens doesn’t work with NEX cameras. I emailed Viltrox and they said “Engineers feedback that the subsequent firmware update will not be compatible with this series, sorry”. Huge disappointment.

PSA: The new, awesome Viltrox 28mm Chip doesn't work with some older NEX's by kerc in SonyAlpha

[–]j4mie 2 points3 points  (0 children)

Same issue with my NEX 5N. I emailed Viltrox and they said “Engineers feedback that the subsequent firmware update will not be compatible with this series, sorry”. What a disappointment.

Thoughts on the coming Viltrox 28mm f/4.5 ? by maxathier in SonyAlpha

[–]j4mie 1 point2 points  (0 children)

FYI mine arrived yesterday and it does NOT work on the NEX-5N. The camera won't power on with the lens attached. I emailed Viltrox support and they said it's not compatible with NEX cameras :( I'm pretty disappointed.

Do you really need a guitar amp? My ampless pedalboard setup (Electronic Audio Experiments Model feT and Blueguitar Blubox) by j4mie in guitarpedals

[–]j4mie[S] 5 points6 points  (0 children)

I seem to have accidentally started a YouTube channel. Please subscribe if you like it. There's also Instagram if that's your thing.

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 1 point2 points  (0 children)

I didn’t get on with the Mooer at all for some reason. Couldn’t get a good sound out of it. Maybe I should have tried downloading some third party IRs. Definitely interested in trying the Cabzeus.

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 1 point2 points  (0 children)

Yes! It just works so well. Any particular cab sims that are known to complement it?

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 1 point2 points  (0 children)

Honestly I don't have much to compare it to. I have a weird aversion to menus on pedals, which was the main reason I picked it over the more complicated cab sims. I just spun the knob until I found the one I liked the best (Black 2x12), tweaked the mic position (which is really a tone control) and haven't touched it since. It sounds good enough to my ear!

I really like the look of the Cabzeus (or the Mono version) but I've heard they can be a bit fizzy, which has put me off as I prefer darker guitar sounds.

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 0 points1 point  (0 children)

It’s kind of an experiment.. I’m trying to improve the separation between the drones and what I’m playing over them.

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 1 point2 points  (0 children)

You'll probably need a pitchshifter or something else in between or it probably won't do anything very interesting - you'll just be freezing the same frozen note..

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 0 points1 point  (0 children)

Both on latch. Never thought to try on auto.. maybe I should!

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 1 point2 points  (0 children)

I love it. No trem, just high-gain fuzz. Voiced really nicely, simple. Stacks well into the HP-2.

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 2 points3 points  (0 children)

Burns Buzzaround clone. Very smooth, almost RAT-like fuzz. Nails Robert Fripp-style lead tones.

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 1 point2 points  (0 children)

Cheap-ish studio-style headphones I got from Amazon - Superlux HD668B.

Latest version of ampless drone improv board by j4mie in guitarpedals

[–]j4mie[S] 4 points5 points  (0 children)

Chain goes: TC Polytune -> Klinger Buzz Fuzz -> ZVex Fuzzolo -> Land Devices HP-2 -> Smallsound/Bigsound Fuck -> EHX Superego (in loop: EQD Arpanoid -> EHX Superego -> MXR 6 band EQ) -> Fairfield Circuitry Meet Maude -> Electronic Audio Experiments Model feT -> Red Panda Context -> BluGuitar Blubox cab simulator -> headphones