strongDM is hiring and we do not spend 20-40 hours or do take home tests. Email ryan@strongdm.com if you are interested.
607 karma · joined September 10, 2016
What are examples of products that sit on the endpoints themselves? One thing I have seen is that because an organization does not always control every asset (like an AWS Aurora instance), they can't simply install some agent on the resource itself to check for access. Also has many more failure modes in that individual agents going down means people don't have access. I might be missing something here though so I wanted to ask.
If you have the time to go through the codebase, it was an interesting read. Nothing too surprising, but cool to see how it all comes together.
Reading EFFs claim is pretty interesting, they state that saving a copy of a video is only one function of youtube-dl. I think the biggest problem is the name is called "youtube download", it is sort of difficult to downplay that saving a copy is only one function when the name implies it is the main purpose of the program.
GraphQL creates a data graph that powers the UI, REST creates a database that you can query on the UI and you have to compose it all together and manage.
I really like the techniques described here. I haven't gotten around to going through Michael Feathers's book, but the list of steps described is what I try and do anyways when working with legacy code.
It is amazing how fast bitrot can take hold of a codebase that isn't being continually maintained. The author's reference to broken window theory, that once you have a chunk of code that is pretty gnarly, the next person who comes along and has to add something to it just slaps it in there, it is already a mess, so why try and clean it up? There is a hard tradeoff with pragmatism that we have to make, especially if you are working at a startup where not getting to market could be the death of your company. But I think that knowing and understanding these techniques can give you confidence that you will be able to go back later and clean up your own legacy code.
I wish him the best going forward, it sounds like he is an awesome developer and teammate and whatever company he goes to next will be lucky to have him.
I'm not a fan of this change because:
- It significantly reduces the pool of repos that you can PR to. I've contributed to repos which haven't explicitly opted in to Hacktoberfest this year and in the past as well. Repos in which I am more comfortable contributing in than some random GitHub search result for the "hacktoberfest" tag. With this change, I am forced to look into those, or convince the maintainers to tag their repos.
- For intermediate or experienced programmers it voids the whole event because the vast majority of OSS projects won't get involved.
- After the spam fest that this year was, people aren't inclined to add the tag to their repos because it paints a target for spam over them.
- Maintainers can now gatekeep your contributions, so even if it's something meaningful the maintainer can deny you a +1 PR for your work. It can be frustrating spending a non-insignificant amount of time to get the t-shirt the right way and then have that time nullified.
- It doesn't address "hello world" spam repos. In fact, it encourages them because of the reduced amount of repos available to contribute to.
Level is hiring a Senior Frontend Engineer to help us build innovative IT solutions in remote management and monitoring.
Please apply through: https://weworkremotely.com/remote-jobs/level-senior-front-en...
Level is hiring a Senior Frontend Engineer to help us build innovative IT solutions in remote management and monitoring.
Please apply through: https://weworkremotely.com/remote-jobs/level-senior-front-en...