Hacker News new | past | comments | ask | show | jobs | submit | more aytekin's comments login

In most development work team productivity is more important than individual productivity. I have found that the best approach is to have co-located team rooms. (And the team members should be working on the same project. Putting people together does not make it a team. If everyone has a different project, that’s not a team)

If the work has to be done individually, then there is no point in being co-located. Remote works well.

Co-located teams communicate well, decide and move quickly, and has much higher trust between team members.

Work that does not require too much communication, speed and collaboration is more suitable to remote.

This hybrid approach worked well for us.


We have been supporting this feature on our web app for many years: https://www.jotform.com/encrypted-forms/

Knowing only you have access to tha data is a good thing. For example, we are able to host our internal employee feedbacks and reviews on our own forms without worrying about a sysadmin or database admin having access to it.

I understand the concerns about client side manipulation but that is hard to do without leaving a trail on our code commit history. Both system and product changes can only be done by code commits.

You cannot protect systems with a single perfect security solution. You have to be paranoid and have many layers in your security model. This may not be the silver bullet, but this greatly enhances the security.


I do inbox zero so I am not usually looking at the email list, but to the actual emails. I also started using larger fonts as I am now 40. So, the amount of space the left and the top frames take up is quite a lot. I haven’t tried this but hopefully this can fix that.

By the way, here are the tricks I do to do inbox zero on gmail: https://www.entrepreneur.com/article/290175


Thank you! The "moving backwards up the list of emails" might be just the thing I need to clear out my email backlog and stay on top of things. I didn't know gmail could do that.

You're being downvoted for being off topic perhaps, but in years of looking at threads like this I'd never seen that tip. And not using the UI at all is a viable approach.

Incidentally I must be on an old UI, my gmail looks nothing like that. Either version looks harder to navigate than the classic one.



What doesn’t kill you makes you stronger.


My version of the saying is - what does not kill you cripples you.


“What doesn’t kill you makes you smaller” - Super Mario


5% + 50c!

They only make sense if you are small in scale. Use them when you are starting out and then build your own after you have a good number of paid users.


Everything has its price. I preffer to improve a core product than to get drowned in international accounting maze (hello EU VATMESS).


I’ve tried writing my own billing system on top of Stripe and PayPal. And I’ve tried using a Paddle-like service (FastSpring, to be precise.)

The bookkeeping and support for my business was much easier when I used FastSpring. I believe the higher payment processing fee to be worth it.


Yes, once you scale really big it is hard to keep a high growth rate. But if you have been always growing at 50% YoY, it is possible to keep that rate even at year 12. This is pretty common amount bootstrappers. I am speaking from my own experience at the company I founded: JotForm’s last 7 years were at 50%.

Ahrefs recently announced a similar growth rate: https://medium.com/swlh/how-we-achieve-65-yoy-growth-by-igno...


Money as a motivator sucks. It is much more easier to earn money as a side effect of being really good at what you do.


You're both talking about money but I don't think you're on the same page as your parent post. They're just saying that it's easy to fall into the trap of being comfortable, whereas when you have to "hustle" (sorry) then you build up a lot of momentum.


Creative Selection: Inside Apple's Design Process During the Golden Age of Steve Jobs by Ken Kocienda

An amazing book full of great stories and lessons to learn from people who made incredible innovations like the first iPhone. My favorite parts are the story of the iPhone keyboard and detailed encounters of Steve Jobs demos he has given.


They should publish on their blog first and then use the import feature of Medium to republish it with a canonical to the original.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: