It should stand a test of time. Don't pick-up books released this year. Search for the ones being recommended by people you trust and that are at least 5+ years old.
793 karma · joined August 7, 2012
https://bento.me/kirso
You don't need to even think where to put notes.
All that overwhelm that all the folks are speaking about, just start writing in your daily page, when you look back -> you have a clear link.
It actually kills ambiguity without having folders and having too much un-needed structure (obviously use-case varies).
Logseq doesn't need plugins because a lot of it is already in-built (tasks, block-references, in-built queries).
It reminds me of the discussion when people praise Next.js for all the packages, and ecosystem but its not a feature, there is a reason people building these.
Spotify has a completely different business model, architecture etc.
Learned HTML/CSS in 2012. Built an app in Rails in 2014. Learned basic Javascript in 2018. Delved into React in 2020. Shifted to no-code. Back to Fundamentals in 2023.
I think its hard to really be good at it, but depends on the goal. Most people want to be software engineers for the wrong reasons these days. To me it was always a hobby and if I can build some small useful things for people with just front-end and a database its a win.
Its not easy though. It never was. It requires commitment and patience as well as regularity beyond tinkering with it 1 time a month.
Jokes aside, I think you kind of need to know how to problem solve in code to even know in which direction to go.
If I tell it, create a Facebook - the limit will kick in. But most people do not konw how to destructure Facebook in terms of functionality and what components are.
“Your personal experiences make up maybe 0.00000001% of what’s happened in the world, but maybe 80% of how you think the world works.” - Morgan Housel
Its the same with dating. If you date toxic people, you start generalising that all men are abusive.
Same with PMs. If you are working within a company that accepts subpar talent, you'll start seeing things based on your benchmark of quality. Until you actually work with a great PM that makes your life easier.
There are good engineers and bad engineers.
This polarisation is IMO an incredible bias.
We were all conditioned to buy courses to learn programming in 5 minutes, yet we are bound to be disappointed.
We eventually learn though, with more frequent feedback loop and fails.
In a game instead of going with the flow and trusting the process people tend to start reading guides how to make the most OP character, maximise stats, and make it a 100% completion.
This approach eventually sucks out the pleasure of exploration and random encounters that made the games so good and instead makes people spend hours on trying to maximise stats in a random dice roll fashion.
Similarly with other activities, the sense of wonder and "just because" goes out as we are all trying to max out something, whether its wealth or code quality.
We don’t need to explain ourselves to them.
We don’t need to prove our success through conventional means.
We don’t need to measure against a scale that others have invented.
We don’t need to feel guilty for refusing to take on unnecessary responsibilities.
Everyone thinks that the way to convince people to trust them or acknowledge them is to be know-it-all, but the truth is just being authentic and help will come.
Don't know where to put the idea, note or just a scribble? You have a 2022-05-12 page without the cognitive load or confusion.
However, I also realise its always easy to critisize the processes from down to top. Now put yourself in the shoes of the CEO or C suite. How do you organise an entire organisation to be efficient? What is a better alternative to OKRs?
Most of the proposals I see in this thread are catering towards smaller companies but quite frankly not a lot of us managed a 1000 people company. I would be curious to know from practitioners about what worked and what didn't.
This contributed to a junior coder market where people are not ready.
I only found a handful of resources out there which are really preparing everyone for a long journey.
Long gone are the promises of a $500k job after 3 months of studying...
If you like painting, work on your craft, not for the sake of betterment but for the sake of joy and appreciation for your craft.
If its weightlifting work on it for the sake of yourself.
IMO this applies to everything you do.
I feel like there are not enough games somewhere between casual and core without the need of spending 50 hours on it. 10-20 hours is the sweet spot.
This is IMO impossible without experimentation and doing stupid stuff during the 20s.
I just turned 35 and only starting out on the best work of my life in the shape of offering something of value except for just my time at work prior.
Nobody really cares about you in the org and in the world in general.
There is a legal implication on side projects on everyone's contract -> so the solution here is to just have an alternative profile on social media...
Oh and don't add HR people on your linkedin.