arasx · HackerTrans

4 yıl öncediscuss

I am self taught, formal education in a different field. I don't know if this would answer your question perfectly but I believe whatever success I had in delivering technology came from curiosity. I remember always thinking about how things run under the hood. Always ask questions. Pseudo-prototype how I would deliver it myself. This would shed a knowledge gap in certain areas because I would not be able to plan a certain step/process. Then I'd focus on that area and learn. It all starts with a hello world.

arasx

4 yıl öncediscuss

I normally would not want to comment short "I Agree"s. But this is music in my ears.

arasx

4 yıl öncediscuss

I've actually used OP's system in way higher traffic environments and was happy to read I was not alone. Sometimes all you need are simple tools and if git pull/ssh covers your basis, what's the big deal.

How actual software delivery is done is a relative term to the systems/needs and the scale you have. You probably have not been in environments where build/deploy tools are over engineered to death, to the point where adjusting it one bit brings down the entire delivery to a halt. If you were able to set those up without such issues, kudos to you.

arasx

5 yıl öncediscuss

If you can apply the scraping to a use case and sell that use case you have a better chance at a viable business model. Examples come to my mind is; builtwith (scrape sites and publish the list of technologies they use), ahrefs (scrape sites and find outgoing/incoming links) etc.

arasx

5 yıl öncediscuss

Software engineering is one of the easiest jobs out there from an ability to track your output standpoint. I think a lot of the commenters implying "if you have 10 hours to cut down a tree, use the 9 to sharpen your ax" and using that to argue against code-line-output != productivity. Certainly in cases where you need to put a lot of thinking or research to come up with a very elegant solution in a few lines, no one can argue you have been productive. But more often than not, we work on simple CRUD or basic apps that were stretched among hours, flying under radar from one stand up to the next, like you mentioned.

It's a common problem so you are not the only one. Especially in large teams, or teams that are run by PM's who are not very savvy to open the hood and understand what had been going on. In most of the opposite cases, it's also awkward for some managers to challenge what you have produced in a day. It starts more on the foot of discovering: is there another mental block with the employee, are they having motivation issues (maybe you fall into this group), is there a training/onboarding issue? And I have seen first hand, most of the time - they give up and mediocre output continues.

Laziness/talent/ethics of it is not our place to comment for you - but it sounds like this would be a boring job to continue. Sure you can make good money and live a comfortable life, but I can't fathom if it would be fulfilling in the long run for me. Find what stirs your passion and try to apply to work. You have the luxury to do so.

arasx

5 yıl öncediscuss

call this a romanticized view, but for every tool mankind has created - there are ways to utilize it in good VS bad outcomes. I didn't really think of it as; the learning would concentrate around opposing views. Instead of "liberal views on middle east" vs "conservative views on middle east" it would be about "middle east politics" whether you are interested in the topic or not in general - if that makes sense.

I would use a tool like this. That being said, that is not always a good indicator for a broad adoption interest.

arasx

5 yıl öncediscuss

I've briefly worked on an idea that was "pandora for news" when pandora was the hot music app. The app would learn from your votes and cater news/aggregations based on your preferences every day to your news dashboard. I was in love with the idea but never pursued it. Is there something like this now?

comments