wrestlerman

9 ms·

61.
by wrestlerman 8y ago
Hmm, I think you are right. I was rather answering the questions in the description not in the title, my bad.
62.
by wrestlerman 8y ago
What exactly does terrible dev skills mean? What's wrong with them?
63.
by wrestlerman 8y ago
I am surprised no one mentioned manager roles. People don't change that much I guess. We know more about our behaviors, that's right, but experience with working with people is something that will be always relevant in my opinion.
64.
by wrestlerman 8y ago
I agree with it a lot. I quit social media pretty fast when I was just too busy to use it and it was only distracting me.
65.
by wrestlerman 8y ago
That's an interesting point of view. I don't know an answer to this question, because I don't have access to any data on this matter. But what I've noticed is that with every "technology advance" there is a new
66.
by wrestlerman 8y ago
You are right.
67.
by wrestlerman 8y ago
Hmm, why not just stick to being an indiehacker then? Or stick to being a freelancer? To be honest, I am curious myself...
68.
by wrestlerman 8y ago
I do think that code changes take more than 5 minutes, why? As a person, who pushed the code: 1. I have to read the comments 2. Decide if they are right/it's worth a hassle 3. Sometimes you have to reach out to the author of the c
69.
by wrestlerman 8y ago
I don't think it's wrong to get excited about new tech. But from what I have observed it's mostly that one dev that pushes for new stuff and after they get sick/leave someone else has to take care of it and many times it
70.
by wrestlerman 8y ago
A lot of things, my experience is based on working in startups: 1. Suggesting silly changes in CR - instead of A you could have used B. So what? I used A, let's keep it that way, time is money. 2. Long discussions in CR 3. Too much thi
71.
by wrestlerman 8y ago
Not enough information. Please provide more information... (Blinking cursor)
72.
by wrestlerman 8y ago
Tooling, that means? I haven't had an opportunity to work on a big/very-big JS project yet. But from experience based on working on small-medium size JS project, I guess console.log() and refresh is just enough. After thinking abo
73.
by wrestlerman 8y ago
I am also a Ruby dev. Haven't used TypeScript in a big project yet, just played with it, but I'd say it's gonna be a standard for frontend dev soon. Why? Writing types isn't that time-consuming... Types will tell you ver
74.
by wrestlerman 8y ago
Don't want to be that guy, but imo one week is not enough to even "learn" Elixir. To be honest it depends on your previous experience, of course. But the problems is, that there a lot of books, but there are not that much cod
75.
by wrestlerman 8y ago
Not OP, but I've been interested in both technologies for a while. Elixir with Phoenix feels like modern RoR, so it's probably best suited for startups that want to build their products fast and want to scale easily and cheaper. I
76.
by wrestlerman 8y ago
They pay based on local rates . For me, this is a big no. I don't think they are a company worth changing your stack for. But going back to your question, this is a hard one... Unfortunately, I guess most companies look for experience
77.
by wrestlerman 8y ago
I think it's because Vue is opinioned, just like Rails, therefore dev's happiness(?)&productivity is one of the main goals of these frameworks. In case of React, there are a lot of libs you can choose from, I'd probably u
78.
by wrestlerman 8y ago
Currently finishing my retrospective slack bot, it's my first product, so I am pretty excited to see what people say about it. Also working on some startup in the cybersecurity industry. The vision we have is really cool, there is a lo
79.
by wrestlerman 8y ago
Rails (I'm Ruby dev). I've been playing with Vue lately and like it a lot. You can have all component's code in one place -> html+js+css, so it's super fast and easy to keep adding code. Also, I like React, but someho
80.
by wrestlerman 8y ago
While I do like some programming languages more than others, I really like this attitude. After all, it's just a tool. Personally, I am that kind of person that likes to experiment with a lot of languages to have a bigger toolset. So w
81.
by wrestlerman 8y ago
I am not familiar with your situation, so the following questions you should ask her/yourself are: 1. Does she really want to learn to code, or does it come from you? 2. Can she write any code? Does she have trouble with just defenitio