"Indistractable" by Eyal Nir is a good book if you want to dive into this topic.
Readit News___luigi commented on How to Break a Phone Addiction theatlantic.com/family/ar... · Posted by u/fortran77
I think the author didn't cover a lot of fundamental research behind NoSQL. If you are reading this comment, and want to dive into SQL/NoSQL DB fundamentals, I highly recommend checking CMU DB (Andy Pavlo) lectures [1] [2].
[1]: https://db.cs.cmu.edu/seminar2020/
[2]: https://www.youtube.com/playlist?list=PLSE8ODhjZXjagqlf1NxuB...
___luigi commented on PostgreSQL 14 on Kubernetes blog.crunchydata.com/blog... · Posted by u/plaur782
___luigi commented on PostgreSQL: Kubegres is available as open source postgresql.org/about/news... · Posted by u/9woc
I wonder how is this compared to Stolon https://github.com/sorintlab/stolon?
___luigi commented on The Fastest Path to the CEO Job, According to a 10-Year Study (2018) hbr.org/2018/01/the-faste... · Posted by u/mgh2
Something that has always surprised me a bit is how many developers want to run their own large companies. Wanting to run a small company is largely about personal freedom that comes for not having a boss, but wanting to be the head of a large business is a whole different ballgame. It's a role that encompasses strategy, leadership, and management - 3 things that can only really be done by talking to people and understanding them. It's a very different role to writing code. Most developers who enjoy writing code run away from meetings given the slightest opportunity, yet they also covet a job that's 90% about having meetings.
For a very long time that was my own journey. I got up to CTO level for a while. Then I realized I just don't enjoy it, so now I'm a senior engineer again. Wanting to be a CEO takes a very specific mindset.
One book that helped me understand these challenges was "Hard things about hard things". I recommend/gift the book to any (engineer) friend who is burning to start his own business. It's a different game. Even Sr. Engineer is a different game than coding, we spend some time on System design, mentoring, presenting technical outcomes of our work/PoCs, writing new product requirements, .. etc. I think these tasks require other skillsets as well.
___luigi commented on Facebook thrives on criticism of “disinformation” doctorow.medium.com/faceb... · Posted by u/throwawaysea
Disinformation is a problem for all social media platforms, for all languages, FB is one of those platforms. I have the feeling that media focuses more on FB & English, but we should rather focus on the problem as whole and its harm for all communities around the globe.
___luigi commented on Why is everything so hard in a large organization? graphthinking.blogspot.co... · Posted by u/physicsgraph
It seems like a lot of people here have been in an ineffective large organisation and an effective startup. I've worked at an effective large organisation and an ineffective startup, so perhaps I can shed some light on what these kind of processes are for:
* You don't get to be a large organisation without accumulating generations of previous products. Well, unless you're google and can regularly fire your customers without going bust. but part from them, you start to need processes just to track what's going on. (The ineffective startup accumulated previous product attempts too, and is still paying for a lot of pointless infra because no-one still there knows which ones can be switched off).
* At a large scale, it starts to be pretty difficult to maneuver if each dept of 30-50 people has built or contracted all their own infra & services. Some divergence is useful for agility, but a lot of it is just waste and actually slows you down when you want two depts to work together on something - or even prevents useful collaboration. An effective organisation will make the tradeoff consciously.
* When you complete dozens of projects per year, it starts to be possible to invest in researching and rolling out best practices in areas where a startup just has to go with the simple/obvious answer. When my startup employer moved, it was pretty onerous, and there was a bunch of stuff we never found again. The large org had so many offices that it had a full time dept just for moving offices. (They weren't dumb, each move consolidated offices -but they kept buying other companies). When they moved us, it was like magic - we went home on a friday and went to work on a monday in the new office, and everything was set up. Well, we had to set up the lab ourselves, but
This is GREAT summary!
I work in a large organization, in an industry that is naturally slow. The work (in the industry) is slow because it's critical to deliver stable and reliable solution because large part of population and economy rely on this industry SW/HW. I have heard a lot of complains on how the process is slow, but in many cases, building on top of existing work takes a long time. It takes long time to understand legacy work, to go through older studies and projects, and to find spots to add contributions. Not all of us work on green field projects, but many of us maintain code/work that doesn't look "cool".
___luigi commented on Unhook: Hide YouTube Recommendations chrome.google.com/webstor... · Posted by u/tandav
Hiding distractions? Sure. But I personally find YouTube recommendations quite good - if you don't ruin it by accidentally watching a single meme.
It's not perfect, but what would be a good alternative for finding new channels that you would like? Do y'all have any suggestions?
> YouTube recommendations quite good
I feel it suffers from "rich is getting richer" phenomena. Once the video start trending, the recommender starts showing it for any search.
___luigi commented on The GIL and its effects on Python multithreading tenthousandmeters.com/blo... · Posted by u/WoodenChair
Is there any reference to delve in the details of GIL, multithreading, multiprocessing, high performance computing on top of Python eco-system?. There are some interesting projects such nimba, Dask, etc, but the resources are a bit scattered.
This is wrong and misleading in many ways, you should ask people why they left, you should give a chance to those who have good skillset, not based on number of jobs they had. I know a lot of people who worked on contracts, so they had to change employers frequently, and I know a lot of people who were looking for a place, as juniors, to learn from good mentors. It is really hard to find mentors in Startups, and not everybody can make it to big companies. If companies don't invest on their employees, they leave.