So I made a small tool that lets you assign categories to transaction CSVs. This is something I come across fairly often while running my small business and I use when preparing taxes. It's free, doesn't cost anything and hope it saves you time and you'll find it useful.
Totally agree with what you said about non-stick pans. Sounds like a total scam. I myself did not go with cast iron skillet (only for some outdoor/bbq stuff). But I switched to stainless steal pan from demeyere like 10 years ago. It's still like new and made thousands of meals. Now i'm in a (slow) process of converting all my equipment to stainless steel from demeyer, quality is just that good. Buy for life.
You can't really have crud without "external dependencies" because you need to store state somewhere.
I'd say, figure out your storage layer (sql, mongo, files etc) then pick the right tech. Django and Rails will let you very easily bootstrap simple crud apps with very little code.
If you need CRUD API i'd personally go with Go and some db that i'm familiar with (pg). You can achieve tons with Go without any external deps.
I'm a little surprised I didn't see more people mention Go honestly. It's kind of easy as a language to pick up, and depending on what you're doing, it might have everything you need in one swoop. Of course I've not done anything too advanced with it yet. Although uAdmin seems to be a Django inspired thing from Go, I'm not sure if it will ever take off or what, but it seems interesting at least to me. The name is kind of terrible though.
> We expect that some package authors will be eager to adopt generics. If you are updating your package to use generics, please consider isolating the new generic API into its own file, build-tagged for Go 1.18 (//go:build go1.18), so that Go 1.17 users can keep building and using the non-generic parts.
You're right. I maintain a very large code base in a private repo and a successful open source project. Generics will allow me to clean up a lot of code duplication internally, but given that Go modules are distributed as source code, this would force everyone to use Go 1.18.
My plan is to not use generics for quite a while, as it's pointless to have two separate implementations, one for 1.18 and one for < 1.18, which is difficult, because I really like the feature.
Upgrading to the latest release of the Go toolchains is generally a painless experience; the Go team has a good track record of enforcing backward compatibility. Hopefully this means that you can assume other users will be able to use code targeting new features of go 1.18 in pretty much the same time window it takes for other releases to supplant old ones, and make this feature not unlike previous (minor) language features that nevertheless would break users who cling to too old toolchains.
I hope that the publicity caused by generics doesn't taint this release causing people to unnecessary procrastinate a toolchains update they would have otherwise done if it wasn't for generics.
Sometimes, people can't be on the latest version of software due to various compliance and regulatory issues, and updating anything to a new version requires some kind of re-certification or new auditing. So, when supporting such users, you need to work carefully on balancing their inability to update, versus yours to move ahead.
Hacking on some projects or experiments is one thing, but say you're providing code for the automotive industry or the payment card industry; you're in for a world of regulatory hurt.
Well for the users, they should be upgrading anyway.
I can't see a situation where someone would mirror your library in and not also have brought, or be bringing in a non breaking language change in the new golang.
The only change management advice I could give, that you'll probably know, would be to roll a month slower than golang.
I think it's because despite the fact that the US is called the land of opportunity, the system is rigged against entrepreneurs (no social safety net) unlike EU where you can fuck around without a job for years. So, I think there is something about money making initiatives because you don't have time to mess around.
>the system is rigged against entrepreneurs (no social safety net)
So then, why does the EU lag behind the US so much at successful startups even with our safety nets?
Or is it mostly due to the US VC funding system that pumps crazy amount of $$$ in tech companies plus having a giant homogenous market with a high purchasing power, all speaking the same language, that's lacking in the EU and in the end has nothing to do with social systems?
>unlike EU where you can fuck around without a job for years.
That's definitely not true. While there are a few people who have made a lifestyle from playing the system in order to live off unemployment their whole lives, that's a minority and not something you can easily voluntarily do.
For the most part, you can't just voluntarily choose not to work for years and still receive unemployment. They'll just cut off your welfare if you do that.
I am not sure I buy that argument—the US has been incredible for entrepreneurs for a long time.
You're right about the lack of a social safety net, but US entrepreneurs are succeeding despite that. Whether it is talent, funding, taxes or mindset something appears to be working.
Dang this does bring back the memories. What was the other tool I used a lot for reversing. Something ice something... softice debugger. That was also a piece of art.
> I wish more devs tried to utilize modern css and js directly instead of relying on frameworks.
Its all well and good saying that, as long as you do not value your time.
Personally, I would rather use a reasonably up-to-date framework such as Bootstrap 5 because Bootstrap has already taken care of the majority of those CSS hacks that are often required to make things look right on various browsers.
And frankly, why re-invent the wheel ? Most "utilize modern css and js directly instead of relying on frameworks" likely ends up looking like "a lot of boilerplate with a few customisations". So why not use Bootstrap for all the boilerplate and spend your time more productively by focusing on the customisations ?
P.S. JS is not a strict requirement for Bootstrap, it can be used CSS-only. But one added benefit of Bootstrap 5 in particular is they've removed the jQuery dependency.
Tbh if you’re not a guy whos not full time doing web dev then you shouldn’t say that. I’ve known html since 1997, and basic js since 1999. It’s exhausting as hell to keep up with all the crap the field keeps making up. I just want a page that looks simple, neat, responsive and shows what I want my users to see. Bootstrap has been the only consistent thing that has allowed me to do that. It allows me to spend a day or half designing the page so I can get back to the data and the backend which is where the magic happens for most people.
> This. I wish more devs tried to utilize modern css and js directly instead of relying on frameworks.
Making any large front end application WITHOUT a framework or a view library is just a bad idea, even today. There is nothing in the DOM or spec-wise that is equivalent to the power of React or Vue, period.
When it comes to CSS, the situation is better. Flexbox, CSS grids, ... have made creating CSS layouts extremely easy. So CSS kind of successfully brought in a lot of things that were directly exploitable by front-end developers.
To this day, HTML and the DOM are JUST NOT RAD for complex UI, period. Web components have a few nice ideas but a lot of flaws (especially support on IOS). Whether you build your own framework or use someone else library, you will absolutely need something that sits on top of the DOM for large front-end applications.
So it's not by choice that most front-end devs have to rely on a framework. It's because the standards are not good enough.
> I try to do this for my own projects but there's gravitational pull toward frameworks in companies.
A simple example. you need a mechanism to manage the life cycle of event handlers on your page, if your app uses the history API. If you do so then you've already started writing your own framework.
Web components failed to address a lot of stuff developers use view libraries for. That's why it is not that popular.
If CSS was not a hack upon a hack I'd be with you but going back to the early 2000s I must have wasted weeks trying to debug obscure CSS corner cases. Yes, we now have flexbox and css grid to replace CSS-P but that has to work with all that came before it. Anything which reduces the time sink of messing with CSS is a blessing.
Yea, I like to use a framework. But I think devs should have the basics down about css. Like margins, padding, div vs. span, etc. I remember reading a css book on vacation in Aruba like 10 years ago, and just having the basics helps considerably, especially when just trying to debug small layout changes.
1. Invent a problem.
2. Market like crazy to make people believe that there's a problem.
3. Charge for a solution to a non-existent problem.
4. Repeat.
You said currency, vast majority of marketing around cryptocurrencies market it as a store of value, not a currency. I'd very much like a decentralized currency.
So I made a small tool that lets you assign categories to transaction CSVs. This is something I come across fairly often while running my small business and I use when preparing taxes. It's free, doesn't cost anything and hope it saves you time and you'll find it useful.
https://categorize-bank-transactions.com/