There's a service in Indianapolis that does exactly that! https://www.clustertruck.com/
They actually license the recipes from local well known restaurants, and then cook them in their own kitchen and deliver them.
1,115 karma · joined March 13, 2009
They actually license the recipes from local well known restaurants, and then cook them in their own kitchen and deliver them.
- Increase fiber intake - especially vegetables, beans, lentils, and complex grains like oatmeal
- Avoid added sugar and processed carbs
- Avoid excess caffeine, which has a diuretic effect and can increase anxiety
Easy to say - hard to do :)
Short version: become a "visible expert" in your field (blog posts, ebook, meetup talks), and then connect with people who might need your service.
Table saw kickback experiments https://www.youtube.com/watch?v=xFkHmgRIkOI
Effects of table saw misalignment, and kickback https://www.youtube.com/watch?v=Fbca0Km8Q5E
It was just a weekend project, so I gave myself Saturday to see what I could come up with, and this was the result.
This was the inspiration: https://twitter.com/patio11/status/1086625920989818880
- Become a "visible expert" in your space. By that I mean give talks at meetups, publish a blog about the technologies you want to work with, etc.
- One of the best things I did was to write an ebook about React. Even a short ebook can give you instant credibility (even if no one ever reads it!) - the fact that you wrote it says a lot about your commitment level.
- Be open minded about what kinds of contracts you will get. Generally, freelancers fall into a couple of different buckets: full time staff augmentation, 1/2 time or less ongoing help, one off project help.
I've written up more tips here: https://www.breakintoconsulting.com/ - and feel free to email me if you want more specific feedback or info! (email in profile)
He asked me how it worked, and I used that to talk about some core programming concepts, including showing him some code. I wouldn't say he "learned" programming from that experience at all - but now he knows what code is, and sort of how programs are made, and he knows that you can make cool stuff like robots :)
So I would say: find something they are really interested in (maybe that's Minecraft, or robots, or animation, etc) - and use that as a jumping off point to introduce the concepts to them.
For your flying example, that might mean to sit and think about just packing for a trip. How does that make you feel?
Then think about driving to the airport. How does that feel?
Then think about boarding the airplane.
Then think about flying calmly.
Finally, think about really rough turbulence.
The idea is to think about each step several times (over many weeks/months) until you are progressively more and more comfortable with the entire process. Often, anxiety about a specific event (turbulent flying) will start well before you experience the turbulence - so by progressively visualizing each step in the process, your mind will begin to better control your body over the entire experience.
This process works for all types of fears: spiders, bridges, going underwater, etc.
However! I’m not a professional - so if it is really bad, then I would recommend going to a therapist - even for just a few sessions - and they can better walk you through the process. Search for “CBT in [your area]” if you don’t know where to start.
Also - if you can’t get over it with just mental exercises, and you really need to fly somewhere - a doctor can prescribe medication that will relax you for the flight (though there are potential side effects - including addiction - so talk that over with your doctor).
It's easier than you might expect - the books are all short picture books at that age, so it's easy to just sit and read 5 at a time. Also if you read the same book 40 times, then it counts 40 times - so it's not 1,000 unique books (although we probably have read 1,000 unique books by now too). We also read 2 or 3 books every night before bedtime, so that adds up quickly.
Our library doesn't have any checkout limit, so we just get 30 at a time and go back once every week or two.
My basic advice is: become a visible expert in the space by starting a blog, posting articles, and go to meetups and speak. Then, start with your network (old jobs and coworkers) to look for work, and expand out from there.
The good news is there is a ton of work for javascript developers right now, so that’s one advantage you have.
Spoiler alert: all of the videos can be summed up by: "eat a whole food, plant based diet".
As a general note though - nutrition as a science is _hard_, because everyone responds slightly differently to the same foods in unexpected ways, and it's really hard to do double blind, controlled trials over a long period of time (they cost too much, or are just unfeasible). So I think the best approach is to read/watch a lot of different content from different sources, in order to gain a wide understanding of the current research.
Hiring people and managing an agency will feel very different than doing consulting yourself. For me, it meant I now had to worry about getting enough work for two people, and managing cash flow so that I could actually make payroll all the time.
For example: before, if I didn't have work then I could just stop paying myself for awhile, and then make up for it by paying myself more when the contracts started coming in again. With an employee though, I had a fixed burn rate (since I couldn't just stop paying him), so I had to manage my cash reserves a lot better. It's a good practice to have anyway, but it took some getting used to.
So my recommendation would be to start small - and don't start by hiring someone full time right away. Instead, start by subcontracting some of your work out to someone else. How does that feel? Can you get enough work to keep two people busy? Can you manage your cash flow so that you can pay people on time?
I mostly chose it because it was free (despite the 10k message limit - which I don't see us hitting anytime soon), and people already know how to use it. I know about the limitations and problems with it - but it was basically the easiest thing to get started.
It's a good read if you're trying to learn the fundamentals.
I guess you're right about the three vs one though - I should make that more clear. I used three because it's the number I give in the "First Client Checklist": https://www.breakintoconsulting.com/first-client-checklist
Basically - I say that if you want to be an independent consultant, you should start a blog and write at least three posts as a way of demonstrating that you're an expert in that area.
https://www.breakintoconsulting.com/blog/2018/4/4/tips-for-w...
Basically - I think the point of a blog (at the beginning) is not really to be lead gen for consulting gigs. Instead, it's a place to plant your flag on the internet and say "This is what I'm an expert in".
Eventually, that may lead to consulting leads - but at least at the start, it's really just a way to establish that you know what you're talking about. Either way - if you're thinking about doing consulting, I would highly recommend it.
They can generate sketch files from react components (https://github.com/airbnb/react-sketchapp) but not the other way around.
The painting with code demo (https://airbnb.design/painting-with-code/) was a step towards that though, and I think it's really interesting as well.
It takes designs for mobile apps (from Sketch files), and tries to convert those into React Native components. It's still early days, but it's a promising start.
It's cool because if I can get it working fully, it can replace a large chunk of my consulting projects (taking designs and converting them to the initial code)
(I'll admit that I don't fully understand it yet), but I think the major thing that capsules tries to fix is that a CNN only looks at a small window of the image at a time. Since the capsules aggregate more information, it can learn more general features.
Also, he notes that the paper was done on the MNIST data set (small images), and may not generalize to larger images, but the initial results are promising.
There have been a lot of changes since 2015 - and the overall experience has gotten quite a bit better. There are many more modules available for both platforms (in 2015 you probably found a lot of modules only supported iOS and not Android) - and in general the whole ecosystem is more stable.
That said: not everything is perfect. React Native moves quickly, so there are sometimes frustrating bugs (especially in new releases) that can take a bit of time to resolve. Also, it's not a great fit for every type of app. 3D games are an obvious example of when you'd want to go native (or use unity).
However, after having done native iOS development and react native development, I can say that react native is still faster (development speed). In practice I find that I can reuse 95% of the code between iOS and Android, so it's been a great win for the teams I've been on.
For example: if you have a list of 1,000 things, you might put them in a scroll view first; but that will lead to very bad loading and scrolling performance (it will with straight native code as well). Instead, you should use FlatList (https://facebook.github.io/react-native/docs/flatlist.html) which is built to be performant on long lists (by reusing components, etc).
There are also a few additional considerations that you don't have when writing pure native code. One example is that if you send a lot of data (like a huge image) over the JavaScript bridge, then that can really slow down app performance. There are ways to get around that however, but it can be easy to accidentally do things like that which hurt performance (and those types of slowdowns might be confusing and difficult to track down).
So yeah, it's not perfect - but it's the best cross platform development tool I've used, and most potential issues have workarounds (once you learn what's causing the issue).