asjdflakjsdf

to a degree but not so much. Land has real value. Stocks are different again. The idea that eth is considered more of a stock than a currency is the root of its problems imo. I have a real itch to one day see a crypto being widely adapted as an actual currency. I think dogecoin is the only one in our current crypto eco-system that has even a fraction of a chance in filling that space. I'm sure it will happen some day, but maybe not with our current crop of cryptos.

I'd basically see it as an investment opportunity that greatly favours early adopters.

Ethereum is quite exciting in that regard, but my feeling is that most eth enthusiasts don't actually care about that. They only care about the value and thus it has become another crypto pyramid scheme for now.

The only crypto community who has shown any genuine effort in creating a "currency" is Dogecoin. And that is mainly because they are more aware that their coin has no value without real adoption. But sadly, even that has been infested with the pyramid scheme HODLers after the recent surge in value.

Another problem with Eth is that regular folk are thrown off when they hear things like "smart contracts", "NFT" etc.. So, in terms of a realistic crypto "currency" having widespread adoption, it seems hard to justify any of them at the moment.

I love using crypto for payments as it can be incredibly simple when done right. I really hope to see a crypto that works toward distributing wealth and opportunity though rather than the toxic crypto culture of HODlers we see today!

eh, that's not really the case in a lot of developer jobs these days. A lot of agile/scrum adoption/bastardization has meant that all work done has to be decided by the team and pretty much every piece of work has to be approved by a product manager. This can often lead to some demoralising meetings where you can either lie about the effort/risk/goal or you can give a true value estimate that gets shot down. If you lie, you can end up spending your own free time working on that refactor or documentation etc. For most devs working on a codebase, its not theirs, and they don't determine what has priority.

In reality, for a lot of people, if you start refactoring the codebase while waiting for a new task you are likely to break something and its just not worth the hassle for the developer or the company.

Learning new tools is always great ofc but it can be very hard to find the motivation in such a role, where unless you are a senior developer, you probably won't have much say on adoption, and you will likley just develop a half baked understanding of a new library that you will never get to use in production. Its much better to have some real free time where you can focus on your own projects and learn that way.

So in short, maybe it should never be the case that devs are in that position, but it often is. Especially for devs with less experience

great, thanks.

link to extension: https://chrome.google.com/webstore/detail/github-helper-code...

and readme: https://github.com/whatever555/git_helper#github-code-review...

yes it just keeps reloading the css files for the page

thanks for the feedback. did you enable it for your domain? you can turn it on by clicking the icon and following the options

Its just a simple little extension that reloads your css files in the background so that you can view changes without having to reload the page each time

Github: https://github.com/whatever555/refreshing/

that's incredible

would be really cool if it just accepted a url and showed the rendered version of the page on all the images available...