Working at company B
Working at company B
Working at company A
Working at company A
708 karma · joined November 3, 2021
Working at company B
Working at company B
Working at company A
Working at company A
But, its not like I love any of the new music I find. I can like it, but I'm never going to blast it on repeat for weeks on end like 15 year old me could. Its hard to make an emotional connection like that as an adult.
As a result, I care less about music discovery. I know I'm not going to find a revolution in my own tastes. I know I'm not going to convince a whole group of friends to do the same, like you might in highschool. Its just a little more colorless now.
Maybe some kind of new license is in order. Open source, but preventing cloud redistribution. I don't know, I can imagine the issues with that as well. You want AWS out, but you probably still want the small up-and-coming CI/CD tool in.
Then you can get as fancy as you want with RLS policies automatically attached to each table and validate the user based on a user table with capabilities. I have a feeling you could instead have the RLS rules automatically insert data instead, but I never tried it. It would have to be multiple updates though, perhaps a trigger/function.
The problem is SET applies to a session, and pgbouncer doesn't make guarantees about the session for a particular statement. Your statement might receive an existing session with another user's ID, or it might receive no ID at all.
Through AWS's RDS Proxy (beefed up pgbouncer AFAIK), the situation is slightly better, in that AWS will detect the modification to the session and 'pin' it to the current connection. Your data will be consistent, but pinned sessions can no longer be multiplexed, so you've basically removed the whole point of connection pooling to begin with.
Ultimately, its probably safer to just manually add the user into your queries. Its not that much overhead.
Functional programming uses stateless, immutable transformations to contorl data flow. The second you instantiate an object with some internal properties that change in memory, you are no longer programming functionally
I'm sorry, but a huge chunk of todays "developers" really are in the business of creating problems.
"Its a cool object" doesn't quite explain its ubiquity, or the fact that they are almost identical looking despite which side of the globe their on. That suggests purpose to me.
This seems to be unique in that, if you get a License from Nintendo, you're allowed to access this companies kit for free.
Still, on my local machine these jobs would take 5 mins so its not perfect. And as the build gets more complicated and more stages are added, the problem compounds since the initial download is the slowest part.
I’m trying to build a circuit simulator. It’s got two main problems to solve: placing and connecting drag and drop electrical components, and the simulation itself.
How would you go about this? The existence of the sim means there’s already guaranteed to be some global manager that understands the current layout and can compute from it. What I don’t know is if that means most things should be handled that way.
Should components be heavy, and make their own changes to the tree, and then let manager read the tree in and build up its schema that way? Or should components be just emit everything to the manager, who then can both build the tree and a state representation.
The second feels cleaner for this use case, but it feels not standard for Godot. Maybe it’s a bad project to start with.
I did build a basic platformer too, and found the distributed logic much easier to deal with there.
You'll be writing scripts to scan the net for open ports, automatically "hack" into them, then globally balance allocate memory between all of them according to certain parameters to make the hack the most "profitable". You'll be writing elementary socket communications, building scripts to feed analytics back to your home PC, even alogirthmic trading in a fake stock market. I had fun with it.
My urge is to lift logic up to the parent of any group of interactions, and let nodes just be renderers. But I understand that is absolutely not the design philosiphy of Godot, and probably won't scale.
I used a document db for our side of the billing integration and I really, really wish I hadn't.