I say to myself I'm a little bit autistic. But I'm not really sure.
I fit the profile of person one in the article.
The reason I'm wondering / even looking at autism is because the meds for my ADHD just make everything worse even at really small doses and I don't really know what to do.
Yeah, there seems to be a bit of overlap between ADHD symptoms and being anywhere other than the extreme neurotypical end of the autism spectrum.
As an ADHD person, one thing that has helped me a lot is listening to ADDitude Mag podcasts[1]. Listening to people who are experts in the subject and are ADHD themselves has been quite validating. Like, yeah, we're not stupid, but the normies sure make us feel that way sometimes, huh! I recommend the ones with Ned Hallowell, especially.
So maybe you're not ADHD, or maybe you are but that's not your main problem. There are probably similar podcasts or forums or communities for people that are 'weird' or mildly disabled in other ways. I guess I'm trying to be helpful because I relate, and I know how alienating it can be, but the best I can come up with is to quote Timothy Leary and say "find the others." Easier said than done. You can talk at me if you want. :)
I really think that is an incredibly divisive and reductive way of looking at people. In my experience, everybody has mental problems, but you usually don’t get to learn of someone’s individual struggles unless you are very close to them.
I am guessing you have a job, and maybe you dislike how you feel others judge you for your personal difficulties with your symptoms. You appear to judge others, who have their own personal struggles with their own quirky symptoms, perhaps which you don’t empathise with because they don’t happen to have ADHD?
Well, maybe that was a bad choice of word on my part. I don't think of the majority of humanity as being judgemental assholes. Most of the people that I actually interact with are nice and understanding, because everybody's got their own set of problems, and we can use all the mutual understanding we can get. But there are certain people, especially in positions of authority, that are able to turn their ignorance and lack of imagination into /my/ problem (teachers I had decades ago, or grandboss at previous job, for example, which is part of the reason I am currently /not/ employed). I'm really complaining about systemic problems, not individuals.
> I really think that is an incredibly divisive and reductive way of looking at people.
This is actually one of the problems in neurodiversity discourse, too: neurotypical doesn't actually qualify as a neurotype, and probably no one is neurotypical.
FBA only exists because market dominance makes FBA style shipping arrangements profitable. Without Amazon's scale and marketplace dominance, that shipping and pricing doesn't work.
Market dominance exists because they offer a better service to the customer. It's not like Amazon has always existed in Italy and always had a dominance position. They gathered their position because they offer a better experience and people are willing to pay a premium for that.
Isn't it the opposite? They have so much money from other markets, that they can take over a new market suffering losses for years, but pushing out everyone else.
I spent some time with a computer refurber back in the day. He used to buy old computers from mining operations these things were literally filled to the brim with dust and weird shit.
Computers are amazingly resilient if you don't need them for much more than office work.
This sparked a memory of an internship I had where I was given an air compressor and had to go blow out machines in various school computer labs for a few weeks. In hindsight I should have worn an N95, they were nasty. They all worked, though.
> but don't need clustering or failover strategies.
Even for those cases where you do need it, there are emerging options. You can handle replication 100% in business logic (something I personally enjoy), or you can use a path like dqlite to replicate the physical WAL log.
Why so? I have the impression every developer relies on it for a lot of local stuff, and many libraries also use it locally in users' machines for persistence needs.
I think they have this perspective because SQLite is almost never mentioned when DBs are discussed. Almost everyone pushes postgres, which I think is often a bit insane. Postgres or (often rarely) MySQL is given as the answer to most DB questions, even when coming from clearly new devs.
It's not often that the dev needs any of the large amount of setup/permissions required for postgres/MySQL. The fact that SQLite comes as part of python's standard library should be used as second nature for most devs.
I feel the same way - that SQLite should be the default answer, and one should reach towards postgres or MySQL unless you really *have* to.
SQLite is not meant to compete directly with MySQL or Postgres. It's meant for local usage only, where you don't need high concurrency, managing multiple connections, replication, etc.
I mean, you could probably use SQLite in many simple cases which currently use Postgres (personal servers, small apps), but advocating it as default solution is inadequate at best, if not misleading to people starting out in the field.
Most of the answers I was referring to are miles away from those requirements. Postgres fanbois love to suggest it for everything - for which ahuge percentage of the time is simply 'This csv is too big, how do I load part of it?'.
The suggestion of Postgres is very often not required, because there isn't a need for multiple users, different permissions, password protection, etc.
SQLite is a file format with a SQL engine which makes it a great embedded database.
It is not an RDBMS in the true sense so in my opinion it is correctly rated.
I tried using SQLite to solve problems which normally would require an RDBMS and ran into so many issues like the lack of enforced static types, built in date or decimal types (and fast aggregations on dates), concurrent writes, etc. It’s only when you’ve gone through this process that you’ll realize that SQLite it not the database you think it is — and SQLite itself is up front about that: https://www.sqlite.org/aff_short.html
I keep a daily log of what I work on, i also drop other info links and notes.
This is mostly to facilitate daily updates in lieu of stand ups.
Another thing I do along side my todo.txt is log important team changes, team switches, people encounters, side projects and any major project milestones that might be useful to point out in my 6 month reviews.
It's really amazing to search back and find links to things you did months ago when search won't pick it up.
I dunno if y'all realise this but I'd pay for a search engine that black holes CloudFlare and any other sites that think bots shouldn't read their sites.
I aim for "small images" because downloading a full install of Ubuntu is rediculous on anything but gigabit fibre.
But I don't aim for minimal images. Using alpine and installing what ever you like without worrying about all the bullshit to make caches stay empty still results in images only a few megs, don't need to do much better than that.
Though I tend to agree, if you're talking about a compiled language. Static binary and there is little need for anything other than `from scratch`.
FWIW, this does not match my experience. I have caught lots of bugs with unit tests, especially in code that is fundamentally complex (because it does complex things, not because it needs polishing). OTOH, refactorings often span units because real simplification comes from changing the ways units interact, or even which units exist, so the tests have to be changed anyway.
Granted, even tests that have to be changed have some value in securing a refactoring.
If you are writing tests to check new code in tandem with writing that code (either via TDD, or some other code-test loop), or are writing tests for existing code, you can (and usually will) find and fix bugs. Likewise if you are investigating a problem and write one or more test cases to check the behaviour.
Once those tests have been written, then they act as regression tests like the parent comment notes.
On "unit tests", I view the behaviour of the class/function and all its dependencies as a single unit for the purpose of testing. I've never liked the idea of needing to mock out a class in order to test another class, just because the class being tested makes use of it. The only case where mocks/stubs/etc. should be used is when interacting with an external component like a database or HTTP API. -- You don't see people that do this mocking out a list, string or other library classes, so why should project classes be any different.
To clarify, when I wrote "the ways units interact", I was referring to units that represent external dependencies in some kind (often a database, as you said). Many refactorings change those interactions in some way.
I agree that there is no reason to mock data containers or other classes with fully self-contained behaviour.
I fit the profile of person one in the article.
The reason I'm wondering / even looking at autism is because the meds for my ADHD just make everything worse even at really small doses and I don't really know what to do.