evm9

I think it's a possibility if targeting earlier stage companies or startups.

Larger companies are unlikely to make a drastic change in process to suit one or a few candidates, especially considering this idea is something risky from a legal & social perspective.

  Location: Calabasas, CA
  Remote: Yes
  Willing to relocate: With a good relocation package, willing to relocate to DTLA/Santa Monica
  Technologies: React, Vue, Redux, Ruby, Rails, Postgres
  Résumé/CV: E-mail
  GitHub: github.com/matisoffn
  Email: noah at matisoff dot me

Would use if had anonymity. If I'm going to prank my friends I don't want them knowing it's me instantaneously.

Of the two (money coming in and money coming out), you can only restrict money going out so much.

You have your basic expenses you need to live (food, shelter, water), which cost most people at least tens of thousands per year.

If you live miserably only allowing money out to expense those needs, you're still only saving tens of thousands.

You have a lot more ability to increase money coming in than money going out.

I think this is the point OP's father was trying to make. Don't get stuck in a loop of allowing your employer to pay you $xx,xxx (or $1xx,xxx) for decades and restrict yourself for your whole life just to retire old and live an average lifestyle. Take control of your life and control your success.

Maybe that works for you, but you'll never be strong/look strong weight training weekly. If you're "overtraining" from one weight training session per week, there's something very wrong. The average human only takes 48-72 hours to fully recover for most muscle groups in the body.

It's also been proven that HIIT is much more beneficial for your system than LISS.

It might "seem" more beneficial to you, but likely is not more beneficial than the alternatives. However, something is definitely better than nothing, and do what works for you and makes you happy.

SEEKING WORK - Remote, based out of Los Angeles, CA.

Experienced in building software for the payments, insurance, and financial industries.

Full-Stack Developer experienced in Ruby, Rails, Postgres, Redis, Node.js, React.js, React Native, and Angular.js.

GitHub: https://github.com/matisoffn

E-mail: noah (at) matisoff.me

WOW. This infuriates me.

Darn, sounds like a cool opportunity but I'm down in LA right now. Best of luck.

I've seen some people here insist that they want their work station and/or laptop ready to go. If I were in the position of hiring an engineer, and made a hire, I would ask said engineer what they would prefer. Having everything setup or letting them unbox and setup, or maybe a combination of both.

Other things not specific to work environment should be ready to go. Their e-mail account, phone (if applicable), or any other virtual or physical materials used on a frequent basis.

As others have suggested, prefer something like a 75/25 social/engineering split for the first day. Introduction to team members and others, company processes, goals, HR stuff, go to lunch, etc.

It's tough to weed out the bad resources on the internet, but you've come to a good place to find the good resources that are available (free or paid).

You'll get out of it how much you put into it. If you spend countless hours learning and then building projects you will learn new things very quickly. Don't get caught watching tons of videos & screencasts while not building anything.

You can read 1,000 books about surfing but when you go to surf you'll fail repeatedly. The same goes with building software. Read code and then write code 5x as much.

The courses are good for beginners, but to take it to the next level you need to build a sizable app and get it to production. There are things you'll learn from putting a project to production that you wouldn't learn otherwise. Remember: software is built for users & actual people, not just machines.

Wow, so cool.

There are many, many reasons that a startup may have failed (or is failing) and there still may be a product-market fit.

Some products & markets require you to go out and get users more than others, and they may not have done that.

It's on a case by case basis, just be sure to get validation for your project. Make sure that you're making something people actually want, and if they want it, how much they will pay for it. Can't stress it enough how important it is to go out and talk to potential customers, ideally hundreds, and figure out if they'll pay and tell their friends about it.

Marketing is important -- having a good landing/marketing page, getting press, etc. But at the end of the day the product is what will create retention. Looks get the first date, but your personality is what will get you the 8th date.

That would be an interesting application. What could the range be?

I like this approach, it's the most careful one.

Though if you truly know that you are valuable to your company and they are going to pay you what you're worth when you make the ask, no need to even get another offer. If it's such a good market you should have no problem finding another gig.

I'm in SoCal doing Ruby, Rails, JavaScript stuff and I was underpaid for the first 1.5 years at a new gig. Since I was confident I could get another gig paying 20-40% more with ease, I didn't bother getting an offer first, when I made the decision, I just went in the next day and took care of business.

Told my manager I have an offer on the table for FIFTY PERCENT more than what I was currently earning (no such offer existed), they matched it (including other perks), and then I was paid 1.5x more. Been here for another year since then, no problems.

YMMV, make the best decision based on your situation. This risk may not be worth it, but it sounds like you're in good standing with your company and provide them good value.

It's already over, they're just trying to reconcile.

You don't need to know of changes unless the user is on that page.

You can use websockets to broadcast/listen for changed data and updated the DOM accordingly (if you're on the web).

My biggest regret about learning programming is that I tend to approach things in the real world from an engineering perspective, which isn't always best for a given situation.

I try to avoid it and over time I've done a better job of approaching things dynamically.

They certainly could have.

Agreed. I feel like the struggling when actually implementing the language for a real project/product is normal.

I think this is because programming languages are built with performance, readability, and writability in mind. I've yet to come across a programming language that was specifically built to make it easy to use to build a software product (plenty of frameworks though, ex Rails).

Thanks, posted over there.

Location: Los Angeles, US. Potentially remote

Product: A product in the payments space, contact to hear more

Stage: Was an idea two weeks ago, now it's in development

Expertise: Back-end engineer (Ruby, Rails, Node.js, Postgres, MySQL, Redis)

Need: Excellent front-end engineer/developer, JavaScript, ES6, and any popular front-end MVVM/web app framework like Angular, React, Vue, Ember, etc.

Split: 60/40. I'm the only guy on the team, it's a brand new project.

Send an e-mail to "noiro@dispostable.com" and I'll respond from my personal e-mail.

1. Being able to effectively communicate technical topics using English is challenging. Technical writing is a talent.

2. It helps me communicate better professionally, whether verbally or written.

3. It's nice to share knowledge when you learn something new, especially something you think can help many other developers.

4. It's another thing to show off and market to potential employers.

5. For me, writing things out makes everything more clear in my head, and hopefully the reader's as well.

6. It holds me accountable to continue learning new things. I force myself to write 3 technical blog posts per week, and I can't do that if I'm not learning new things.

From my experience, paying the premium to get on GitHub, StackOverflow, and any other major job post site as well as paying mid to upper six figures will always bring in good candidates.

Also offering a killer relocation package to candidates that aren't located near you can help.

If you value your side projects and they aren't "shit no one needs & terrible ideas" then don't work on a company issued machine.

I've never heard any term except dyno (or dynamometer), but I much prefer those terms simply because it's more apparent to someone that doesn't have an understanding of engine & car testing.

I'm a fan of names that give insight into what the thing/product/service/company actually does.

In the automotive industry, we call them dynamometers. Though you'll never hear anyone say that, we just call them dynos.