lobati

There doesn't appear to be good evidence that this is better for RSI. I found one study that shows greater shoulder and back strain when doing the hover hands approach. It might make more sense for piano since you need more mobility up and down the keyboard, but for typing your hands don't need to move nearly as much, so resting should be just fine. The do suggest some sort of support under your wrists, though.

https://pubmed.ncbi.nlm.nih.gov/15145291/

I'm building a flash card learning tool. I was frustrated with the slowness and complexity of other solutions. Animations and loaders with tools like Duolingo, and unnecessary extra steps to move onto the next card in tools like Anki. If you give it a try I'd love to hear your feedback.

https://flash.boon.gl

I actually have a success story. A woman I started dating was the CTO of an early stage startup. I gradually started helping her with some coding on the side and it grew to the point where I left my day job and went on full time at her company. I've been working at the company for more than a decade at this point. It's gone from just the 3 of us, including her cofounder, to a 70+ person company. We're married now with 2 kids.

There was a good amount of conflict between us during the early stages of the company, so it's important that your relationship is sturdy if you are going to put yourself in that sort of situation. Now things are running pretty smoothly, so we actually don't talk as much about the company in off hours.

We've interviewed and hired a number of friends as well, mostly with good outcomes. We had to fire one friend, unfortunately, and another relationship soured as a result of how the interview process went. But several others are still with the company, and a couple have come and gone onto other things.

One thing to note, though, is that for the friends we've hired, they often morph into more professional relationships. Now that the company is settling down a bit, we're trying to rekindle some of the friendship piece.

A really simple tip that has worked wonders for me:

Don't eat until you're full, eat until you're no longer hungry.

I've lost 25 pounds so far with this in mind. It requires reflecting while you're eating and realizing that while you may want to eat more, you may not actually be hungry anymore. While I may want to stuff myself and eat 4 slices of pizza, I'm generally no longer hungry after a single slice. In the morning, half an egg and a couple of sausage links is enough, or a few bites of oatmeal.

That's all well and good, but then you might be hungry in an hour. This actually hasn't been a huge issue for me, but if I am hungry, I'll generally eat a handful of nuts or a spoonful of peanut butter.

I'll typically eat a bigger dinner, and let myself cut loose a bit on the weekend when we order delivery.

Haha, me too.

Did you read the section I'm referring to? Pay particular attention to the word "intrusion". Quoting:

The Registrant grants an irrevocable licence to NICTL and it’s agents a right to access, monitor and scan any content published publicly including where such processes may involve an intrusion or cause a potential modification of data, providing such scanning is for the purpose of identifying internet security vulnerabilities or the presence of malicious software or content capable of causing harm or disruption to the systems of other Internet users.

We're actually not counting you towards the total. Here's hoping your assessment goes well, though.

I think a slight clarification would be in order here: motivation and attitude are huge weighting factors in our selection process, but another important part is that we feel you can learn enough in ten weeks to be able to get a job. This doesn't require any programming skill, and the bulk of our students have little to none, but we definitely look for problem solving ability. Anyone can learn to code, everyone should. Just not everybody can learn it in ten weeks. As we nail down the curriculum and improve our teaching we'll probably take on more challenging students, and move closer to the goal of assessing students based on attitude alone.

You seem to be operating on the assumption that the hiring companies are just "trusting" that we put out good students, when in fact they each have their own rigorous interview processes designed to weed out people who have just read the books from those who actually have the ability to think and solve ambiguous or complicated problems, as well as who have the curiosity and passion to continue their education. At my previous jobs I interviewed quite a few potential hires and didn't find a great deal of correlation between having a degree in CS and their fitness for the position. In fact, those who taught themselves tended to need a lot less ramp-up and hand holding than hires straight out of undergrad--the knowledge sticks a lot better when applied to real world projects.

At DBC we're not just a bunch of opportunists trying to make a quick buck. We're people with advanced degrees in CS and educators who believe that education can be done better, at least when it comes to engineering, and we aim to prove it. We choose students who are eager to make a career switch and who have the right attitude for growth. Zed's right--these people would be successful on their own, but we're giving them a leg up by helping them to make it happen in a few weeks instead of a few years. We're not just training a bunch of script monkeys. We're ramping passionate people up on the tools commonly used in a modern web-based company, as well as giving them the mental resources to solve messy problems and to continue their education once they leave. Not to mention a strong sense of the community they are joining and where they can contribute. They won't be experts, by any means, but they'll be ready to carry their weight as entry-level engineers.