This is such a neat tool. The presentation is very pleasant. Is the intention to have the snippets/notes be shareable in the future? I actually made a similar tool [1] (though your's is much more complete), which I use to quickly find passages and relevant text when I'm blogging. And, I was thinking it might be really useful to have highly rated notes on a snippet available so that you can get someone else's insight on a particular selection. I'll give this a more in depth look later when I want to write another blog post.
Thanks for sharing, I like the name and I'll try it out. Yes, I'd like to add opt-in sharing features in the future -- seeing others' notes can be very insightful as you said.
Yeah, I know that online "investing" is driven by hype these days. But, I was basically hoping that there was something out there that at least explores investing ideas out of the mainstream not based entirely on hype or rug pulls. Just want exposure to some interesting ideas that I can then do due diligence on.
Thanks, had not heard of The Art and Science of Technical Analysis, will definitely check it out. I read Intelligent Investor, but kind of felt it lacking, because I didn't feel like it went low-level enough. I also have Security Analysis by Ben Graham, but have never gone through it. Any thoughts on that?
I guess, like with everything, the best way to learn is with practice, so as soon as you can start getting screen time on the markets.
Use whatever books to understand concepts, not strategies. For example, work to understand the why of the Bollinger bands or why hammer patter and how is can be related to volume... don't try to learn strategies like "buy the dip" because nobody really know what's the "dip".
It's very easy to see patterns on a graph but it's completely different to see them as they are forming and being able to predict what is going to form.
It is all random but it's based on human behavior, so a "breakout" is not just something that happens on a graph, is a bunch of people (or machines programmed by people) looking at a specific price and when that price is reached a bunch of trading happens moving the price because an expectation was there... "if $AMZ reaches $XYZ I'll buy"
Also, people have memory, and tons of greed, so if they made/lost $$ at some price point it's possible that they are now fixed around that price to make an action... i.e. I buy $AAPL at $500 but it went down to $480... well, I'm greedy enough to try to save face and try to wait for AAPL to go back to $500... even if it keeps dropping...
All that is to say, look for books that give you insight into why people behave the way they behave on the market and then try your hardest to behave in a way that is of your choosing and to your benefit instead of just letting emotions take over.
Also, about getting screen time, it's completely different to get screen time on a paper account vs with your own money, so as soon as you are able put some money in (something that you are ok loosing), you'll very quickly realize some strong emotions creeping in, and handling those emotions is what a few traders say separates the ones that are profitable vs the ones that get wiped out.
Looks interesting. Is there a benefit specific to using PHP for building the UI, like access to PHP libraries, etc.? Or is it for people already using PHP on the server-side, so they can also use the same language for the client-side?
It's for PHP developers mostly, who want to build SPA but struggle with JavaScript frameworks, or who want SPA as well as efficient SSR without involving Node js on their servers. Plus, it's already familiar php and html, similar template syntax as in Angular or Vue.
I think he's getting at something important. I started writing for the same reason basically. But wish there was a way to network my writings with other people's writings.
Maybe I just need to build a social media following (probably on Twitter)?
I miss the community of bloggers in the old days... there was these groups of people often cross-referencing and reacting to each other in the form of essays. No particular hierarchy, just an amorphous conversation
Yeah, I prefer the discussions via essay format as well. Instead of the quick meme reactions. I guess it's good for comedy and being edgy, but not really for high quality ideas. I vaguely recall seeing a Show HN of a discovery tool for personal blogs, but don't think it really took off. Sad to see.
Had a boss once who insisted that all if statements should be pushed out to factory classes, and all control logic should be done by constructing a different instance of an interface. It was a pretty rigid system, but at least it did force me to write small focused classes that were easy to test.
Debated for a long time whether that methodology was stuck in the second phase or if it was actually the third. Still don't have an answer, but these days I think having a plan is better than just letting engineers run roughshod, as long as the conventions are easy to follow.
Programming alone vs programming in a team are very, very different occupations. A lot of what applies to one doesn’t apply to the other. I’m still painfully learning this, after all these years.
I think it comes down to there being two kinds of codebases...
In the first kind, all relevant developers have deep expertise in the system, or build towards having deep expertise. There's an expectation that flexible abstractions will be used, not abused, unless it's one of those scenarios where the use outweighs the abuse. The abstractions are tomato cages, and they're there to support the system as it grows, provide some structure, but not to strangle it.
In the second kind, the default expectation is that a developer will have little to no familiarity with the system, they will be isolated from it as much as possible, and they will be given such a tightly constrained sandbox that they can't break anything outside it. You will write your little plugin, or whatever, get in and out, and you're done.
These can both be useful kinds of systems/codebases in orgs of any size. The first kind of codebase can enable an experienced team to move really fast and be extremely productive. The second kind of system can help lots of different teams of different skill levels jump in and leverage your system with little required knowledge, and thus be productive that way. So there's really no way to say one of these patterns is good or bad.
But in general if you churn in and out a bunch of replaceable cog code monkeys, probably low-paid, the second kind of system just ends up working better. Giant "enterprise" software shops like parent poster aluded to typically end up in this kind of high turnover scenario after enough finance/MBA people have been brought in, hence their bad rap.
I have much more experience working alone, but: git alone is a breeze. I don’t need to impose myself some arbitrary constrain because I know (or think I do) I won’t abuse it. I can use the stack I consider best/am more productive on, instead of what’s fashionable this year. No linting, coding conventions, etc. Just the pure joy of problem solving.
On the other hand, on the right conditions, the amount you learn on a good team is ridiculous compared to what you’d do alone. Weeks vs years kind of thing.
The key insight to "at least destroying your architecture makes it easy to unit test" is that being able to unit test is not actually that important. There's other kinds of testing out there!
I bought a PopOS Gazelle with an Nvidia GPU so I could play around with ML stuff. But, looking back on it, it might have been more efficient to just get a GPU instance on AWS or Google Cloud, and just using a remote desktop like this.
Anybody tried that configuration? If so, how has your experience been?
Yeah, I feel like this article's outrage at the inability of prisoners to get used books is unwarranted. What actually deserves this level of outrage is the violence encountered by many in prison as you mentioned.
Imagine going to prison for a small-time felony, and having to deal with widespread rape[1], gangs[2], and drugs[3]. Many of the people are in prison did seriously bad things, and should be allowed out any time soon. But, the eighth amendment also says people should not be subjected to cruel and unusual punishment [4]. But perhaps I'm just soft like Tom DuBois from The Boondoks.
[1]: https://ishmael.app