1. Why focus on Swifts as opposed to any other species in decline? They state that they are "iconic", so maybe that's the answer? Are they more "iconic" than any other specifies in Scotland?
2. Why are these bricks the best solution? Why not take that money that would be spent on bricks and instead preserve land, or just build them dedicated houses elsewhere?
3. Why does this need to be done via government mandate versus voluntarily asking people to build Swift housing in existing buildings or land?
I'm worried that this is a government policy with great intentions that will result in economic costs with unmeasured benefits and bureaucratic bloat. Hopefully I am proven wrong!
GDP records market transactions. So in your scenario, purchasing the chicken, the chicken feed, the chicken coop, etc would all be measured. The time spent raising the chicken (assuming you did not pay someone to do it), would not be captured.
However, I think part of your criticism is a moralistic and health based argument that raising a chicken is intrinsically better and healthier that Doordashing fast food. When a consumer chooses a $60 delivered meal over a $45 home-cooked alternative, that reveals a preference for whatever they value, such as convenience, time saved, taste, service quality, etc. GDP doesn’t evaluate whether that preference is “good”; it only records the transaction value that arises from it.
So I agree GDP is not a perfect measure, but it's far from useless.
I would not over complicate this. My personal four part plan for this is:
1. Donate a portion of my income to charitable causes I find worthy. I would like to target 10% of my net income.
2. Volunteer at a local organization that you care about. There are usually ample opportunities for committed volunteers if you look for them.
3. Have children. Try to raise them to be responsible, caring citizens. That way I can extend my efforts to the next generation.
4. In the near future, I intend to attempt to get involved with local politics somehow. I am still figuring out the specifics, but I am thinking that running for the local school board would be beneficial.
This is spot on. Obviously there is a lot to dislike about performance reviews, but big companies need some process to determine who gets a raise, who gets promoted, etc. Although flawed, performance reviews are the best process for that.
I think the things that companies can do to make them better are:
2. Have transparency about the ranking system and distribution to all current employees and future employees.
3. Ensure that some amount of accountability is shared at the department level and also at the team level, so you can have somewhat objective conversations about trade-offs between departments and teams.
Has anyone implemented a DSL for a professional use case? I would love anyone to share what was the use case, what alternatives did you consider and how did you measure success?
I have previously implemented one for credit policy decisions, but I am not sure in hindsight if it was the right approach and we did a poor job of measuring success, so I would love to hear from the community.
This is a common practice in other high altitude, high traffic mountains, such as Aconcagua. Rangers actually watch you deposit your excrement bag and fine you if you do not do so or they catch you leaving your waste on the mountain. I'm frankly surprised its just now becoming a policy on Everest.
It sounds gross, but in practice it is not as bad as it seems. For anyone interested in the details, it is stored in multiple bags (one bag per movement, then multiple larger outer bags) and freezes pretty quickly, so there isn't really any smell.
" They could only get hired into new companies where nobody knew any of their past coworkers, because a simple reference check would reveal how difficult they were to work with." --> Any tips on how to effectively conduct reference checks? In my experience, candidates will only provide references from folks that they know will give glowing review, so you end up with generic positive feedback that ends up not being informative.
Would love to hear any strategies others have found successful.
I don't think its any less convenient for my partner than if I worked in an actual office. Plus, I still have the added benefit of no commute, which means more time with my partner.
I see the value in this, but I personally have not had success with it. I have found I am most effective remote if during my working hours, I don't do anything I wouldn't do if I was working at the office. For me, that means no laundry during the day, no extended lunches, etc. It keeps my mind in "work mode" and at the end of the day, I shut my office door and transition my brain out of work-mode.
Streamlit and Shiny for Python are both great for cranking out simple UI's for basic use cases, especially where there is a tie-in with something data or machine learning related.
A typical workflow could be for a team to prototype in one of these tools, get feedback, but at some point they eventually get rebuilt as a proper webapp. I would love to see these tools evolve to not require that total rebuild. Maybe they could add the capability to export to React or Angular. Then that could be used as a starting point for converting that into a proper webapp.
"...rather you get a bunch of people xgboosting their way up your leaderboard" -->
I don't see that as a universally bad thing. I feel this is actually very representative of the majority of ML projects that most organizations encounter. Most organizations don't have petabytes of data and a huge compute budget to train a DNN. They typically have megabytes to gigabytes of somewhat crappy data and need something that can be developed and deployed relatively quickly for low cost.
I've had a similar thought. I read a LOT of these various blogs and I frequently ask myself whether its valuable and how much time I should invest in these. I've concluded its probably valuable and a few hours a week is probably the right amount of time.
I think where the value lies is in when I am asked to give input into product or technology strategy. Having a broader understand of the technology ecosystem is a useful foundation for making recommendations to my specific scenario.
Yeah I totally agree, but I do think there are times when starting with the absolute most basic implementation that meets the business needs is the way to go. That could be a simple bash script, or a python script without Django, etc.
In my experience, the key is making those tradeoff decisions in an educated manner. Ideally, product and engineering and in sync and have a somewhat informed view of the future, so appropriate tradeoffs on velocity (simple bash script) versus extensibility (Python with Django) can be discussed.
Pinecone is in a tough spot. A huge number of database vendors are implementing vector functionality into their products, which risks the niche that Pinecone is attempting to carve out for their business. They are probably trying to gain adoption of their database by developing an open source RAG framework that leverages their database and gives companies a solution to quickly implement RAG in their specific applications.
Regarding whether RAG will still be required in the future, this is a good question. Increasing context window sizes may render this moot or much less important. However, there are still cost and performance implications of a RAG architecture for many use cases.
1. Why focus on Swifts as opposed to any other species in decline? They state that they are "iconic", so maybe that's the answer? Are they more "iconic" than any other specifies in Scotland?
2. Why are these bricks the best solution? Why not take that money that would be spent on bricks and instead preserve land, or just build them dedicated houses elsewhere?
3. Why does this need to be done via government mandate versus voluntarily asking people to build Swift housing in existing buildings or land?
I'm worried that this is a government policy with great intentions that will result in economic costs with unmeasured benefits and bureaucratic bloat. Hopefully I am proven wrong!