noshbrinken

This tool will parse your local My Clippings file to JSON: https://github.com/maxhallinan/my-clippings-to-json

I can't speak to Typescript but check out the Flow types for Ramda: https://github.com/flowtype/flow-typed/blob/master/definitio...

Maybe just a matter of perception but it looks verbose to me.

Some (many?) slack bots will need to be updated.

>...what we call web frameworks are transforming from runtime libraries into optimizing compilers.

I took that to mean that the frameworks are doing the optimization. But the article doesn't give examples of the frameworks. The only examples of code transforming optimizations are Uglify and Babel. So I thought maybe these were the things the author has in mind and not actual frameworks. I was genuinely confused and prefaced with the aside about pedantry because questioning these kinds of semantics can come across as pedantic.

The second half of my comment stands regardless.

> The trend started by minifiers like UglifyJS and continued by transpilers like Babel will only accelerate.

Not to be pedantic, but are UglifyJS and Babel "frameworks"? Not a Ember user, so maybe Ember has some sort of built-in source code transformer and that's what the author is referring to?

I think the basic idea that JavaScript developers, especially those working in a browser environment, will increasingly write source code that compiles to JavaScript "bytecode" is not a recent idea. A much more nuanced reflection on that idea can be found here: http://composition.al/blog/2017/07/30/what-do-people-mean-wh....

With all the hand-wringing about "JavaScript fatigue", it's a little bit sad that prominent JavaScript developers use titles like "Compilers are the New Frameworks". The tone of this title is the tone of a bell ringing for the next round of JavaScript fad musical chairs.

I think you're missing the point. I don't think that Americans are losing faith in the value of education. Most Americans I know envy the low cost of education in Europe exactly because they would like the same conditions of access. Simply put, we want to go to school. But we don't want to sink ourselves into decades of debt to do so. Would anyone?

Individual known for benevolent acts arrested on charges of other, malevolent acts chills community of benevolent actors?

I definitely appreciated this early warning to get off the ride.

Thanks for the code snippets. That actually helps me to understand quite a bit how Elm's JSON parsing situation can be improved within the FP paradigm.

> So what you're frustrated with is that a group of likeminded individuals celebrates their common point of interest and doesn't make room for you to nay-say them?

I'm not frustrated with responses to criticisms I've made. In fact, I haven't made any criticisms (except of course, the ones in the last comment :P). So I don't have any experience of anyone not making room for me. But I have observed some smart people with well-articulated suggestions get shut down. It's not that their suggestions weren't accepted but it was the way that their ideas were received. I haven't actually seen someone who isn't Evan C. contribute something significant that isn't "doing X like Evan would do it." In the entire world of this language, there seems to be 1 architect and a community of implementers. Now, there's nothing wrong with being an implementer. I am an implementer. But it seems easy to see that cultures are healthier when there are a diversity of ideas.

I think that your characterization of the Elm community as a "group of likeminded individuals celebrat(ing) their common point of interest" is actually close to what I'm talking about. It's great when a programming language community is passionate about the language. If people enjoy using that language, it's certainly a good sign. But I wouldn't trust the judgment of a group of people who can't critique what they love and are unwelcoming to those who do.

The counterpoint here is Dan Abramov and the Redux community. Dan is continually pushing people to understand why they are using Redux and not to see it as a solution for everything. That kind of transparency, and the continual acknowledgement by Redux maintainers that there is more than one good way to do something, is the kind of intellectual honesty that I'm using as a standard in my assessment of Elm.

> How many Python tutorials stop midstride to browbeat you about how great Python's way of doing things is?

I couldn't say and it wouldn't change my opinion of Elm.

Unfortunately, CFS is not the only illness whose existence the medical profession generally refuses to admit. There are a host of other syndromes or symptom constellations that doctors can't find markers of and thus call psychosomatic. Generally, people suffering from these conditions congregate on message boards where they develop a culture and community. Sometimes this is truly productive research sharing and emotional support and sometimes it promotes alternative treatments of dubious efficacy and speculative science based on amateur readings of research. What's really overwhelming is the disconnect between the medical profession and the people they exist to serve. These people need help and yet doctors seem to push them away because doctors are too uncomfortable with a state of not knowing or not understanding.

I've wondered the same thing myself pretty much every time I've come into contact with a doctor. The fundamental lack of curiosity for someone in a field related to science (seemingly based on science) is astonishing.

Something I find incredibly off-putting about Elm is the evangelical and generally unbalanced tone taken by many prominent members of the Elm community. I almost never come across Elm advocates accepting a valid criticism of the language. The response almost always amounts to "you don't understand" or "yes, but". They spend a lot of time celebrating the compiler's humanistic virtues but seem less clearly humanist in their relation to original thinking or diversity of thought. So much of Elm community dialogue (in talks, in articles, in the Elm slack which I follow daily) is simply those with more experience initiating those with lesser experience into the "Elm way" of doing things. For this reason, Elm feels more like a framework with a domain specific language than a fully qualified programming language. And while it might seem like a gentle introduction to functional programming techniques, I'm not confidant that it really teaches people the concepts themselves nor gives them enough room to think critically about how to apply them. Instead, the task is to internalize and apply the "Elm way". The inability to even acknowledge the unprecedented labor required simply to parse a JSON response is a perfect example of the cultish mentality emerging in this community.

Thanks for adding redeuceur to your list! I didn't realize there were so many reducer utilities but I'm not surprised. I like the way Redux leaves room for the user to play with the implementation.

In the blog post you linked to ([2]), you say:

>Ah, the dreaded switch statement. For some reason, this is one of the most disliked aspects of typical Redux code, and I have yet to figure out why.

The Redux docs take the position that switch statements are an implementation detail. The documentation author(s) provide an alternative approach, the action type to handler map, in the Reducing Boilerplate section. I think Redux advocates get a little bit impatient with the criticisms of Redux that amount to "I don't like switch statements". I share that point of view. Switch statements are an implementation detail and aren't worth arguing about when the Redux architecture does not depend on them. When I came up with redeuceur, I wanted to isolate independent operations. For me, breaking a larger function into smaller functions means less cognitive overhead. I would have used the createReducer idea from the docs but I needed support for arbitrary computed conditions rather than a simple action type map. So, it's not about getting rid of switch statements but more about making it easier for my average mind to keep track of things.

All of that being said, are you sure you're not being disingenuous when you say "I have yet to figure out why?" The strength of the animus against switch statements in Redux reducers might be a product of received wisdom or unreasonable bias. But the additional cognitive overhead of things like `break` vs. cascading `case`'s, and `default` is a reasonable basis for preferring `if` statements or something more declarative. As near as I can tell, the original Redux examples used switch statements because they were aesthetically pleasing to the author. There's nothing wrong with this. But it shouldn't be a surprise that people prefer a construct with less complex behavior, even if the complexity of a switch statement is manageable to someone with solid JavaScript experience.

The last part of your comment blames front-end developers for the shortcomings of the web platform. I think many would be interested in a more uniform, stable interface. But they're not the ones with the power to change things on the protocol layer.

John Resig used Genius to annotate the jQuery source code. Seems to be broken now.

https://genius.it/johnresig.com/files/jquery-original.html

Great list! Thanks a bunch.

I like python_prompt_toolkit, though I think the learning curve can be a bit steep. It gives you a ton of flexibility, which I really appreciate, but I have a hard time remembering how all the pieces interact. I hope I don't sound overly critical of people's open source work, because I've used and really appreciate both Inquirer and PPT. Just seems like there's yet to be a canonical library for this problem set.

This is great. Exactly the kind of thing I'm looking for.

I think many/most Node TUI's use Inquirer. I have mixed feelings about it. Python has several library's that provide lower-level constructs for building CLI and TUI's. Then they provide examples for using the library to implement a common pattern or prompt. Inquirer gives you some ready-made prompts but doesn't provide any help/convenience for creating your own prompt. It seems like the wrong level of abstraction.

Thanks for pointing that out. I'm interested in both.

I love reading Dan Abramov's writing because I always learn two things at the same time:

1. something about programming;

2. something about communicating with people.

"How I Beg The Question That Mac Spaces Aren't The Same As Physical Monitors"

"Why Everyone Should Adopt My Personal Preference"

Someday I'm going to write a Medium article titled: "Why I Don't Care About What You Started or Stopped Doing."

If you decide to continue with this job, take it as an opportunity to learn two essential professional programming skills: estimating effort and managing expectations.

"production ready app in iOS, Android, website, and server setup as well as website/app design and logo creation and branding" in 4 months at 18 hours a week is an unreasonable scope of work, at least for me. I would not be employed under these terms unless my hourly rate was in the thousands or tens of thousands, and even then I would be concerned about the impact of four high-stress months on my health.

You are going to encounter these kinds of unreasonable requests throughout your career. The ability to explain in layman's terms and plain English why this isn't possible and to present an alternative is invaluable and it's part of what you're being paid to do. It is always better to risk disappointing the client in the beginning, by having this conversation, then it is to disappoint them in the end, by failing to deliver.

It sounds like your approach is already very proactive and productive. Don't underestimate the value of persistence. I spent a year teaching myself to code. I was able to get a foot in the door through an internship at a NYC agency. This came after several months of fruitless applications and one freelance gig that ended because I didn't know enough about WordPress. I was dog walking in the meantime. Now I am a software engineer. Truly entry-level positions are (in my experience) hard to find for a new web developer. Once you have your first professional experience, internship or junior position, you will receive more interest from prospective employers. Unfortunately, the lack of entry level positions means that you have to have patience and persistence in the beginning. Believe in yourself. Trust that you made the right commitment. Keep at it. I did little things like buying clothes that I was going to wear when I finally had my first web dev job. I didn't wear those clothes until the first day of my internship. By investing in that future, even in silly, little ways, it helped me to believe that future would be a reality.

If you're in NYC, check out the BoroughJS meetups. I don't know if this will help you find a job but I think it will help you to feel part of the JavaScript community. You are part of that community if you choose to be, even if you don't have a job. People there will (in my experience) take you seriously regardless.

Finally, a word on bootcamps. I've interviewed several candidates who graduated from bootcamps. Some are great. Others are not. I think the attitude generally is that a bootcamp listed on a resume isn't an indication of anything. If this is one of the primary ways you define yourself, I would deemphasize it. Instead, emphasize code you've written (in the form of Github repos, Gists, CodePens, live sites, etc.) and communicate that you think like a programmer, even if you don't have a lot of experience. These are the two things I focus on when interviewing junior candidates.

I've had the exact same experience with American doctors. What is that? These people are supposed to be scientific thinkers. They've had years of biology. But I've never met a doctor who applies the scientific method, or cares to. They are a fundamentally uncurious bunch.

Sponsoring visa's for foreign devs would be a huge incentive, I think. Many people would like to live/work in a foreign country but find it hard/impossible to do so without an employer sponsoring their visa.

- Did not educate myself about market rate for my position.

- Did not negotiate compensation.

- Over-identified with my work.

- Trusted employer to match my level of selflessness.

- Underreported hours worked.

- Did not limit the number of hours worked in a week.

It's comforting to find other Hacker News readers who have experienced stress-induced cognitive impairment. A recent mental breakdown eroded my cognitive abilities. One of the worst aspects of this experience is the feeling that I'm no longer good enough for the work, the communities, and the discourses that are the primary passions of my life.