andersonmvd
Joined 12 years ago
Karma
552
Submissions
266
Member since
Aug 4
Recent submissions
Comment · 15 days ago
Meta employees seems to be one of the evidences https://www.reuters.com/world/americas/meta-employees-said-l...
Comment · 17 days ago
Meta is also influencing Brazil's election: https://www.reuters.com/world/americas/meta-employees-said-l... - other social networks as well.
Comment · 2 years ago
Related thread: Boss as a Service – Hire a boss, get stuff done (bossasaservice.life) https://news.ycombinator.com/item?id=18512197
Comment · 2 years ago
Does it impact your friendship? I'd guess you may resent them if they kept a lot of money, especially when you need the money. Or you may start avoiding them completely when you're aware that you didn't achieve a given goal, no? I guess for small amounts it may work but on the long run it seems like a trap.
Comment · 2 years ago
I fail to see a reason where it would be a violation because of the following reasons:
1) it's a response to a user's request, i.e., not initiated by the repo author
2) it depends on consensus of the user.
3) it's not automated (most of the items from the policy are related to automation).
4) the repo author has no obligation whatsoever of maintaining the project. He is not paid or forced to do it.
5) if the user really wants to apply this change or disagrees with this practice, he/she can always fork it.
That said, I understand that it may still not feel "fair" compared to other projects that don't follow this practice. Or the feeling of "wanting to help but you're asked to do some things first".
Companies already do that to accept your pull requests though [0], which takes way longer than giving a star - and I didn't see a complaint about it on HN
Comment · 2 years ago
The goal of cybersecurity should be to align cybersecurity with existing processes, but minimizing friction. What the author experienced seems to be a high friction security program, which is the result of a suboptimal cybersecurity program.
This is unfortunately the reality in many companies because cybersecurity is implemented as a subset of a high level information security framework without qualified people to connect the high and low level requirements.
In the past, security departments were the "firewall gatekepeers", choosing who to allow or deny access. They started to change over time from gatekeepers to support the business but this transition is not complete as we know from experience.
The CISO has also has the dillema of having to support the business but will also be held accountable for any hack, which increases the tension on reducing friction vs increasing friction (and increasing control).
This is not an easy problem to fix, but I particularly think it's very productive to see posts like this so we can bring this topic to light and find the right balance.
And for those interested in learning how to add security to their organizations with minimal friction (security by design, especifically), I'm creating some webinars (free on youtube) here: https://devops.security/webinars.html
--
about me & contact: https://dadario.com.br
best pic ever: https://jayub-intercomm.weebly.com/uploads/6/0/2/8/60283505/1443822731.png
--
I kinda like to code. I more or less like to do product management. But I'm always delighted to ship products that people love.
--
"If you want to set off and go develop some grand new thing, you don't need millions of dollars of capitalization. You need enough pizza and Diet Coke to stick in your refrigerator, a cheap PC to work on and the dedication to go through with it." - John Carmack (quote stolen from HN user nchelluri)
--
"when the rubber meets the road", love this quote
--
"(...) you want to do projects that are inspiring and that make people excited about the future. my life's got to be about more than just solving problems who want to get up in the morning and say yes I'm looking forward to that thing happening (...)" mr musk
-- loginwithhn
wX4oPqNdLt