Hey, I'm the author of the blog post. Thank you for submitting this. If you have any questions feel free to ask and please let me know how the writing was. It's one of my first posts so I'd like to improve
It was a fun and easy read
Readit Newsnull_deref commented on I gave the AI arms and legs then it rejected me grell.dev/blog/ai_rejecti... · Posted by u/serhack_
null_deref commented on I gave the AI arms and legs then it rejected me grell.dev/blog/ai_rejecti... · Posted by u/serhack_
There is some dirty secret i learned in my time as a eng. manager: Working in open source / Being the maintainer of a popular library / Blogging about software: All this things won't give you necessarily a competitive edge but can work against you. It's counterintuitive but sometimes teams are looking for a more low-profile hire.
I agree with the other comments on this thread, but I have a question of my own, why not work as consultant at that point and not as team member?
null_deref commented on A Python dict that can report which keys you did not use peterbe.com/plog/a-python... · Posted by u/gilad
Mine was a bit more specific. I had a JSON object of data exported per account I was importing, and then a complex mapping (also JSON) of where to put each piece of data.
Therefore, I really wanted to know that I was actually pulling in all of the data I needed, so I tracked what was seen vs not seen, and compared against what was attempted to see.
In the end it was basically a wrapper around the JSON object itself, that allowed lookup of data via a string in "dot notation" (so you could do "keyA.key2" to get the same thing you would have directly in JSON. Then, it would either return a simple value (if there was one), or another instance of the wrapper if the result was itself an object (or an array or wrapped objects). All instances would share the "seen" list.
It's unfortunately locked behind NDA/copyright stuff, but the implementation was only 67 lines.
Nice very interesting, thank you very much for taking the time to explain a bit further
null_deref commented on A Python dict that can report which keys you did not use peterbe.com/plog/a-python... · Posted by u/gilad
I actually wrote something similar in nodejs for a data import system. Was very handy.
Interesting! Can you elaborate a little bit more on your implementation?
null_deref commented on I scanned all of GitHub's "oops commits" for leaked secrets trufflesecurity.com/blog/... · Posted by u/elza_1111
To be clear, Parameter Store is a separate product from Secrets Manager, but is essentially the same thing without features like the UI, key rotation, etc. Functionally though, they're the same (for example, passing secrets into an ECS container is just a matter of passing the ARN)
Thank you! Just implemented this in my lambda, still a bit frustrated there is no easy way to push env vars from the deploying machine
null_deref commented on I scanned all of GitHub's "oops commits" for leaked secrets trufflesecurity.com/blog/... · Posted by u/elza_1111
If all you're doing is storing, and not using advanced features like auto rotation, Parameter Store is free for most use cases.
Ok I may have misread the pricing model, I’ll look into it, thanks!
null_deref commented on I scanned all of GitHub's "oops commits" for leaked secrets trufflesecurity.com/blog/... · Posted by u/elza_1111
For a long time and probably still today, Google AppEngine kinda encouraged storing secrets in the YAML, which is easy to accidentally git-commit. There's no easy way to pass secrets to your services otherwise, unlike Heroku etc where it's always been a single command to put them into envvars on the jobs.
Last time I tried, the default suggestion was Cloud KMS (yeah), now there's some new secret manager that also looks annoying: https://stackoverflow.com/questions/58371905/how-to-handle-s...
And can we talk about the predatory pricing model? In AWS one secret service prices a secret for 0.4 dollars a month.
I was appalled when I first saw it, are you going to charge me 5$ a year for storing my 12 bytes?
null_deref commented on Why Koreans ask what year you were born bryanhogan.com/blog/korea... · Posted by u/bryanhogan
Drinking responsibly is uncool by definition when you are that age.
Yeah yeah I agree, it’s sometimes fun to go crazy in that age. I meant drinking responsibly in the broadest way possible
null_deref commented on Why Koreans ask what year you were born bryanhogan.com/blog/korea... · Posted by u/bryanhogan
The fact that all Koreans that were born in the same year become of a legal age to drink on the same day, probably creates some cool memories if you drink responsibly
Is it actually funny though?
If you like improvisation, some shows there are pretty good in that aspect