605 karma · joined May 21, 2012
edit: ok maybe not so unintuitive after all, try
label:"ghost box"
then look at the albums.
Plenty of people think their job sucks or feel like they don't have enough time to focus on the things they love, but if you are having genuine thoughts about suicide, you DO have options. Even if things seem hopeless and you can't see a way out, things can improve for you. Don't give up on yourself :)
Mentorloop is a Melbourne-based start-up making mentoring relationships easier to start, run and participate in. At a high-growth stage, we’re seeking an experienced developer to work closely with our small and dedicated team to take Mentorloop to the next level.
Our SaaS product is full-stack JS, so we're looking for a talented developer to help bolster our small team. The ideal candidate would be comfortable working with Node as well as the front end, but if you're an excellent dev that specialises in one over the other we'd love to talk to you too!
Our tech stack includes Node, React, RxJS, MongoDB and AWS. If any of this appeals to you, reach out and get in touch.
Details here https://mentorloop.com/job-full-stack-developer/
Salary is commensurate with experience, we're happy to negotiate to get the right person for the role.
Mentorloop is a Melbourne-based start-up making mentoring relationships easier to start, run and participate in.
We're currently looking for a mid-level full stack JS dev to join our small, friendly team.
Successful candidate has experience with:
- Node backends
- Single page apps with React & friends
- Building mobile-first UIs
Full details at https://mentorloop.com/job-full-stack-developer/i sort of forget about the keyboard until i use my old macbook pro and remember what i'm missing out on. and even that one was a step down from the previous gen.
Not saying it's likely, just something that he should probably attempt to disprove before declaring that the Uber app is sneakily using your GPS after you tell your phone to turn it off.
> there is a red push pin right on top of literally the room I am sitting in in the house using Google Maps Satellite View.
why not step outside and try again, see if it moves. or is that room just where he spends most of his time with the phone location services turned on connected to wifi...?
- Meteor uses MongoDB as a data store
- You write queries on the server called "publications", that make documents available to the client
- The client implements "MiniMongo", which basically lets you query the documents that have been published via your publications using Mongo queries as if you were writing them straight from the server
- The publications are (by default) reactive, so whenever any of the documents in your queries is added/removed/modified, the changes propagate instantly to your client.
- The original view library (Blaze) would seamlessly update with these changes in your UI.
From memory, the performance bottlenecks here are:
- It uses the Mongo OpLog to determine when changes have been made to the collections, which makes the queries themselves quite slow.
- For every dataset published to the client, Mongo keeps a cache of that dataset on the server so it knows when it needs to send deltas over the wire.
So for both of these reasons, once your queries get big, they get SLOW.
The other thing that is costly (but not fundamentally a fault of Meteor itself), is that most people building web apps model their data in relational terms. If you try and apply that to Mongo, (ie, treating collections as tables and "joining" across them instead of nesting data hierarchically inside your documents), you'll end up writing slow queries.
The releases since 1.3 have definitely pushed it in the right direction:
* NPM instead of atmosphere
* React/Vue/whatever instead of Blaze
* ES Modules (import/export syntax) in place of global variables everywhere and a dependency loading system that i-shit-you-not came down to loading things in alphabetical order
* ESNext support
* Getting Node and NPM up to current LTS versions
Next stop on their roadmap is integrating Apollo, at which point it'll basically be a turnkey system for building React/Vue apps on top of GraphQL. Most of what originally made Meteor what it was will have been removed in place of sensible best practices that everybody else in the JS world has since moved on to.
But for me the sticking point is that Meteor is built on a couple of assumptions that, in my humble opinion, are fundamentally incorrect.
1. Focusing on writing code that runs on both the server and the client is a useful idea.
2. MiniMongo is a sensible way to handle the data layer and reactivity everywhere is helpful.
I personally reckon these are both crappy ideas, and combined with the "magic" parts of the framework, they encourage people who are new to full stack JS to develop bad habits and skip learning some of the real fundamentals that every developer should know in relation to security, performance and scalability.
Feel free to fork or borrow or contribute!
So I recently wrote a CLI in Node that takes a URL and a CSS-style query selector (ie, '.album-title'), then scrapes the page, searches for each found instance and adds them all to a spotify playlist.
github.com/markreid/scrapify
thanks for sharing :)
https://www.amazon.com/Rise-Warrior-Cop-Militarization-Ameri...
yeah i had a discussion with a friend recently to this end. they were making a bunch of arguments against the internet that seemed to just as easily apply to the printing press.