856 karma · joined December 6, 2009
Frequent speaker and author on tech subjects. Expert in building, scaling and maintaining complex web applications with Python, Django, React, PostgreSQL usually on Kubernetes.
Email: frank@revsys.com Twitter: @fwiles Mastodon: https://frankwiles.social/@frank Homepage: https://www.frankwiles.com/ LinkedIn: https://www.linkedin.com/in/frankwiles/ Work: https://www.revsys.com
- beltway.wtf
- startups.wtf
- recy.(link|co|in|info|io) as I had grand plans to do a link curation app
- saltmaster.net
- hostedsalt.com
Stories and situations like this is one of the reasons I accepted a board position at http://www.headquarterscounselingcenter.org/. It's very preventable with the right treatment at the right time.
What I'm getting at is that MOST of the time, even if a particular job lists off some particular tech, the ultimate customer is generally interested in a good working solution and doesn't care that much about the tech used.
Think of search engines like ElasticSearch and Solr as being purpose built for "search" rather than ad hoc querying.
They offer more advanced searching features like faceting and synonyms, if your example had been "SELECT id FROM pages WHERE title LIKE '%dog'" you could set things up so that matches for 'dog', 'dogs', 'doggie', 'puppy', 'pup', 'canine', and 'mans best friend' all returned the same results.
We quickly realized the app was going to be 99% Javascript anyway so using something like atom-shell started to make a lot of sense.
We originally were targeting just OSX and Linux desktops, but using atom-shell opens up a path to Windows desktops much more easily for us.
The app needs to display a large of amount of changing data from the local machine and atom-shell + ReactJS, so far, is handling it just fine.
Not saying you can't do it with Solr or that Solr doesn't scale, it does. You'll just have an easier and more fun time doing it with ES.
Couple of related/examples:
http://highscalability.com/blog/2014/1/6/how-hipchat-stores-...
Honestly I'd probably look for a new job, but with that option off the table #1 runs the risk of you looking bad doing the bare minimum and having truly failing tests that pass the suite. #2 runs the risk of you doing a ton of work for free only to get a pat on the back and maybe a "good job" email.
What makes your management tick? Is it happy customers? Frame the discussion with "We had 47 customer impacting bugs that were missed by the test suite last month." Is it cost savings? "My team spent 312 man hours last quarter fiddling with the test framework when you could have been moving the product forward or fixing actual bugs".
Just because it's not "customer facing" doesn't mean it isn't "customer impacting".
Keep in mind not everything needs to be that "real time" and it is also a horrible business decision to rewrite your core apps in the latest framework without reason.
That being said, I almost always DO separate them because over time your generic views often become more complex and more overridden. I also personally prefer my urls.py to not get so "messy", but it's not really a horrible practice or one with a lot of downsides.