SQL All the things!
-
Your experience?
I introduce some changes they saw as a nuance, as something to hate me for wasting my time doing it, then 2 months and now it is integral to our process. I tell them some other suggestions, they ignore only later to hear it back from their precious outsourced contractors and now it is a good idea!
Funny, I guess my changes are going to stay but now that I started looking I will not. This would be my job hopping experience, just waiting for the right offer.
-
I should be doing something else that needs pro-bullshitting skills.
Always tell the truth, just twist it a little. You could tell him it was a recruiter who cold called you from LinkedIn.
-
This would be my job hopping experience, just waiting for the right offer.
Sounds like a good idea.
I introduce some changes they saw as a nuance
A subtle change to the feel of the code perhaps?
Side note: I really hate the emoticons. I'm just going to start writing out the words 'colon pee'.
You could tell him it was a recruiter who cold called you from LinkedIn.
... but turned out to be a scammer who tells you your account is flagged as fraudulent or something. Lol.
-
Side note: I really hate the emoticons.
EmojiOne emoji do suck; the Apple* set is much nicer
That's what it's labelled as in Slack
-
-
As expected they want to do everything in SQL even though Elastic search is infinitely better. Waiting til payday and then I am handing my notice in.
-
even though Elastic search is infinitely better
Biased much?Seriously, if you want us to empathize with your struggle to make this shop do things the One True Way, you'll have to give us enough to show why your way is appropriate and better than the others. Otherwise you sound like @Carsten_Haitzler. All I've seen is a push for Big Data tools, without anything that suggests this is Big Data data.
Also, their bikeshedding the schema before they even have all their requirements nailed down is still a big WTF, and I empathize with that.
-
Two of the main selling points that elastic search claims on the home page is exactly what we want to do.
The argument of my boss is lets do it better later because we might not have time, which means we will never have time to do it right.
-
A subtle change to the feel of the code perhaps?
Crazy ideas like having source control and designing software and data structures instead of writing scripts and copying them to a network drive then asking coworkers politely not to change them
-
writing scripts and copying them to a network drive then asking coworkers politely not to change them
You could always commit them to git…
-
All I've seen is a push for Big Data tools, without anything that suggests this is Big Data data.
So much this.
OP @lucas - As a front end Dev, what has your experience been with large databases?
1 GB? 5 GB? 100GB? 1 TB? 5 TB? 50 TB?
Data of any of those sizes can work just fine in SQL Server (though for 1 TB and up, you really ought to be sure the database and hardware is designed well). Of course, perhaps you are dealing with huge transactional volume instead of pure size - maybe you have 6 million views per hour like Wikipedia (who uses a MySQL database sharded into 200-300gb servers).
"Big Data" sounds cool and sexy and it will solve all your problems. But do you know how much knowledge has been poured into RDBMS' over the past 40 years?
Have a detailed read here.
http://coding-geek.com/how-databases-work/NoSQL databases do about 1/10th of what most RDBMS' do. Have you thought that maybe the business leaders are interested in more than just a developer's "ooh this is shiny" mentality?
-
But do you know how much knowledge has been poured into RDBMS' over the past 40 years?
To many proponents of Big Data, using established tools with 40+ years of research behind them would be too boring. And something something performance.
-
ES is a specific purpose engine, like Sphinx, that solves that one purpose well, in a way that (at least) MySQL sucks donkey balls at, which is full text indexing and searching.
You can use ES for wider NoSQL uses but it's not really what it's geared for.
-
I know how SQL databases work. I wasn't always a front end dev.
I just don't think an SQL database is the best option for the scenario.
-
-
Good we are agreed
