That’s how I understand in this case merged = appended but yea that’s probably the confusion. I’m probably misunderstanding the argument, knowing myself.
1 Like
Mostly MySQL because that’s what I’m used to, but SQL Lite on one thing.
1 Like
It was pretty easy but I don’t have a lot to compare it with. I have used it on a PC and on Linux. On the PC have done it both on the Windows side and in a Linux subsystem.
1 Like
If it is a very simple project - a mistake a lot of people make is thinking they need a DB at all. You could just implement a very simple file based key value store. Or like a csv file - there’s plenty of csv parsers out there if you don’t wanna write your own.
2 Likes
In my one corporate programming job there was an Oracle database that we used in the beginning, but it was run by the database Department. It took several meetings and months to get anything to change even a single column in single table. I got my friend who was in the system’s Administration department to surreptitiously give me a Linux machine and we ran all our database stuff that didn’t need other people’s data on mysql from there.
1 Like
oh, in that case I would probably use a key-value store because it is the simplest type of database. I have never set up redis, but it’s one of the most popular ones.
If you want practice with a relational database, something like mysql server seems most popular, but I’ve never personally used it. My work experience is with key-value stores.
Do you guys do anything to work around the bureaucracy? It’s kind of amazing the lengths to which people will go to overcome the obstacles that management puts in the way. We had another project where my team, the web team had to interact with a totally separate team that did flash games and we could not get anything done going through channels and just traded favors.
Looking at hosted options if you’d rather go that way…
For non-relational k/v stuff, AWS DynamoDB is fairly straightforward to get started with, and is effectively free for light usage.
Or for relational, I think DigitalOcean does managed MySQL instances for like $15/mo. Certainly cheaper to DIY, but it’s easy to get started with if that’s what you’re looking for.
1 Like
I haven’t done anything like that, but I looked at it and I think that doing it yourself is just as simple.
There could be hiccups, and I don’t use a mac so I don’t know if there are any in particular for that, but if everything goes well you could have MySQL up and running and accessing it in like 30 minutes if you just follow the instructions.
What I would consider a managed option for would be if you had a lot of traffic and you didn’t have the time to worry about scaling up the machine if necessary or keeping up with security patches or updates or something like that.
The QA sounds like a frustration for your job but imagine how awful it is for the QA person.
1 Like
Imagine the QA person goes to their manager and says " my job is meaningless and pretending that I’m working and doing something useful everyday is making me want to shove an ice pick into my brain. Can I go find something useful to do?" The manager replies " no way, then I lose a direct report."
That’s Corporate America.
haha I am applying for QA engineer positions.
Hopefully the programmers at the job are really terrible and you’ll have plenty to do.
Well that was kind of my default position at my old job. We had no QA so I filled in. We had very good developers - but for some reason I can always think of a way to break something. It was kind of a joke that if I could not break it, it could not be broken (ofc not true). I just have a much different way of looking at test cases and I never use things how you’re “supposed” to use them because I am kind of a moron who mashes buttons. But I could usually find bugs, and then a really good QA will go into the code and find exactly where they suspect problem area is. That’s what I did anyway.
It’s a thankless job IMO because no matter what you’re probably gonna be aggravating people. Devs don’t like being told their stuff has bugs.
We don’t even have QA. Which means that the product owner, a director, is our QA. 
1 Like
ew manual testing. No I’d only accept a “QA Automation Engineer” position because then you work with the test framework and infrastructure. I just enjoy it and am really good at it.
1 Like
I am the product owner, dev lead, architect, and QA - even though we technically have people for product owner and product manager roles who are also supposed to do QA testing. But the two who actually knew stuff about the app left, and the PM is overworked on a bunch of projects and is aggressively slow to learn the app. We have a new product person but apparently she’s either incapable of doing this stuff or they want her on other things. It’s annoying.
Now my boss wants to go down the same road with another app. I told her I’ll do the lead/architect stuff but I don’t want to be the product owner/nanny who makes sure everything gets done. In part because I don’t want to do it - things get tense when I have to boss everyone around and lord over the whole project.
But also because I want to leave sometime this year. When I do I will be sure to remind her how I tried to make sure I wasn’t going to drop the bottom of of the project when I left. But you insisted on me owning everything. So now you’re screwed.
yea sorry I dont know what things are called. That’s what I want to do.
I didnt even know manual testing was a thing, that sounds legitimately horrible. I did plenty of manual testing but that was only so I could figure out how to automate it.
Back on the road. I want to see the whole world slowly, like how I saw Central America and Mexico. I will try to make a little money with contract jobs, live poker, and any other opportunity that comes up. But I don’t need to make much to float for a few years.
Here’s a thought I just had that applies to other things, but I think it applies to programming, it’s best to end the day right in the middle of something because it’s easier to get back into the groove the next day than if you finish something and have to figure out what’s next.