It feels like it has become trendy for everyone to worry about everything rather than to look to the future, be creative, and explore all of the amazing uses and problems that we can start tackling.
411 karma · joined December 25, 2015
It feels like it has become trendy for everyone to worry about everything rather than to look to the future, be creative, and explore all of the amazing uses and problems that we can start tackling.
- Cooking via YouTube (Food Wishes w/ Chef John, and Kenji Lopez Alt's channel)
- ML model architectures (AI Coffee Break, and Yannic Kilcher's channels)
- Exploring different ways of thinking about and responses to the question: What is the meaning of life? (I don't think there is one, so it's more about how we derive one for ourselves.)
As for attributing burnout as the core issue here, I would strongly disagree with this idea. When teaching undergrads I noticed immediately that a good portion of each student cohort was basically there because they were interested in making money in the future rather than exploring the ideas of computer science. They were no doubt going to get frustrated or bored and move into management or some other profession rather than continue to expand as an engineer. This is totally fine, and they are probably richer for having learned what they did, but I don't know why we can't just see this and appreciate it for what it is rather than portraying it as the drama of burnout.
Maybe we need to find ways to value creation far more than consumption. Missing new and cool ideas is peanuts in comparison to creating something from nothing, whether that be art, technology, or friendship.
Imagine you are working at a games company trying to hire a contractor to help with 3D audio programming. The ideal candidate is probably going to have a portfolio that includes 3D audio programming, or at least audio and DSP experience.
Personally, I'd focus on building valuable expertise in a community that includes the kinds of people and businesses for whom you would want to work. There is always demand for skilled engineers who deliver.
There’s a poetry in the merging of two new-age religions stemming from different communities. Unfortunately I’m an atheist, and so are most of us here I’d imagine.
I think part of what is exciting and intriguing in your article is that it paints a picture of what agriculture could look like. Instead of just feeling a sense of dread about how our society is ruining everything, many of us are technological optimists with a core belief that science and engineering can help light a way to a better future. Who doesn't like reading articles that reinforce their existing beliefs? ;-)
I've scoured YouTube and other sources for regenerative ag content over the last few years, and what I crave are more specifics and details of business models, scientific analysis, etc. It would be fascinating to actually see the books for a couple of different farms, conventional vs organic vs regenerative. How much money is spent on chemicals vs labor vs seed, etc.? What does insurance cost, and how much risk is there? Does regenerative ag with higher soil carbon lower this risk? (Maybe there is a smart regenerative only insurance play here?) Many of us would probably love to work on autonomous tractors, computer vision to spot problems, etc., etc., so learning about the key levers and problems underlying this industry would be incredibly thought provoking. While reading your article my head went to: why can't those electric fences both monitor the cattle and move themselves around? Could you attach water or compost to the cows themselves to have them help distribute useful inputs? There is an incredible amount of food waste, yard trimming waste, and other carbon rich waste streams generated by society. Why aren't we spreading that on these farms? Instead of tilling the top inch or two, couldn't we be planting the seeds in a new layer of added material? I guess this would require moving a lot of mass, but maybe if it's an autonomous supply chain it could be constantly bringing beneficial waste streams to farmers? It seems like each crop is likely to take some nutrients and provide others. Could you not auto-sample a farm and then automically determine the optimal crop mix which will most benefit the soil? If you have market data you could also connect this with current market prices. Last, if all you did was grow optimal cover crops for a few years could you dramatically improve a farm? Should we pay farmers to give the land a break and only grow beneficial crops so they can come back in N years as an organic, regenerative operation?
My wife and I have started trying to order all of our meats (fish, pork, beef, chicken) from sustainable operations, and it's actually quite hard to know who to go to. When we do finally find one that seems compelling, they are often sold out. Is anyone creating a centralized marketplace for the output from regenerative farms? I have a feeling we aren't the only ones who want to support these operations.
Thanks for a thought provoking article!
Sorry, but this is no Clojure. Instead of a proper comment syntax you define a dummy variable to a string? Ghetto.
Instead I would start jamming on a whiteboard or in a notebook. Think about the problem you are tackling: what are the inputs, what are the outputs, what are the key functions, and what data structures and algorithms might be important? How about the team? Is it just you, or are you working with other people? What are your experiences, interests and passions? What's the timeline? Spend some time exploring libraries, reading paper and blog posts to inform yourself of the space. Maybe read some open source libraries. Don't go nuts, but scan around to soak up some good ideas and build a mental model of the space. This all helps put some parameters around the situation and give you some confidence that you are making informed decisions. Now you can think about the MVP, key interfaces, etc, and you might find that you can do some quick and dirty components for 80% of the project while really focusing on the heart of the challenge in that last 20%.
Often times if you define good interfaces you can swap early hacks and experiments out for something fancier (faster, more scalable, etc) later on, so then you don't need to worry as much about making optimal decisions. For example, you might use some distributed key value store or message bus in the end system, but to get the ball rolling you can just spin up a Redis instance during development, or even just write a couple functions that fake it in-memory or using JSON on disk for starters.
Now you can think about what you want to learn in this project. What's going to be fun and interesting about it? Do you want to dig into some new algorithms, a different language, a machine learning model? I like to use my curiosity as a major motivation to differentiate from other solutions and push through what could otherwise be boring aspects of the project. Say you need a service that just manages logins and sends back some tokens. That can be done in a million ways, and it is likely to get swapped out down the line anyways as you scale or whatever. So make it interesting, pick a new library or language and go nuts. This of course needs to be balanced with making sure you can accomplish the task in a reasonable amount of time, but this kind of learning is empowering and it will make you a more capable engineer. Now 20 years into my career I can program in 10+ languages on embedded micro-controllers or virtual cloud clusters, and picking up a new language or framework isn't daunting at all.
Have fun doing it, and you'll get better faster than everyone who is picking the boring framework in their same old language to solve it the way that the blogs are telling them to and then frantically searching stackoverflow because half way into the project they discover that their square problem doesn't perfectly fit into the framework's glorious round, ahem, hole. That's not engineering or craftsmanship. That's nervous fanboy frenzy that is the opposite of empowering.
Everyone has to find their own explore vs exploit trade-off, and we need people whose experience is narrow and deep as well as others who have learned far and wide. Choose what kind of person you want to be and make it happen.