softwarefounder

"build in a weekend"

I just signed-up - I'll give it a try. Nice sign-up process.

- Hook yourself into online communities - Take a college course, PRIMARILY if you need to be pressured to finish your work (i.e. pass/fail). Otherwise, it might feel like a waste if you can understand the concepts through your own learning + communities.

This is a muscle that you have to practice developing - it'll hurt at first.

Small things you can start off with:

- Use less emoji's when interacting via SMS or Slack with your colleagues. Indicate a little less sentiment.

- Learn to say no, nicely.

- Stop being obligated into situations you don't want to be part of (meetings, situations, etc)

Some people will say that you're "imagining" these thoughts - that they aren't reality. If you have a high EQ, you may not be, and this may be what is actually going on. Consider this a gift - that you feel like you might be able to "read" people. Also be aware that you could be wrong on this.

Regardless - you can't live your life based on other peoples emotions. Act accordingly - if it helps, act as if you couldn't read that person.

Happy to chat about this further.

Is there anyone that you can bring up the ranks to make your omission less detrimental?

Slowly integrate them into meetings, company decisions; make sure it's someone you trust. And slowly step back.

Just an off-cuff thought.

Haha, brilliant point. Fortunately, it's probably a lot of VC money instead of individuals, or publicly traded companies; at least one would think.

Being 100% responsible for any failures (bugs in the code, missed promises and deadlines, etc), and having no padding between you and the client.

Overcome this by being painfully detail orientated. And never sub-contract, except to _extremely_ trust sources.

Is there a reason why someone would throw away unit tests? I've never understood this. Time was taken to write it, test it, upheave the bug, and now we want to remove the safeguards that we spent time/money on? Leaving the possibility for the bug to infest again?

Scrapping unit tests is scrapping time.

One of the best uses for Unit Tests and Integration Tests, in my experience, is for testing things that would be incredibly difficult to test through QA, or the UI.

Because if someone gets confused and doesn't/can't make the purchase due to this misunderstanding, this is lost revenue, for no other reason than assuming that a user knows what CVV means.

The most effective evangelists are those who have actually used the tools they're speaking of. And I mean more than for "hello word".

Let me say this: I went to a meetup several months ago for an Angular event. The speaker was horribly unimpressive; quite literally copy and pasted code from the Angular Demo site in-front of us for the "demo", and couldn't answer in-depth questions. No one liked this "evangelist".

In short; have a conviction for what your evangelizing, and dig deep into it.

I love bagging my own groceries the way I like, and avoiding interaction with a potentially disgruntled and inattentive cashier. I love self-checkouts.

"No thank you...My salary is private."

Only on HN, would the same crowd that ferociously defends data privacy, decide to play devil's advocate on this comment.

(Regarding the thread under the parent post)

This is a foolish and idealistic stance.

Especially with all the factors to consider (neighbors, location, salary, relativity to peers, etc.)

Unnecessary tech yields contrived work. (i.e. job security / pay)

You're right about nexus, but I sell a non-tangible SaaS product (no hard-ware, no CD download, etc). It's a grey area, but I think I'm okay. I'll verify at some point soon. It's still a side-thing w/ little to no revenue.

WI.

This is a great question. Fortunately my LLC for my startup is based in a state that doesn't mandate charging sales tax for SaaS products. That being said, I do not go out my way to apply sales tax to those ordering in a state that does. I've never found a clear definition of what to do in these terms; at least, not without spending serious cash on a lawyer.

One word: Sub-contract.

Network with small to mid-size consulting companies. If they can trust you, it's a win-win. You 1099 with them, they make $20-$30+/hr off the top of your rate w/ no burdens of having you as an employee.

This also removes the complications of the sales side of things.

I was going to use GCP, but ended up using AWS after discovering GCP doesn't [currently] support MSSQL as a service.

Couldn't be happier with AWS.

Well first off, use the term "consultant", and you'll see a 50% increase in revenue.

When you land a contract.

You seem to be getting down-voted, maybe by the feminine comment, but you're right; it's clear that their marketing is towards women (https://www.spectacles.com/), and they're missing a huge market. (Why not two styles?)

Edit: Imagine if they would've had a male styled version, and tried to get Kanye West, or some other pop/style star wearing them.

Huge miss.

I like how this list is zero-indexed.

Authentication.

i.e. Have you successfully implemented a good OAuth[2] security system? Can you explain the difference between JWTs, and session auth? Why choose one over the other. Talk to me about SSL a little bit, even at a high-level. How do you secure APIs? Talk to me about how you encrypt passwords, and sensative data.

Have you had to deal with PCI DSS?

This is one of the differences between "I'm a developer who has maintained a simple CRUD app" and "I'm a senior developer who can build a secure system".

Or in other words, authentication separates the men from the boys.

Humorous, but true. For fellow developers that insist on using Bootstrap, I've been telling them to use the stable 3.* version.

Quickbooks Online. The greatness of QB functionality (it's improved a lot since it's initial release), and the benefit of accountants knowing QB, and being able to access it online without sending over files.

This whole thing sounds like a sitcom parody.

Agreed. The advice should be.

1) Build an MVP, and get it to beta. 2) _Then_ get customers to try it out (give them an incentive, such as giving it to them for free). This works well with individuals, or small businesses. Larger company's won't give you the time of day, and you probably want to wait until you have some sort of following before you approach them; or you'll get squashed. 3) Get feedback. 4) Repeat steps 2/3 until your out of beta.

Unless I'm missing something, it shouldn't really be "redis or MongoDb". More like, MongDB vs PostgreSQL vs MySQL.

Redis is usually used for caching and scaling that DB's have a hard[er] time with. Not as a primary datastore.