HNHacker News
TopNewBestAskShowJobs

soroso

458 karma · joined February 23, 2014

submissionscomments
soroso··on Go channels are bad
From http://go-proverbs.github.io/:

Channels orchestrate; mutexes serialize.

soroso··on Microsoft Is Acquiring London’s AI-Driven Swiftkey for $250M
Just uninstalled it.
soroso··on Ask HN: How do I evaluate my equity offer?
Be careful. Some equities have tight rules of what you can do with them, essentially rendering them worthless. What's the difference between one stock option you can't sell, can't withdraw profit or that doesn't exist in a clear piece of paper from the one that doesn't exist?
soroso··on Problems with Go's design
FUD
soroso··on Why Software Outsourcing Doesn't Work Anymore
This guy has an agenda. He himself has patented some way of distributed remote teams and wants to kill enemy ideas. Look for his weird idea of XDSD.
soroso··on Ask HN: How did you start your company alone?
I saw just on case of one founder company.

The guy was amazingly passionate and stubborn about his product (a company expert in making websites in the time CMS were not so pervasive in the market he operated on). He had this "boutique" idea of working with 10 or so customers only and not push for growth.

Of course, he did not grow and eventually his pool of customers shrank as he was being pressed by the competition of open and free CMS.

He operated in a very low cost budget: no cars, his house was both his office and home; he had freelancers filling the gaps for him (I was one of his contractors); and at a certain point he had 2 employees.

So yes, it is possible. But he was just unlucky with market sudden changes.

soroso··on Ask HN: How important is code commenting in your org? What is your org?
Cannot say about my current company, but the last one (a real estate listing agency in South America). It was very important, but there was always a huge debate of what was important to comment. One developer thought that adding docblocks was just enough. The other thought about commenting the why of code blocks etc.

So your question may sound like "How important it is to live within your own means". Everyone will agree, at some level, the living within means is important - but people will diverge on whether you just give up your goals or aiming for them anyway.

Comments as much as code are meant for human eyes. The main difference are that comments are not executed, therefore they are less likely to be updated when the reason for a piece of code changes as well. Programmers update code until it compiles and passes tests, but it doesn't follow they update comments accordingly. Nothing is more misleading than an outdated comment.

Also, you might find those who will say that if the code is self-evident, then it does not need commenting. Which is theoretically true, but usually people miscalculate the ability of later read to extract context of uncommented code.

soroso··on Ask HN: What are the consequences for a startup employee whose startup fails?
Technically it didn't fail. If you do not mind losing your vesting opportunities, just look for greener pa$ture$.
soroso··on Ask HN: My startup has failed. What comes next?
I do not know details, but it seems the biggest mistake was not failing before cash ended. I had two startups that were successes, but I had other few which were failures. The trick, back then, was to set a certain threshold in which we could call success or failure, and move on.

If you happen to have spared some cash before the actual declaration of failure, consider to take a 3 months break (I did). 3 months break does not mean not working, but actually removing from your life entirely any concerns for future plans or making another business.

It is a sort of short and strong detox, that will allow you to regroup and think better what's come next. But keep doing business... Those who felt the taste of startup never really let that go. For some reason, I can't explain, it is addictive.

soroso··on 7 days to leave Hiveage
I side with the Startup. If the customers is not a good one for them, they have the same right to kick him off as much as the customer has the right to seek for another better service provider.

And his condescending tone it pretty obvious to me, in http://s.natalian.org/2015-06-17/7days.pdf (but maybe these are just cultural differences ;])

soroso··on Semantic Versioning 2.0.0
Where's the changelog? What has changed?
soroso··on Ask HN: Boss with Steve Jobs Complex
I had similar experience, however in my case I built what my boss wanted. And he was happy. I managed this not by magic, but the beginning of my story looked strikingly similar to yours. And, of course, the project didn't fail.

So yeah, his method is not _that_ wrong. But there's a catch: in the beginning he was really interesting in pico-iterations. So not only I was doing, but every hour or so we were discussing what the screen looked like, going to the lengths of adding fake buttons that did not do anything, but helped to reason about the application.

After few years (you read it right), we no longer needed to talk a lot about what the company needed. Usually he would point to a problem to be solved, what he would like to see, and the development team managed to fill the gaps.

More recently, in another company with another boss, at a certain point she appraised the team for not really having to fill the gaps of understanding for the team: she spit a vision and we do it in our way. Every iteration she validates it, and of course ask for changes. Pretty average.

I think the real problem in your case is the attitude : public scolding and humiliation. For this, I have two alternatives.

If you are vested with stocks or somehow protected by some strong contract, and believe in the idea, the solution is to bark back. Abusive behavior are always multiplied by lack of balance and checks.

If you are just a developer, with zero personal benefits than compensation, the solution to your problem is quitting. Suddenly. Even if you do not have another job in sight.

The reason of this sudden quit is to ensure you halt the damage to you well being while staying in this company. The damage is and will be there: days you don't feel like working, arriving very late and leaving very soon, avoid opportunities, apathetic feedback when approached by people etc etc. In the right intensity, even depression. (well if you're in US you might want to actually get depressed and ask for compensation in court. Probably will give you more money).

Good luck.

soroso··on Functional programmers act as if Go is stealing a future that belonged to them
I had the same fear too... It is not completely gone. But it helps a lot the fact that it is fully open-source, and the majority of contributors are outside of Google.
soroso··on Dear AirBNB, No Thank You for the XXX Freak Fest
Sorry for my lack of knowledge. What is it "XXX Freak Fest"?
soroso··on Ask HN: How do I become a faster programmer?
IMHO, right now no one really can answer that. There are tools that can help you speed up, such IDEs and online resources; and of course nothing replaces practice and experience: the more experienced you are, more patterns of code you're gonna have from top of your mind, essentially allowing you to jump faster ahead.

The real problem now, is that the programming languages are now trying to solve a weird dichotomy. Do you want a language which syntax allows you to express your ideas in as few lines possible? Or do you want a language in which the syntax itself is not that important (you'd be OK with inconsistencies and lack of idioms) but that would have all batteries included?

So I believe in this case you will need first figure out your programming identity before worrying about your speed.

If you feel that speed for you means writing fastly well defined algorithms, you might want to take a look at the modern functional languages. In them, it really doesn't matter if you type fast or slow, or if you can think fast or slow, all you need to worry about is to use the proper idioms properly to achieve an implementation goal. If you manage to choose the right idioms in the very first time you're writing something, you'll be debugging just tiny typos.

If you feel that speed is getting things done fast - even if it means you might be brute forcing your way out of the problem - you might want to take a look in languages with very rich standard libraries like Java, PHP or Go. All of them have issues with their syntaxes (respectively verbose, inconsistent and bland) but because they have extensive standard library all you will to memorize and practice is the call for tools they offer.

Then, I believe you will be able to say you're faster.

soroso··on Ask HN: How to succeed with poor working memory as programmer?
The fewer you memorise, the faster you remember. So the trick is to leverage abstraction and memory by association.

Abstraction helps you to reduce the amount of things to remember, and association creates clusters of related topics.

← PreviousPage 2 of 2