Yeah, might be more like 6 months from now when I upgrade my k8s cluster version and cycle out containers I'll have no idea why things are failing. Fun times.
Hi all, I figured this is pretty critical to share out. Docker recently announced in February that starting April 1st unauthenticated Docker Pulls from the Docker Hub registry will be limited to 10 per hour. This is a pretty significant breaking change, especially for those that run Kubernetes in production.
Many Kubernetes clusters may host open source software with images pulled from docker hub without credentials, thus by default the pulls are unauthenticated. And many of these clusters run behind a NAT.
I was very surprised to see this warning from Digital Ocean today and that there's only a 3 day lead time to address this. Surfacing for visibility in case anyone else doesn't regularly follow Docker Hub updates.
The entire 18f org was let go. Many of these employees oversaw the building of digital services.
Login.gov is a most critical SSO resource for logging into services such as the IRS for tax payments. It’ll see peak usage next month for taxes. The teams maintaining these have been indiscriminately let go.
More of these online services will start to go down, rapidly.
If the point of DOGE is really to tackle the deficit, all these moves are incredibly shortsighted.
(Yesterday the 18F former employee put https://18f.org/ as a transparent warning of what’s to come)
This was hauntingly beautiful. A story of conscience and reconciliation with the paradoxes of war and personal spirituality/religion.
His decision to join the war as an interrogator, believing his presence and oversight would ensure the humane treatment of prisoners is admirable. I often wonder what is the right thing to do: non-participation, or conscientious participation to ensure abuses are minimized.
Dmitry, you never cease to amaze me with your side projects and the lengths and hurdles you go through with ease. These writeups are fun to read and provide me with some inspiration if I'm ever stuck on something.
For those that don't know, Dmitry also ported linux to an 8 bit micro-controller.
Hi there! Sunil here (CTO at Buffer). Really great question! We've had a long and hard look at our salaries and have been in the midst of overhauling how exactly we determine salaries. One of the great things with being transparent about our salaries is that we learn so much about how we've originally set up our salaries and how we'd need to further adjust things. We received some great feedback and through that, we've realized how under-market our rates have been for areas like SF and NYC, while being quite above market rates in many other regions. We've been in the middle of overhauling how salaries get set, and have adjusted developer salaries based on some solid feedback. I believe we'll update the public numbers and be transparent about the process we took and our overall learnings quite soon!
Generally our approach with salaries (and much of the company) has been to iterate with continuous feedback loops. The feedback we receive in HN may further influence how we think about things. Would love any more thoughts/advice you have :)
This is a great post! Our entire team is fully remote all over the world, with 31 people in 22 different cities in each major continent. I'm quite glad the OP wrote this because it talks about the very first thing I try to say when people ask about what it's like for remote working: Remote working doesn't work for everyone. Some are energized by an office environment with face-to-face time, and others are more productive by self-managing and lots of focus time. I feel like it's key to recognize which camp you're in.
We've had to construct our hiring and on-boarding process to gauge in so many ways whether someone is a good culture fit and is also energized by remote working. We feel like there's no way to truly tell unless you work with them under a contract period, which is what we do for everyone that's hired. Generally we've found about 30% who enter this period aren't quite a fit for either remote or culture for us.
Yup, that's right. I'm an early Buffer employee/cto. I also wanted to confirm that I had the option of receiving some liquidity in this round by giving up some of my options that have vested. I chose not to sell them at this time as did most of the employees that had vested shares. Great thoughts guys!
We do all hands support at Buffer as well. At first it started out as to help maintain the inbox, especially during launch days, which was always fun. We quickly realized how important this is. So much of our product decisions, bug fixes and security patches have come from talking first hand to our customers.
I really love this because it's been an opportunity for me to help others and also learn about different areas of our product that I may not deal with on a daily basis. We've started having a support focus be part of the engineering on-boarding process.
We've recently gone to an all hands day rotating system which has been working well. I'm curious what others do. Do you do more a free-for-all, or do you have a more structured system?
Hi there! Our engineering interview process is something we're continuously iterating on. At the moment this is how it looks: 1 technical interview with Sunil (discussion on past experience, code walkthrough and a high level technical question). 2 culture interviews with Carolyn and Leo. Then a mix bag interview with Joel. If all goes well, we have a 45 day trial period where we gauge technical and culture fit from both sides. Hope that helps!
That's exactly right imo. Running MongoDB in production, you end up concerned over the performance of each query (as you should be). MongoDB's profiler makes this easier to investigate.
If you hit a db level lock limit, you're probably running a sub-optimal or unindexed query.
Thanks for the update! We're working to have expected functionality when third party cookies being disabled. I'll keep an eye on when it's planned to be released.
There were rumors about third-party cookies being disabled by default in v22. I downloaded it and found this not to be true. Can anyone shed some light on when Mozilla plans on doing this? http://www.pcworld.com/article/2038956/mozilla-postpones-def...
By HN guidelines, things that are appropriate are "Anything that good hackers would find interesting... anything that gratifies one's intellectual curiosity."
This is the story of Dr. Joshua Miele who, after this horrific attack, has been working on some really interesting projects using technology to make the lives of those living with disabilities better.
After reading this story, I found an interview he did describing some of the projects he's been working on, including tactile maps on smartphones to help blind people navigate their world.
http://www.kqed.org/a/forum/R201106171000.
Anyone else having trouble working through their examples? It seems like they haven't made their example repositories public yet.
https://github.com/googleplus