freeCodeCamp

I was wondering this too a few years back when serverless started to gain traction. I remember thinking it sounded like a lot of mock infrastructure. Just did a search and found the following links interesting: https://medium.freecodecamp.org/the-best-ways-to-test-your-serverless-… https://github.com/lambci/docker-lambda It seems non-trivial to set up at this point EDIT: Still reading into it... https://serverless.com/framework/docs/providers/aws/guide/testing/ Would love to here a best practice case study from someone who has deployed something like this

This was a good read, along those lines: https://medium.freecodecamp.org/how-i-replicated-an-86-million-project…

I am a data science freelancer/consultant (background story and motivation: http://p.migdal.pl/2015/12/14/sci-to-data-sci.html). But in my case, it's purely recommendations and people contacting me (it takes some time to build it, though). Freelancer websites look like a race to the bottom. Some links I gathered: https://pinboard.in/u:pmigdal/t:freelancing. Plus, price negotiation is super important (way more than for regular jobs). I recommend "Ten Rules for Negotiating a Job Offer" https://medium.freecodecamp.org/ten-rules-for-negotiating-a-job-offer-… Look at https://brainpool.ai/ (they offered some good contracts). In general leveraging one's PhD and credentials is a good strategy.

It’s not an existing site, but any of the ‘make a blog in 15 min’ tutorials [1] will get you to working code examples quickly. The Elixir build utility `mix` has great tools for creating new projects and the example project will scale easily into what you want to try. Also, GenServer’s are a good way to retrieve _and_ cache the data from the other http server, following the KV supervisor tutorial would be a good starting point. 1: https://medium.com/@kacpx123/phoenix-1-3-simple-blog-api-and-postman-t… 2: https://github.com/learnphoenixtv/blog 3: https://medium.freecodecamp.org/simple-extensible-blog-built-with-elix…

He addresses this in a follow-up: https://medium.freecodecamp.org/remember-that-86-million-license-plate…

For editing, one thing that has helped me is learning sales copywriting and direct response. Copywriting forces you to trim the cruft and makes you take the reader's perspective. Their time is valuable so you need to be entertaining and engaging, AND you need to get to the point fast. Tested Advertising Methods & Scientific Advertising are just some of the classic books about sales copy. I don't know what topic you're writing about, but sometimes you really just need to get your work out there, despite it not being perfect. I spent too much time writing and re-writing this article on procrastination (https://medium.freecodecamp.org/procrastination-sucks-so-heres-the-eat… till I finally said "f--- it, I'm going to write this last section about finishing and shipping, then hit the publish button"

I like this list if you add one more point (that happens the most important one): * the solutions she comes with are easily explained and understood by everyone working on the codebase. Stories like this: https://medium.freecodecamp.org/we-fired-our-top-talent-best-decision-… are all too common.

I'd say good code is as easy to understand as possible (note, not always easy to understand as not every domain lends itself to that). The part about attracting other world class developers helps with this as everyone will be on the same page. > Stories like this: https://medium.freecodecamp.org/we-fired-our-top-talent-best... are all too common. Maybe for some people but I've never had issue with it. Managing top talent is definitely its own skill though. One of the challenges is integrating them into the team and not having other people upset when they get high profile projects. It's not trivial but it is doable and in my experience, well worth it.

Here are a couple great articles about code review that I've learned a lot from - they address the 'social' aspect of code review specifically, which I think is where you're having a hard time finding traction. - https://blog.plaid.com/building-an-inclusive-code-review-culture/ - https://medium.freecodecamp.org/unlearning-toxic-behaviors-in-a-code-r… The takeaway is that it's a communication problem, and one of the first steps is probably setting some shared expectations. As others have mentioned, if you can't get alignment on expectations, you're not going to be happy in your job, but hopefully there's common ground somewhere, and you can all help each other level up technically and as a team.

I really enjoyed working at Shazam. One of my favourite parts were the hackdays, got to learn a lot. Here's a write up of visualising music recognitions: https://medium.freecodecamp.org/data-visualisation-with-1-billion-shaz… I've been planning to do more write-ups from past hackdays, such as building a functional Shazam experience in client side JavaScript and other visualisations. For example one time, I repurposed a WebGL globe to plot music recognitions over it. I don't have access to the Shazam tag stream anymore, but you can get a feel for how this looked as I've applied near real-time Wikipedia edits on the globe instead: https://umaar.com/globe/

The Developer's Guide to Interviewing has some great ideas: https://medium.freecodecamp.org/how-to-interview-as-a-developer-candid…

Previous discussion: 173 points by ivank on Jan 30, 2017 | 55 comments https://news.ycombinator.com/item?id=13518919 Great concept, do you see it coming? edit: there's an update with a more detailed implementation here: A Spacial Model for Lossless Web Navigation https://medium.freecodecamp.org/lossless-web-navigation-spatial-model-…

> And the scary syntax is all in the Rust world. JavaScript is heading in the direction of Haskell, Scala, and (to a lesser extent) Rust, too [1]. [1]: https://medium.freecodecamp.org/here-are-three-upcoming-changes-to-jav…

The same kind of report, written a few days after releasing a self-published open source book: https://medium.freecodecamp.org/taking-off-the-successful-launch-of-an… Nine months later, the book earned a little more than $3,000 in Leanpub royalties. Like other said, marketing is definitely the hardest part, especially if (like me) you had no initial audience. Since the book is free to read on GitHub, I hoped word-of-mouth would be enough to make it widely known and popular. Boy was I wrong. The experience was worth it for a number of reasons, honing one's skills being the number one. That said, would-be authors without an existing follower base should prepare themselves for a multi-year commitment in order to reap any significant rewards.

Excellent counter article "Design tools are running out of track" speaking of "We are all just drawing pictures. It’s insane...Our products are interactive. Our tools are static." https://medium.freecodecamp.org/design-tools-are-running-out-of-track-…

To add to the link pile: A Study Plan To Cure JavaScript Fatigue - https://medium.freecodecamp.org/a-study-plan-to-cure-javascript-fatigu… The author recommends this plan: Week 0: JavaScript basics Week 1: React Week 2: Building a React project Week 3: Mastering ES6 Week 4: State management (Redux) Bonus: Building APIs with GraphQL So pick and choose from all the links here and just study them depending on the week. To kick you off, I'd check out Wes Bos (Javascript30 guy). For more in depth stuff, dive into You Don't Know JS. Have fun!

Here are three excellent article. I think that you should read them in the following order: https://medium.com/the-node-js-collection/modern-javascript-explained-… https://medium.com/@parsyval/javascript-prototype-vs-class-a7015d5473b https://medium.freecodecamp.org/here-are-examples-of-everything-new-in…

Hey, I didn't mentioned it in this article because I have another article dedicated to serverless-express (https://medium.freecodecamp.org/express-js-and-aws-lambda-a-serverless… also we dedicated whole chapter of our book to it too with explanation how does it work, etc. (livebook link: https://livebook.manning.com/#!/book/serverless-apps-with-node-and-cla…

Rick. https://medium.freecodecamp.org/we-fired-our-top-talent-best-decision-…

There's a lot of courses in Massive Open Online Courses (MOOC) [1] site which you can dip your hands first to try to learn some technical stuff. You can also go to the Free Code Camp[2] where you can get some real-world training in software development. They have a lot of stories[3] as well showcasing people who were self-taught and now have stable careers in the technology field. Career opportunities would come as soon as you have showcased that you are capable of learning and solving technical stuff. But you got to start first by learning the ropes of software development. Best of luck. [1] http://mooc.org/ [2] https://www.freecodecamp.org/ [3] https://medium.freecodecamp.org/inspirational-success-stories-from-sel…

...instead of hand-rolling as per e.g. https://medium.freecodecamp.org/you-might-not-need-react-router-386736… ? Asking because I'm just getting into React, and not really clear on best practice yet. You seem to know a thing and have an opinion; will you share them?

Yeah, there's some truth to that. There was actually a good article and related tweets by Justin Falcone a few months ago on that topic [0][1][2], which are excellent reading. That said, I'm always looking for ways we can make it easier to get started with Redux, improve the learning process, and make the ecosystem better. I filed an issue earlier this year to get community feedback and discuss how we can simplify things [3]. Please feel free to add suggestions to that issue. I'm also always open to ways we can improve the docs as well. [0] https://medium.freecodecamp.org/whats-so-great-about-redux-ac16f1cc0f8… [1] https://storify.com/acemarke/redux-pros-cons-and-limitations [2] https://twitter.com/modernserf/status/886426115874717697 [3] https://github.com/reactjs/redux/issues/2295

This statistical analysis[1] of review websites suggests that the scoring and review systems everywhere but Metacritic are somewhat flawed because they do not follow a normal distribution. Of course it starts with the ground truth that movie quality follows a normal distribution, but that’s not a terribly difficult supposition in the first place. [1]: https://medium.freecodecamp.org/whose-reviews-should-you-trust-imdb-ro…

It depends a lot on why he wants to know, what he wants to do, and how much detail he's looking for. Look, I did a search for you: https://www.google.co.uk/search?q=bitcoin+eli5 Since I have an irrational hatred of Reddit[0] I then followed it up with this: https://www.google.co.uk/search?q=bitcoin+eli5+-reddit This seems to be the best explanation. https://medium.freecodecamp.org/explain-bitcoin-like-im-five-73b4257ac… Here's another with a different slant: https://medium.com/@suchconor/eli5-how-does-bitcoin-work-29eadc989369 Hope that helps. Will you return and tell us how you got on? ======== [0] It's irrational - don't try to understand it or convince me otherwise.

Good CS fundamentals are important https://medium.freecodecamp.org/welcome-to-the-software-interview-ee67… Yes, I can see the confusion. You see, we are looking for the very best Translators, and it has been proven by major companies that the people that are able to do the job best have a very solid foundation in the science translation is based in, such as Linguistics and Classics.

This is Quincy with freeCodeCamp. Congratulations on your new job, and your diverse portfolio. Getting a job as a new developer after only 4 rejections is a great batting average. Sean Smith rejected 192 times before getting a job at Trustar. https://medium.freecodecamp.org/how-i-learned-to-code-and-earned-a-job…

The right number is zero and a UBI until they figure out how to stop being jerks. (My primary personal reason for supporting a UBI is I want to be able to say "No rational employer should employ you" without that implying "so you should be homeless and starve.") But short of that, the right number is zero on the interview circuit. You can employ jerks if you have to, but don't put them in more positions where they have to interact with others than necessary. Give them the legacy products where you can't staff a team of more than one qualified person anyway. Give them an office. And keep the door closed. Remember that a jerk is basically a 0.1x developer - an employee who causes other employees to lose productivity by spending time working around the jerkiness, taking a morale hit, etc. Even a remarkably productive jerk at best only compensates for their negative effect on people they work with, and most jerks are not consistently remarkably productive. https://medium.freecodecamp.org/we-fired-our-top-talent-best-decision-… is a good example of a company learning that lesson a little too late. A company that signals that they trust their jerks enough to make hiring decisions and to represent the company's culture to potential new hires is a company that signals they're actively cool with jerks (or incapable of noticing, which has the same effect). If a jerk makes a good employee unhappy and they leave, the jerk is a net negative. And if you keep…

I just went through my bookmarks and quite a few of the links are dead... I've been doing this for decades so that's not a surprise. And not really a big deal. Most of the progress I've seen has been made in the last five or so years. Technical interviews might be horrible now, but they used to be way worse! A LOT of the articles I've read over the years I have not bookmarked because my idea of a good technical interview is the opposite of what those articles recommended. I normally read everything interview related I come across in HN or Reddit programming subreddits but I'll also do a search every six months or so and see if anything interesting comes up. Although I have cherry-picked advice from reading many articles over the years, more importantly I've tried really hard to come up with an interview process I myself would enjoy as a candidate. That factor is very important to me because I think the interviewing process sucks at many companies. It's painful for everyone involved and ineffective. I would tolerate painful and effective. But I think it can be somewhat painless and effective. I remember getting at least a few valuable ideas from these: http://firstround.com/review/The-anatomy-of-the-perfect-technical-inte… https://www.wired.com/2015/04/hire-like-google/ https://medium.freecodecamp.org/we-analyzed-thousands-of-coding-interv… Also ask someone in HR what soft skills you need to improve…

While there are many great reasons to learn languages like Scala and Kotlin, "Java is old" is not the right one (for one, it's false). The functional programming elements in Java 8 (<4 years old) do make it a new language. I've been keeping up with Java since V1.4, and I felt like Java 5 was the update that made Java a modern language, but Java 8 brought a paradigm shift (if you felt like changing your style). And in any way, the title is misleading. It should have been "Kotlin: here is why we think it's better than Java 5" - because that's the actual content of the article. I like learning about new languages, but I wish the article had more. For instance, it doesn't mention functional programming paradigms (the new thing in Java 8), even though Kotlin does have them, e.g.[1]. That's one way to improve the article beyond the title. [1] https://medium.freecodecamp.org/my-favorite-examples-of-functional-pro…

Great post, but lofty. Here is an example of a relatable situtational system thinking in the very small: https://medium.freecodecamp.org/how-to-organize-your-thoughts-on-the-w… I havent read much on the theories, but part of my write was also inspired by two books and hence why I am responding to help others. Pragmatic Thinking and Learning by Andy Hunt and The Fifth Discipline by Peter Senge helped me with this type of thinking. A few things key concepts. Organization of related systems and their interaction patterns. But a key, that you are also apart of the system as you interact. For instance, the causal link of bringing sweet smelling dry erase markers. You could shift the whole system of interview rating based on memory of smell on that sweet expo choco mint as you erase your complex mistakes away. Or they could think that you're just crazy.