One way is to read this: How to become a Git expert – freeCodeCamp.org. There’s a lot of good pages on how to get started on git, but if you are joining a software project, you may be expected to know more than the basics. You may be required to know the kind of things that piece talks about. Of course you can ask people on your team for help, but why not get as much skill as you can first and then ask better questions? There’s always something new to learn when it comes to git and software management: learn as much as you can by yourself and increase your skill set and your value to the team.
Then this is a good page for them to go to: How I Learned How To Code Using Free Resources | Home | Bri Limitless.
There’s plenty of good links to information, and they are all free. I can vouch for a number of them, such as Codecademy and Coursera.
One problem people run into is: why should I learn to code? One obvious answer is to learn a set of skills to help them gain employment. Two other reasons I have:
- build a website to promote yourself or any future business you might have.
- automate things you do on your computer
For #1, being able to build a website is a great way to promote yourself and show yourself to the world. As for #2, that’s the main reason I still keep coding. There’s lots of information I want to process, personally and professionally, and coding is the best way to do that.
Regardless of your reason, if you want to learn to code, check out Bri Limitless’s web page.
When it comes to insurance and wearables, I think the effect of these devices will be limited. I think this because:
- I don’t believe people are consistent about using wearables. I have been using wearables and fitbits for some time. I believe most people are prone to not wearing them constantly. Inconsistent use will make it harder for insurers to guarantee you a better rate or for you to achieve one.
- You are more likely to wear it and use it when you are trying to keep in shape. If you are not, you will likely not wear it. The insurer can’t know if you are getting out of shape or just no longer wearing it. (I used to use a Nike+ device for running, and I ran consistently, but I did not use the device consistently. Many days and weeks I just didn’t feel like it.) The use of wearables is mostly an upside for you, and of limited value to the insurer.
- One reason I gave up on using wearables consistently is that they don’t give you much new information. I walk and exercise consistently and so they often give me the same information consistently. Which means I tend to not wear them often. I don’t need the fitbit to tell me I walked 10,000 steps. I know I did because my commute to and from work plus my lunchtime walk consistently gives me that.
- My fitbit scale is great for tracking my weight over time, but an insurer could also just ask me my weight, height and waistline and get a sense of my eligibility for insurance, just like how they ask if I smoke. A very low tech way to measure things. Men with a waist over 40 inches are more prone to heart disease then men with much smaller waists, regardless of what a high tech scale says. A insurer needs a limited number of data points to assess your health risks.
- I believe there is limited return for insurers to get this much data. I base this on my current life insurer. I can get life insurance from 1-6X my salary (assuming I pay the corresponding rise in premiums) without providing medical data. They only ask for medical data if I ask for more than 6X. It likely isn’t of benefit for them to process the data for lower amounts, so they proceed without it.
- Insurers are data driven, for sure, but I think they are good at picking out a limited number of good numbers to determine what to charge you for insurance. I don’t think the numbers coming back from wearable tech is all that good.
So in short, I don’t believe people or insurers will get much benefit from wearable tech. People will not get breaks on their insurance, and insurers will not be able to reduce their risk substantially with the use of wearables.
I’m a fan of mindmapping tools in general. One I’ve been using and enjoying lately is MindMup 2.
Two things I like about it:
- It’s simple to modify your mindmaps on the go. You don’t need to do much to add or modify your map.
- It’s also simple to export your mindmap into a number of different formats. If you occasionally use mindmaps or you want to start with a mindmap to generate ideas but then you want to do the majority of the work in Word or some other tool, this is a good feature.
Mindmup_2 is a good tool. Go map your thoughts.
Nope. And this piece, Machine Learning Vs. Artificial Intelligence: How Are They Different?, does a nice job of reviewing them at a non-technical level. At the end, you should see the differences.
(The image, via g2crowd.com, also shows this nicely).
- I remember what a big deal it was that Apple was going to support third party software developers. That was by no means a given: Apple could have restricted the iPhone to only their apps and a handful of third party software vendors. By being much more open, they made the iPhone so much more than it could have been if they had not.
- I believe iTunes had a big influence on this. It was a model, in a sense, for what the App Store could be. And as iTunes helped make the iPod a success, so would the App Store help make the iPhone (and the iPod Touch) a success.
- One influence iTunes had on the App Store was software pricing. Before the App Store software was either free or pricey. Suddenly the App Store came along and software was the price of a song. The few vendors that wanted to charge more could not compete with those who were fine with the low cost. The App Store changed the way people thought about what they should pay for software.
- Another effect the App Store had on software was time to market. With mobile apps, people expected updates regularly and bugs to be fixed right away. Companies that used to ship annually now were shipping weekly or daily. This had a huge effect on how software teams developed software. Everyone had to have a mobile app, and every mobile app had to keep up with the new pace. This effect rippled through companies. Software developers adopted the pace for mobile apps to other software being created and released that frequently as well.
- The App Store also improved software quality. If you released bad software, you would hear from users immediately via the ratings. There was no hiding bad apps. As well, if your app sucked, other people would come out with better apps and steal whatever market share you had. Software development teams were on tighter leashes because of the App Store.
- The App Store allowed software developers to make money in ways they could not before. You had a direct channel to consumers of software via the App Store. And lots of developers made a good amount of money as a result.
- Apps became part of our culture. Games like Angry Birds found an audience because of the App Store.
- We downloaded so many apps we lost track of them. And some of them turned out not to be good for us. Speaking of that, if you want to do a bit of spring cleaning on your apps and make sure that the ones remain are good, I recommend you read this: On the 10th anniversary of the App store, it’s time to delete most of your apps (Popular Science)