rvdmei
rvdmei on Hacker News
It’s contract only, mobile carriers are not happy that they have to maintain the 3G equipment just for IoT.
I can highly recommended not adding a reason at all for rejecting a meeting request. If I feel I do not need to attend at all I will let the organizer know. If the time conflicts with my schedule / plans I will simply ask for a reschedule. (And no, I’m not the CEO).
But from a technical perspective, adding end-point protection everywhere is not only a trend, but often a requirement imposed by law and regulation.
You are sort asking for legal advice. Not sure if I need to elaborate more.
Rancher Desktop macOS version is based on Lima.
It also comes with nerdctl (docker compatible cli). It interacts with containerd directly and is a drop-in replacement for docker cli.
Just curious, since FastAPI is mostly async, why not write the basic examples to use async?
I guess easiest would be Longhorn on top of k3s
To some extent, but this is beyond what is acceptable. Even if this is so support COVID notifications. Any install on an unmanaged device should be asking for permission to install something, unless you opt-in or something.
I think poetry is rally gaining traction. Poetry solves some problems in an easy way that are cumbersome to replicate with pip (like guarding against supply chain attacks with lock files) and teams are starting to realize that basic use of pip and requirements.txt no longer is enough to manage dependencies. I am starting to more an more projects adopting poetry and the uptake seems to look like the uptake I saw in FastAPI. Side note: I tried using pipenv, but is was just too slow for resolving dependencies. Curious what other people’s experience is on this with pipenv and poetry.
Just the thought of Google being able to do something like this scares the $&@*#% out of me. How on earth can you trust a company that does something like this?
Below is not just my experience, but also from other teams I have worked with over the past 10 years in an agile / scrum setting.
Sprints:
- pros
Helps to avoid continuous changing direction at request of stakeholders. 2 week sprint feel really good as planning horizon: not too long, not too short. Teams do not commit to anything beyond that timeline. Any roadmap commitments are based on stats and product owner responsibility. Team is not accountable for any missed deadlines.
- Cons:
It can feel like wash-rinse-repeat sometimes. Can be a killer for flow and feel inflexible when you are nearly there (getting it done) and the sprint review interrupts the flow. If the balance is bad you should probably look at kanban.
Daily’s:
- Pros
Excellent way to find out if team members need help or some syncing is needed. If done well team will “feel” if your getting closer to getting everything done. With work from home good to see everyone on the team at least once a day.
-Cons:
Hard to get right. Should be about inspection by the team to help adapt the plan and get to your goal, but this is often forgotten. Might become a way to “control” the team and put pressure on people and check for performance of individuals.
As for micromanagement: this is not exclusively found in agile / scrum. A micromanager will find a way to abuse any method to “control” their world. If you let go, set a clear purpose and direction, start helping team members to get more autonomous you will find that performance goes beyond what micromanagement can achieve.
Scrum (as defined in the scrum guide) can work, when it doesn’t: adapt and try again.
Just build something you need (or just a simple To Do app) and use a modern library / framework that uses the “new” stuff. I can highly recommend to give FastAPI a try. Even just going through the examples in the docs (amazing docs) should get you started.
Definitely a reason to try and game the metrics (and probably easy too). In my experience the metrics make sense when you use them to improve as a team, I would actually try to avoid using them as OKR or KPI.
Why would you want to game metrics that honestly can help improve your business outcome? The study is worth reading and to put it simply: the metrics seem to make sense anyway and if science proves that they do, that’s even better.
Not yet. Apparently Philips (TP Vision actually) is working on resolving the issue. If they can’t fix it I will definitely go back to the store (Dutch law makes them responsible for any defects) and try to get some kind of refund.
This might be a good explanation why my Philips 55POS9002 oled tv can no longer stream 4K with Netflix/Prime/YouTube. A Widevine certificate was revoked for some Philips TVs. Maybe the RSA key was leaked in the Philips firmware.
Posted by
rvdmei on Tuesday March 10, 2020 @02:37AM
from the nnw.ranchero.com dept.
Bugs do get to prod, that’s just reality. If you keep changes small and release often you won’t see many big bugs in production. We typically keep master in an “always deployable” state. If a bug gets found in prod, we either fix it or create a new commit that reverts the commit that caused the problem. If it’s a faulty migration, reverting the commit usually won’t work and we have to fix the bug. For QA we use a mix of automated tests and manual tests.
Rolling back is usually a bad practice and can get quite challenging if not impossible in distributed environments.
If you can pinpoint a specific commit that is causing the issue. Revert that commit and go through your standard release process.
Depends on where you are coming from and what you need. Developer productivity is really high (real world experience). It has better defaults / builtins compared to flask (much faster to get to production quality). Faster to learn than Django / Django rest framework. My team has been using it for a couple of months now and it’s been really easy and fast to get an API up and running with api docs, data validation, middleware for auth and metrics, persistence, mix of async and sync functions and background jobs.
Posted by
rvdmei on Monday May 13, 2019 @03:16AM
from the dutchreview.com dept.
Posted by
rvdmei on Saturday March 30, 2019 @07:53AM
from the hamy.io dept.
This is HN at it’s best, nobody answered the original question. Diagrams such as the one on the git-lfs site are most likely created with the traditional tools in the Adobe Creative Suite (or something similar). I have seen and used my share of design, diagramming and modeling tools over pas 20-30 years and until now I haven’t run into anything that ticks all the boxes. Usually diagramming and modeling tools aren’t the ones to make something look really nice.
That would be awesome. I think WireGuard + Tinc + userland windows + iOS support would be the ultimate VPN solution. Bringing WireGuard back hail to Tinc would bring that one important step closer.
We have been using WAMP 2 and crossbar in production for a while now. We have js, PHP and python all talking to each other without any issues. We will probably add Go in the next months (prototypes are already working). For authorization and authentication you have to spend some effort to get something working without hardcoded config. Biggest down side is that clustering of the open source router crossbar is not really possible and we haven’t seen any production ready alternatives. Until now this wasn’t really an issue, but it looks like this might be the reason why we will leave WAMP / crossbar this year. Best options to replace this with is probably some solution based on GRPC or NATS.
Technomanifestos by Adam Brate. I never had any introduction to the history of information technology until I read this book.
This is just another attempt to get money from eager “investors” through an ICO (according to Kodak it will be SEC regulated, I would be very surprised, it would probably be the first)
Why do you need a block chain for this? The functionality can also be created without this.