HN user

siriniok

113 karma

entrepreneur, software product engineer, generalist, transhumanist, helping developers grow at mtdv.io, #ruby #lisp #AI #science

Posts15
Comments35
View on HN

Status UPD:

I'm sorry for this experience, but we just can't add all locations right now :(

We were adding the locations to the map manually. After the app went viral, we got over 600 new places over 24 hours, so we can't handle it this way anymore. We are working on automating this process, and as soon as we'll figure it out, we are going to add all the locations, including yours, to the map.

Thank you for your contribution! It means a lot to us. Please, don't worry, we will add your submissions as soon as we can.

I'm sorry for this, we just can't add all locations right now :(

We were adding the locations to the map manually. After the app went viral, we got over 600 new places over 24 hours, so we can't handle it this way anymore. We are working on automating this process, and as soon as we will figure it out, we are going to add all the locations, including yours, to the map.

Thank you for your contribution! It means a lot to us. Please, don't worry, we will add your submission as soon as we can.

It's ok to feel like that, totally. And it's not easy to become your own boss, you have to learn how to manage yourself and that will take time. You also need to change your expectations for rewards: you are no longer working for salary, you are working for profit now, which means that you have a different feedback loop now. As soon as you get used to this new feedback loop, you will be more comfortable with you new role.

I'd recommend to get some confidence with Ruby before moving to Rails. It's better to spend 2-3 months learning Ruby and then focus on learning Rails, than struggle with both right from the start.

When people say that you can learn only basics of Ruby in few days and then move to Rails, they are right, you can, but this way you will learn two things in parallel, and it's pretty exhausting. So this doubtfully will save you any time.

Transforming implicit mental models into explicit is the most important step in learning for me. And it's only possible to understand whether I had done it right when I try to apply them in practice.

My favorite limiting belief is that about our limited willpower. While it's kinda true, studies show that people who believe that willpower is unlimited perform better, than those people who believe in limited willpower. IMO, it's a perfect demonstration of how the limiting beliefs work.

I totally understand your frustration. I was happy to met a wonderful mentor in the early days of my career. I was expecting to hear mainly technical stuff, but instead he was talking about soft skills, empathy, lifestyle, communications and so on. Only few months later I've realized how actually important was all that stuff for my career.

So that's what I would recommend to you: find a good mentor who looks beyond hard skills. It's hard, but look for a fellow who is happy about their career :D.

Another thing I would highly recommend is to find an accountability partner or join a mastermind group. Those can be your peers who are interested in meeting from time to time and talk about career-related topics. You can discuss your goals and progress, work-related problems, and keep each other accountable. That helps a lot in actually making progress more than anything else.

Hope this is helpful. If you want to talk more about all these things, I'm always open to chat.

Yes, such tools exist, and they are really hard to use usually. It's hard to copy, hard to refactor, hard to compose, etc., and clicking by mouse is really slow.

I don't say that a good UX couldn't exist for such thing, but we already have that good UX in a form of text. Really. Think of it.

Interesting concept. We could probably talk about "engineering maturity" with a pretty similar list of characteristic when applied to programming.

Hi fellows!

I curate a small online community about career for people in tech. Every month we collect and produce a lot of useful materials on career, engineering, learning, lifestyle, business, and everything else related to building a successful career in tech. And as I said, the community is small, but I believe that such materials are worth sharing with a wider audience. So I decided to manually compile a free newsletter every two weeks and feature the most useful findings.

Hope you'll enjoy it! I will appreciate your feedback: what do you want to see on the digest, how often, and how to make it more helpful for you?