windows_sucks

I've really enjoyed using Reolink + Blue Iris.

I think it's being downvoted because it's a little too simplistic to be meaningful. Everything we do, literally everything, we do because it makes us feel good, and therefore everything is a transaction. We provide food and shelter for ourselves because, well, we enjoy those things. We help friends and family in need because we derive pleasure from helping others and seeing our loved ones flourish.

If we all agree on that basic universal law of human behavior, we can talk about higher level meaning about the role of an employer in society beyond the simple transaction of money for labor.

fwiw they release about monthly in the dev channel

works flawlessly on my X1 carbon

the client should be responsible for not executing embedded JS in a message

yeah I really can't fathom how the material design won out. it's so.... gimmicky. like when you click a button, and it radiates out a ripple across the button surface.

would love to see an example of the data corruption you're talking about

nothing but if you want to do something, say even at 1fps, you need to enable the signal to fire in the first place.

"onMouseMove" is a user signal that you would want to be fast. also signals should be used for more than just user input interactions, like "download progress" etc..

The problem I've had with Airflow is that it tries to do way too much: UI/logging/config management

I've really enjoyed using taskflow (https://github.com/taskflow/taskflow) it allows us to employ our existing logging and deployment paradigms.

why do you keep posting this over and over again in this thread? The department applied this rule to attempt to reduce turnover, not because they literally want dumb cops.

yeah but deployments and language choice are no longer a single teams choice now. microservices really do allow for a "we did our job" development

    make_pepperoni_pizza()
     is bad code compared to
     make_pizza(toppings=[PEPPERONI])

I think you can disable notifications, so you're not disturbed

I agree. If you can't rely somewhat on previous experiences to guestimate roughly how long a task will take, you're not a senior eng.

I mean, to illustrate the point, if you call any general contractor in your area and ask how long a new kitchen cabinet build takes, you'll probably get a price range and a time range, depending on several factors. They probably won't say "I literally cannot even fathom an answer to your question until I inspect the condition of the dry wall, wood prices and availability, etc.". This is because the people who want the thing built will use time and price etc as an input to decide if ironing out the little details is worth it.

Ever been told to do something by a developer and you firmly disagree? I'm not going to give in and do what he says

How do you go about doing this? A direct confrontation? Or by asking for documentation for their request (like a JIRA ticket), and then replying in the ticket with your suggestion? etc