justinwp

This is absolutely not true.

I have a home hydroponics setup in my garage on two tiers of a home depot storage rack covering about 24 sq feet. We eat the equivalent of $10-15 worth of leafy green veggies and herbs every single day. The produce I grow is far superior in taste and more diverse than what is available at the grocery store.

My maintenance includes every 3 weeks topping the water/nutrients and checking pH. This could be extended to 5 weeks or more if I went from DWC to Kratky method, basically just turning off some of the circulation pumps. I probably spend about 10 minutes a week pruning, adjusting air circulation, etc. Everything is controllable from my phone (water pump, aeration, lights, etc).

Mostly about running(ultra distances) and my career as a software engineer. Built with 11ty.dev.

Other discussions such as "why doesn't this code work?" or "this behavior seems unexpected" we redirect to StackOverflow and GitHub. Discord also serves as an activity hub for us as we have channels with automated feeds from blogs, youtube, stackoverflow, github, twitter, etc all located in a single location.

This pattern seems to be working for us.

The reason? No comparable homes that were recently sold AND available via MLS (private sales are ignored). The rules for appraisals breakdown when there is no liquidity. At least Zillow still considered private sales. The Zestimate was much more correct than the "expert" appraiser.

Overall, I am very pleased and looking forward to the continued improvements.

More on my setup, charts, etc here: https://jpoehnelt.medium.com/upgrading-to-starlink-bc6d4cd7e...

[DONE] CO - Bennet (Thanking him)

[DONE] CO - Hickenlooper (Urging him to support)

> And that reward / grading structure may not at all correspond to either the monetary or cultural success of a corporation.

The key feedback/suggestions I see for my own performance review is to define my impact on both the monetary and cultural success of my org. Exactly the opposite of what you are saying.

> being asked to 'level up' and told that this is your mission can lead to an unpleasurable career

I don't see this happening either. I commonly hear others say the opposite and make it known they are no longer trying to level up and that they are happy where they are.

> technical team lead to management or architect

This does not jive at all with the various career ladders I see. There is no ceiling that requires me to move to management in my tech ladder.

> find that you don't enjoy the new responsibilities

To some extent, the promo process levels up employees already working at that n+1. Sure, some may not want to maintain that, but that is ultimately up to the individual.

Disclaimer: I work at Google, opinions are my own.

- security - minimize privilege escalation and access to infrastructure

- scalability - different workloads need different metrics to scale(CPU bounds vs connection bound)

- dependencies - why burden devs with all dependencies especially some that are more difficult to setup dev environments for

- service per backend dbs/etc (overlaps with the above)

- domain - can place domain specific skills on a team

2. Exactly the same process except there is a single pr instead of multiple across multiple repositories.

One of our challenges was integrating one of our public repos into our repo and that is more of a difference in release patterns(semantic versioning vs nightlies). We use copybara to help with this problem.

- https://github.com/google/copybara

- Ease of onboarding. Being able to quickly build or test any target is awesome for the new employee.

- Ease of collaboration. I can see all of the code easily and can learn from these patterns. I can also quickly contribute or extend apis and fix all usages without concern for breaking changes.

Our use of Bazel quickly gets us around git scale issues by enabling external dependencies that can be loaded into the workspace without fully vendoring everything.

We get around some of these nonhermetic issues with python and dependencies by using a consistent docker based dev environment for everyone. Only takes a few minutes bazel build/test/run anything in our repo.

EDIT: We run Bazel in drone as part of our CI/CD system and this is probably the most unoptimized part given how they do not work that well together. Bazel query allows us to due targeted builds/tests based upon the git changes and dependents of those changes.

there are better things to eat than shitty meat from cows grazing in a desert. i'll take the outdoor activities and the preservation of these ecosystems

And yet it is an incredibly destructive use of land for so few cows. BLM land is often shrubby desert and is not able to cope with the impacts of the cows and remain a healthy ecosystem.

If you are lucky! Docker makes no guarantees about this. I'm betting most data science dockerfiles start with "RUN apt-get update && apt-get install -y -q \ && ... ". How much do you stick in numerous run commands following that? Docker images are not deterministic by default.

- scaling based on very disparate resource requirements across our api

- security isolation of critical backend infrastructure

- language requirements and dependency management

- accommodating different skills and groups of skills across our organization

You can read more on the technical side here: https://medium.com/descartestech/geovisual-search-using-comp...