Thoughts: The URL is suspicious, may require changing the URL. The solution likely requires combining the boolean operators, but not sure how. I'm especially unclear how to use the words in the URL. "true", "false", "0", "1" etc. don't work so it has to be something more than simply evaluating a boolean expression.
is it writing a message in signal, telegram or something like that if yes which one to frank underwood for the underwood machine plus the tap tap tap. :( I'm confuse. also I was thinking about the famous writers that own a underwood machine
Screw Apple! I'm moving away from it. The system is just not suited for any system's development. Too many undocumented and unexposed crap in the OS. If one want's to do something with the AV, it is near to impossible because of the restrictions and it is not something they've invented. They are bunch of lazy people who doesn't want anyone to mess around with their OS. They will never learn or change. Better stick with Windows or Linux (It has greatly improved for AV in the recent years and it's just the fragmentation which is causing a lot of issues which might eventually get consolidated or streamlined. That's another issue by itself!! :))
And all these notorization and getting a certificate every year is just too much to continue the development for a small bunch of users who doesn't even know or care about what is existing.
Some good folks amongst the users are there, but they can be counted with one hand. All other Mac or Apple users doesn't even have a clue about what is under the hood. It just has to look good with oohs and aaahs... And that's pretty much it... Offcourse as long as it works the way it is supposed to work (and that is how the 99% of it's dum dum users use it), they'll continue to remain a trillion doller company... iOS is another story by itself...
Created a LIMS system (Lawful Interception and Monitoring Systems) in 2000-2001.
It was abused at a large scale in some large enterprises in India to monitor it's employees network communication.
Thought I was doing a good work for govt. agencies, but in turned out otherwise due to the abuse and affected a lot of privacy. Since then, I've made myself away from any and all mass techs as much possible and stuck with manual methods, cash and privacy friendly alternatives.
It's like creating a double edged sword. All the newer age, continuous monitoring and etc, etc., are doing more harm then what it solves...
Like in medical community, but an opposite... Risks outweigh the benefits!!
Enough said! Peace!
I have played / playing CTO for multiple startups spanning over 6 years with a total experience of over 20+ years.
I am fairly successful (!?) (though the perspective is my own and satisfied with the mix of life I'm into and whatever I'm!) in my career and have enjoyed a good and competent technical team with me all the time.
I mentor my team mostly from ground-up and have found that anyone can become a fantastic and a dependable competent resource provided enough freedom and directions. Also worked as a startup coach. Been into startups since early 2000s
Obviously, this handle is my pseudonym and not my real name. Extremely sorry for that as I value privacy more than anything and people call me that I'm a paranoid. I'm still not in a position to divulge much personally.
I'll try to list down common issues faced and lessons learnt by startup a CTO as much possible.
- Having to deal with a non-technical founder is very hard
- Technical work could be very challenging if you are one of the few who takes cares of many things or try to play multiple roles
- Getting competent resources could prove to be a very tough task if you are in a third world country. (I'm not talking about the Bay Area types)
- Have a process right from day one. Do everything in a documented manner and work like what will happen if you get run over by a truck (it could happen to anyone on the team). Then what?
- Technical stack identification for an initial MVP will take time until one gets it right considering a 360 degree view covering all the aspects
- Having business knowledge / outlook is a must and without that, however technical one could be, he/she will not bring value on a long run. There could always be a better one who will replace you
- Strike the deal from the day one. There is no free lunch. Negotiate hard and properly for what you are worth. No slack or compromise on those aspects
- There are no shortcuts for anything
- Everyday is a learning day
- There are newer ways of doing things which gets into the mainstream and some might even come from you!
- Keeping the team together and motivated is an extremely tough thing to do if you are in a non-commercial decision making role. Try to vest some powers towards that direction if you are joining a team (not as a part of core founding / decision making team, but just playing a CTO / VP of Tech or something akin to it)
- Pleasing everyone is not possible all the time. Learn to cope with frustrations and take decisions based on long term goals
- Never get driven by emotions
- Be ready to adopt to any situation, and be adept at many things. Learn, learn and learn and put to use
- Have a birds eye view on everything and have the vision of an ant on specifics (up close!)
There is much more to write (it's my part time passion and mostly use it for internal communications, mentoring and teaching), but seriously considering it towards a book of experience in (near?) future.
Though the above is incomplete in many ways, would like to hear the thoughts / views from other technical people. Thanks for reading so far!
