432 karma · joined October 29, 2014
I think its an acceptable strawman, as often we do need to remind ourselves that, "No one but me is actually forcing me to [live here / work here / see these people ]".
When they move to the city, they don't really want to live in the city. They want McMansion suburbanized city with a bar scene...
Maybe a better tact at why JavaScript first: people are far more likely to hire junior front end people than junior backend.
- unzip the .docx file into xml files
- parse the xml into something organizable by line (csv? etc)
- commit this other file format
- in the GUI of your app, when someone selects a snapshot in time, go from the by line (csv? etc) format back to .docx
- open in word
- profit
(way back when we did this with excel, but ultimately gave up https://github.com/decisive-wizard/GridHub)
Seems related to: "MVP" --> "the rewrite / second system"
this equation is often true for non-family people I know: SFRent - EBRent <= OwningCar
for family people renting bigger spaces, the equation then might look like: SFRent - EBRent >= OwningCar
Much easier than vagrant or running everything manually.
I'm calling BS on that last statement of hers. I don't intend for this to sound mean. I intend for it to help her (or readers), to be honest with themselves. It WOULD be sad if she wasted all this time on SVG if she really would have rather just been building stuff with SVG. However, that to me doesnt reflect reality; so it shouldn't make her sad. She got to spend time doing what she clearly actually likes doing: technical writing! Theres nothing wrong with that!
No one who actually likes to build stuff would spend so much time on committees, book deals, and technical writing. Thats okay! She should be honest with herself about her preferences.
The positives are that "committees, book deals and technical writing" are very transferable skills to whatever other web technology needs more of this sort of thing.
EDIT: I in no way mean for this to be callous regarding counting pennies. I am sympathetic to the fact that much of her work was unpaid :(
I find this to be the biggest issue. Specifically, the "best" time to write tests is also when the code is least likely to be stable!
It's easy to think "if we had just started writing browser tests when we had fewer features, we could have kept up with a testing suite". But that means your browser tests are constantly breaking and people just give up on them. The app eventually gets big enough, and has enough users, that you have to bolt on the tests later to keep bugs from hurting too many customers.
This seems problem seems to be way less of an issue with regular unit tests. I guess the lack of changing dom selectors would be a big reason why.
Specifically, you could use postgresql for the edge traversing and its jsonb column to store searchable attributes.
Parent comment says: if `(former programmer) turned manager` is more equal in gender than `programmer`, that might mean there is a sorting function that is pulling women out of engineering and into management.
His/her hypothesis is that being a "regular dev" is not very socially respected, and thus, pushes women to want out at a higher rate than other professions, like say, Doctor.
The fact that Doctor gender ratio is similar to Manager Doctor gender ratio, actually fits his hypothesis.
Not saying I disagree with either of you, just re stating.
Kant and his Critique of Pure Reason has those 4 quadrants of "knowing". A priori vs posteriori. Synthetic vs analytic. Its literally a CRITIQUE of how far pure reason can take us. In the area much of philosophy dances in, pure reason simple cant take us very far!
[0] https://en.wikipedia.org/wiki/Analytic%E2%80%93synthetic_dis...
Finding "a" reason to live matters far more than finding "the" reason to live. Would we rather be happy or would we rather be right?
I like this quote attributed to Kant: "Rules for happiness: something to do, someone to love, and something to hope for".
It's highly likely I'm being too harsh on him. I probably have baggage from having read a lot of this kind of stuff and having it leave me less than satisfied. My apologies.
Perhaps what bothers me is that he spends a lot of time tearing down and differentiating from others, and less time telling us what he actually does believes in.
The word gymnastics used on that site to disqualify "everybody else's muddled middle" except for his own personal version of a "muddled middle" seems hypocritical. He talks in enough circles, and we are supposed to forget that his muddled middle is pretty much all the other muddled middles he says can't work.
I wasted so much time reading philosophy stuff in college. Its like a virus that infects the mind, "there must be a RIGHT answer!" and the infected mind goes in circles arguing with itself. Its an infinite recursive loop without a base case.
The base case is this: "would you rather be right or would you rather be happy?" its not meant to mean that we should all get on "brave new world" soma. what it does though, is get your mind out of that infinite loop of "i must know the RIGHT answer with certainty!". These sorts of topics have no certainty. They are topics worth considering, but trying to find "correct" is just missing the forest from the trees.
Python (and its type system) + Go routines
Where can I find that!?
I'll admit im not sure.
Being the creator or top two contributor of a library is now worth so much more than being a small time contributor that the incentives are skewed towards everyone just making a new thing, always.
It's their way to stand out.
So why is this more prevalent in JavaScript? Front end inherently has more new comers. Long time hackers or cs grads feel less of a need to prove themselves making free software?
I think it's natural that the web programmers would understand web self promotion better than other languages. Guess who's better at Twitter? The js people! Why? They were writing the web to begin with!
I wish it would stop. Our qa engineer is writing web driver tests in JavaScript and I don't understand why! There's nothing about testing that NEEDS to be async! The python API would likely be no slower and much easier to write and debug.
Sane defaults are an important part of tech, and default async is a terrible setting. Python sync is easier, and Go routine concurrency is easier. Always on async just seems like a terrible default. For speed I'd do Go, and for all else Python.
Cool to read it all laid out why we like certain games so much more than others.
Also, interesting to note that in the olympic / NCAA 50 yard and 50 meter freestyle, a drag race, usually people are not kicking to 15m. So perhaps underwater is only faster with effeciency in mind. With a short race like the 50 free it's possibly still not the fastest. It's similar to how fly is as fast as free swimming at short distances. It's the inefficiency that makes fly end up slower over a 50/100 vs freestyle.
Shit game everyone plays: clash of clans.
Basically, there's more non gamers than gamers, and more mkney in skinner box candy crush than good old school games. So the game makers sold out.
It's like how people think dark souls or Bloodborne is "too hard" to be fun. It's exactly fun because you have to try and not just do endless todo list quests!
I actually turned off the TV and finished the entire article. Its amazing to think how rare it is for me to actually read an article and not just SKIM. Maybe its not that amazing. Most articles just aren't worth more than a skim. This was so enjoyable I was disappointed that it was over. I'd read a book like this...
Favorite line:
> The hashtag unleashes a stream of photographs featuring people I’ve never met — beautiful people, the kind of people who look good in athleisure.
I had intended the api to be entirely programmatic and allow others to build GUIs for how they wanted, say, font size drop downs to look. I could host the test html page I've been testing it with. It exposes some random styling buttons and visualizes the data model below the rendered text.
My favorite idea was using independent ranges data objects to track styling. Eg {start: 2, end: 3, range: color, value: blue}. Then only the rendering api needs to worry about overlapping ranges. Basically avoids manipulating trees. That's partly what makes content editable suck so much.