devnull3
Actually a lot of mechanical manual work we do are subroutines.
Examples
1. Make an omlette (params like: which kitchen or ingredients are derived from context)
2. Change engine oil
3. Take blood sample
Yep.
"Power resides where men believe it resides. It's a trick..." -- Varys from Game Of Thrones.
"In India, the software is not directly patented but it can be granted patent if it is attached with novel hardware, an invention that is unique and capable of industrial use."
So patenting a pure algo or data-structure will face legal hurdles.
[1] https://techcrunch.com/2021/09/13/india-and-singapore-to-lin...
This means that a private player's implementation does not become defacto standard.
Multiple factors are aligning to make UPI successful:
1. Massive Mobile (smart phones) & Internet penetration
2. Cheap mobile data from telcos
3. Low cost of payment infrastructure to the banks and shops.
4. Fast clearing of payments (< 5-8 seconds)
5. Neutral standardisation body with blessings from the central bank
For short term this might be ok but in medium term the govt should study this space, do broad consultations and bring some regulations instead of banning it.
I would add developed Western democracies in general.
Reminds me of a dialogue from GoT: Power resides where men believe it resides.
Sidewinder – The Weapon That Changed Air Combat
Newman: Don't you find it interesting that your friend had the foresight of buying postal insurance? Parcels are rarely damaged during shipping
Jerry: Define rarely
Newman: Frequently
Production Hell – Batwoman
Newletters are essentially curated content for specific audience. Even if there is a content profitable for a while then it will be made into a commodity soon because it will attract so many folks.
Also, the issue with content from individuals compared to content from companies: Scale. The dynamic of working alone vs making money is hard to pull off if not impossible.
A lot of people want this. Its basic human nature ... take or construct the path of least resistance. Its just that most people cannot do this and only top 1% can.
The whole FIRE movement makes ppl aspire for the day when they can live on passive income from the savings/investments.
The funny thing is Google as an org ends up hating their users "accidently" anyway because of their history of pulling the rug under the services/APIs etc.
The idea is that if passwords are compromised they will not work unless you know the algo. So now you will have to remember two things:
1. The master password
2. The algo
Ask HN: Protecting against Password Manager getting hacked
I am thinking of using a password manager. I am having trouble to trust these managers. My fear is that a password manager becomes a single point of vulnerability.Here is an idea to protect passwords.Say I want to store the password: ykT%mK#5 (just an example). Instead of storing it as is. I would apply the following algo:1. Reverse letters2. Add character at 5th position (1 based indexing)So...
Second was the degree of false paths (term I made-up). This essentially governs the branching of each false path. Higher the degree higher the branching and higher the backtracking. This would make the maze harder.
So my algo was
1. To generate a valid path from top-left to bottom-right. (this is simple bfs/dfs walk). This is illustrated as path 1-2-3-4-5-6-7..-10 below. This ensures we have a fair maze.
2. Now from each number below, generate path in an outward manner till it hits walls. These are false paths. The "degree" mentioned above will dictate if there are further branching out of these paths.
1 * * * * *
2 3 * * * *
* 4 5 6 * *
* * * 7 * *
* * * 8 9 10
In the step #1 we note the row,col in a dict/hashmap. We use these in step #2 to ensure the dfs walk dont step on these row,col.
This is all I could conjure-up in 45 min including a code in python. I was labelled lean-no hire.
Edit: fixed the rendering of the maze
---------
This can be a good interview question for Google to screw people over.
I was asked to write a code to generate maze (100x100) with the constraints that it should neither be easy not it should be hard. This was for L6 position.
This is analogous to Xerox experimenting with GUI and not really believing in it. No real drive, no zeal. Satya doubled down on it. Made it priority 1 and most importantly executed it well.
Ballmer's world view was completely different which was more rooted in 90s and early 2000s. He was more of Windows guy and not really seeing the changing trends. That is why MSFT's foray into mobile looked like an after thought.
1. Github acquisition: With already dev-tooling play they have, there is a clear strategy here. I think this will serve them well.
2. LinkedIn acquisition: Not sure how it is faring.
3. Friendly relations with open source projects: It improved developer mindshare
Now the same friends admit that there is a lot improvement in this regard since Satya came on-board.
[1] https://images.squarespace-cdn.com/content/v1/500e2d14e4b042...
On the other hand, new age product companies/startups are similar to Silicon Valley.
Yeah, these companies make employees read & sign code-of-conduct, ethics etc. Hell, I was made to attend sessions explaining "values" of the company.
The sheer hypocrisy ... only if execs walk the talk, the world would be a better place