devnull3
1. Tracking i.e. navigating through jungles for hunting or find where the bottleneck is.
2. The thrill of the hunt. The joy after finding the hotspot or the bottleneck. It makes your day.
3. The actual hunt i.e. shooting an arrow/spear or using clever way of fixing.
4. Brag about the hunt or writing a blog post or tech talk on how difficult and awesome the hunt was.
Also optimizing a critical path has multiple takers in the org:
1. Product Managers are happy due to improved user experience.
2. Management is happy as in some cases it actually saves a lot of money.
3. Your boss is happy because he/she gets to score points as "team achievement" when evaluation is around the corner.
4. Engineers get to do nerdy things which otherwise would not find traction in the org.
All in all its a win-win-win-* situation.
Before performing upgrade make a copy of the db file. Also multiple DBs can be inited in parallel.
I fail to see why this might be so hard.
If a tech works 80% of the time, then I know that I need to be vigilant and I will review the output. The entire team structure is aware of this. There will be processes to offset this 20%.
The problem is that when the AI becomes > 95% accurate (if at all) then humans will become complacent and the checks and balances will be ineffective.
1. Identify top-N tenants
2. Separate the DB for these tenants
The top-N could be based on mix of IOPS, importance (revenue wise), etc.
The data model should be designed in such a way that from rows pertaining to each tenant can be extracted.
The fact that no one really knows how LLMS will pan-out means every projection in future is a prediction.
Infact, a lot of the patterns in the likes of HTMX will be standardised.
HTMX's OOB swap appears to be an after thought.
[1] https://www.google.com/search?client=firefox-b-d&channel=ent...
[1] https://thephd.dev/c2y-the-defer-technical-specification-its...
If AI trains on generated text it is equivalent of an incestuous relationship and I don't have elaborate on analogy further.
Infact the patent holder can file a lawsuit against a startup. Now even if the startup can prove that the patent is invalid, it has to spend precious money on the lawsuit.
Others can. But during their application who is going to tell that there is a prior art? Patent offices only do basic checks on existing patents and not on the wider internet.
Once the others get their patent, you can appeal [1] it.
[1] I am not sure its the right word
Am I the only one who thinks the this sacrifices the readability?
The world has always been divide on: Owners and workers. This transcends communism and capitalism. Owners always wants more work out of workers. Owners unknowingly or knowingly behave as if they own the people. This was literally true when slavery was widespread.
Even in western countries we find the unwritten understanding between Steve Jobs and Eric Schmidt not to poach each other's engineers [1]. Where is a the "free hand of markets" here? Does it not limit the career opportunities for employees?
Activision Blizzard, one of the top AAA game developer had huge culture problems. There is a lawsuit as well [2]
How is it in the land of free and ideals of Martin Luther King and Abraham Lincoln get to a point where humans are treated like corporate property?
[1] https://www.theverge.com/2012/1/27/2753701/no-poach-scandal-...
[2] https://en.wikipedia.org/wiki/California_Department_of_Fair_...
1. Services
2. Products
The product companies's culture and environment are on-par with silicon valley and this includes a good pay as well.
Services is another matter. The fundamental issue is the business model. These companies earn revenue per person and hence the incentive is to over-staff or over-sell the people needed. There is no incentive to solve or be pro-active about customer's problems.
Hence the "leaving certificate" serves multiple purpose:
1. Person is not working elsewhere
2. Person has gracefully exited the employement and there not pending dues or conflicts.
An existing employer can weaponize this and simply not issue this letter.
This does not happen in India but I am not sure if this the case in Japan though.
Does that mean that say a security vulnerability in openssl is a responsibility of all software which uses them? I think its unreasonable to expect software projects/products to find things like heartbleed.
What about bugs in kernel/OS? How many user-mode software can find bugs in kernel/OS?
There are times when a feature is used in a way which was not intended by the developers. Now do the developers have to publish their test scenarios?
What if the bug is in 3rd party library? Add to it the complexity of open-source code.
1. Anyone claiming to know India well is either foolish or lying? (This includes Indians). India is diverse on all counts imaginable (color, language, wealth, urbanization, etc). Every permutation will throw up large number of people.
2. India consistently disappoints the pessimistic and the optimistic. If you see the bad side (poverty, chaos, etc) it is easy to bet that this country is going nowhere but this is just few scenes of long movie. There are other scenes and its easy to be absolutely bullish.
3. Think in absolute numbers as well and not just percentages. 3% in India translates to lot of people. It is more than the adult population of many countries. Apply this to any metric you will get large numbers on either side of the bell curve. So in India you will find 3% of the smartest and also the dumbest (in IQ terms) both in huge numbers. You will see these (only a subset of) 3% migrating to western countries and be hugely successful.
As per me the only way to deal with India is to accept its all hues and colors.
Also, apis like S3 are defacto standard with many vendors supporting a descent subset of it.
Also SF was based on SVN. They failed to understand and capitalize on a better tech on the market i.e. git.
So, a downfall of a potential alternative was also a factor IMO.
Edit: after I commented I realized that SF was already mentioned in other comment