stocktech

Beautiful site, but the UX needs work.

If you're more senior, the biggest impacts will come from networking. Figure out where you want your career/life to go, then work towards that. Want to be CTO? Want to work at XYZ tech co? Want to start a business? Doesn't matter, make some friends and start networking.

I'm a big advocate for leveraging the energy of your youth, but make sure you're spending it wisely. There's more to life than working.

Nonviolent Communication.

I think it was linked on HN where it caught my attention. This book teaches a great way to communicate, but for me, it has also helped me think about my feelings and how I can communicate those feelings better. I feel more in touch with my feelings and more empathetic as a direct result from following what the book is teaching.

On the communication side, it has helped me put more structure around tough conversations, personally and professionally. It has helped me understand others more and vice versa. It's also helped me see toxic traits in others. Such as people who aren't interested in understanding or people who struggle to understand their own emotions.

What? Can you expand on this? It sounds like a server rendering issue which has nothing to do with the framework itself.

Personally, I feel Ember is best suited for the enterprise world. It's a slower moving framework focused on backwards compatibility that remains relatively similar over the years. I feel slightly insulated from the rapid changes in the front end world which allows me and my team the ability to focus on the business. Of course, I push my team to understand what's going on outside of Ember. I've definitely taken things away from React and Redux.

But having to maintain dozens of apps (and growing), I couldn't imagine the technical debt we'd have if we chose a different framework. Our repos would be scattered with the latest and hottest fad and changing standards.

> a few projects even prompted companies to reach out to me first

This raises a flag for me. If they're reaching out, they must be convinced of your technical ability.

I understand you're frustrated and I don't want to read too much into your post. However, how you're talking about your relationships, being blunt, working at desperate places, it makes me think your interviewing skills need work. A single interview faux pas can remove you from consideration. Being negative or highlighting your faults puts you in a bad light. It's entirely possible to remain positive, but still be honest about your experience.

I might have phrased "acknowledging their deficiencies" too literally. To give you an example, I once interviewed someone who couldn't even explain basic terminology. Their github was just OK. Yet, they knew about the company. They spoke intelligently about their projects and seemed excited about what the team does. They knew the technical portion didn't go great and were able to 1) convince me they could learn and 2) positively related their existing experience and prior ability to learn to the requirements of the position. Great junior.

For the pay cut, there's too many factors to assume, but in this situation, I'm not paying senior rates for lessor work. You also have no leverage so you'd be at wherever I value the position and my belief in your ability. Again, if you can prove yourself after hiring, I'd bring your pay up to an appropriate place.

There's also a category of people who prefer work where they can come in, do their thing, and leave at the end of the day. They're not looking for more responsibility and there's nothing wrong with that, but they too are left with a skills gap.

From a hiring manager perspective, I wouldn't say that it's game over, however. I've had plenty of devs get to the interview stage that have an experience vs skill mismatch, maybe 5 years instead of 10, but I consider them for maintenance work or our QA team that's less code heavy. For someone in this position, those roles might be a better fit or the candidate would have a place to prove themselves. Of course, you'd have to take a pay cut and take a mid-level or possibly a junior position. If I offered someone with 5 years of experience a junior position, it would probably be communicated that a bump could happen in 6 months to a mid-level role. A trial period of sorts.

The key is to be upfront. I've had devs try to bullshit their experience into something it obviously wasn't and it never works. I'd be blown away if a candidate came in, acknowledged their deficiencies, and said "I'm doing XYZ to figure it out and I really just need a chance to prove myself". Don't underestimate the importance of attitude and industry experience.

> What companies are most willing to give the "one year experience over many years" worker a fighting chance and get them up to speed?

Something about this question rubs me the wrong way. If you've fallen into the 1x10 pattern, no company is responsible for giving you a fighting chance. The burden is now on you. The advice I can give you is the same as any other dev, but probably more important, find a way to show me your skills and that you're working on improving. Open source work, code tests, side projects, anything and be able to discuss them.

The 1x10 devs that I already have are the ones who reject the opportunities given to them, who don't want extra responsibilities, and who aren't interested in learning new things. You need to give me confidence that that isn't you.

Otherwise, I haven't paid attention to the core,data, and cli release schedules.

I think there's a point where you're experienced enough for it not to be a trap. Concepts, patterns, and structures repeat and once you've started to accumulate enough experience, learning a new language or framework is just implementing things you've seen elsewhere. Then it becomes a choice of productivity and what does the project benefit from most.

If you're not there in your career yet, focus on learning something new. I promise it'll be a level up one way or another. For your project, it might delay it a little, but it'll help your resume and round you out as a developer.

Ember has been a big win for us. Upgrading old apps is a breeze. Every app has a consistent structure and the conventions make it easy for developers to move between projects. We don't need to worry about the individual pieces - routing, data, etc - we trust the core devs so that we only worry about business logic. We're experimenting with Ember Engines right now and I'm not sure how we'd replicate it if we were using React or Angular. All in all, I think it has made us incredibly productive.

Outside of the code, the Ember team's communication skills are top notch. I feel like every time I tell my team that "XYZ is coming down the pipe", there's a clear plan of attack and any impact is minimal. In the last 3 years, I've never had to tell my boss that development will be paused to focus on a refactor/upgrade/maintenance.

The biggest downside is in hiring, unfortunately. I don't look for Ember experience, but I have had to adjust my expectations when it comes to the learning curve.

For a self driving taxi, I don't understand the need for a cost focused option.

When this anonymity slightly fades, the idea of a meritocracy fades with it. I know I could make more money working on the west coast. I know the work I'm doing isn't sexy. But my project is fucking interesting and on HN that's all that matters.

Even then, data analyst roles are entry level at my company. Not saying that's how it is everywhere, but you'll be taking a pay cut without experience. My recommendation would be to look for business intelligence positions. It varies what the role actually is, but you're bound to find a few BI developer positions that value web development experience. Regardless, the worst case scenario is that it's tangent to data analyst work and best case it overlaps. With the nano degree and your experience, I'd imagine you could see a raise even.

I do think there's room for new tools tho, but by definition, they're on the cutting edge and not especially visible if you're not looking. Things like stream processing are already incredibly useful and only getting better. Machine learning could be in this list too. It might not be a 1000% improvement like caching, but that's part of a maturing industry.

I think this is healthier than a separate plan for each department as then you'll get people questioning the plan and their roles, value, etc.