Every time I talk to a recent grad I hear a variation of the phrase, “I know how to code, I can code in anything.” This is, on the surface, true for some bits like boolean logic and loops. Where it starts to fail for me is when I need to leverage a language’s ecosystem.…
I have learned to respect the learning curve on any new “Language”. I appreciate the YouVideo and subscription to Udemy that I have. It still takes time, more time than getting on a bicycle after 10 years.
I now know twelve languages and the last two took almost as much time as the first ten.
via I Know How to Code, I Can Code in Anything — DZone Web Dev Zone
I have used D3 in concert with C3 to create a data visualization front end to a data warehouse. D3 has a ton of features but is difficult to use out of the box for the novice user. The C3 library puts a layer of smarts on top of D3 making it much easier to get started in graphic visualizations. I’ve also used CData product to get an ODBC connection to Google sheets in order to analyze and transfer results from a Google form survey to a data warehouse. CData products are very good just be willing to pay for that excellence.
This article is a good read because it combines the two to assemble a REST service and use it to provide the data feed to D3.
via Building Dynamic D3.js Web Apps With Database Data — DZone Web Dev Zone
I would like to invite you to read a amazing and very interesting article about node.js, which I am quoting with a link to the target page: “… Last year and at the beginning of this year, we asked you, Node.js users, to help us understand where, how … more
Well, programmer kiddies as I have said before it’s Node.JS because it’s fracking everywhere. When Microsoft’s Visual Studio has a special setup just for Node.JS and .net applications then it must be real. 😉
Seriously, take some time to learn the Node.JS basics. There are 2-ton of YouTube videos and excellent Udemy classes. You can learn the basics in 2 hours.
via Node.js Emerging as the Universal Development Framework for a Diversity of Applications — JSFeeds
Making HTTP requests is a core functionality for modern languages and one of the first things many developers learn when acclimating to new environments. When it comes to Node.js there are a fair amount of solutions to this problem both built into the … more
If you’re using Node to develop applications or servers you will need to handle HTTP requests. The standard Node HTTP library is good but there are some options including promises, Super Agent and Ajax to name a few. While it’s not rocket science this article comes from the experiences with NASA.
via HTTP Requests in Node.js — JSFeeds
Services in a microservices architecture share some common requirements regarding authentication and transportation when they need to be accessible by external clients. API Gateway s provide a shared layer to handle differences between service protocols and fulfills the requirements of specific clients like desktop browsers, mobile devices, and legacy systems. Click to see all chapters…
API Gateways are the middle man in the Application-Data relationship. They serve as a community hall where folks go to meet and talk to one another. This community hall has a universal translator like on Star Trek that makes data understood by all the people in the room. Developers don’t worry about XML/JSON because the gateway understands them both. DBA don’t worry about formatting the data because the gateway loves to format stuff.
Have you ever been fustrated with Sri, OK Google or Alexa? Gateway quality varies from one vendor to another. Write your own in Node may be an alternative, I don’t know. Let’s talk.
via Building an API Gateway using Node.js — RisingStack Engineering
In the UK we have a chef called Jamie Oliver and over the years he has created lots of TV episodes and also a book on how to make a complete family meal in 30 Minutes – The premise of this, is that time doesn’t have to be an excuse not to make healthy food […]
There are times when you need a mock server for a REST API that returns JSON results and you need it now!! This article goes over the process to create one on your local system which could be transferred to a server. You create a JSON file, simple text file, with the data in it and JSON-Server writes a full API service around it. It can do all the CRUD you want and support queries.
There are a few restrictions like having a key field requirement in each table with the identical name. (IE: _id) . Most of my work requires using the key that was already in the database (ie: benficiaryID, providerNumber, DiagCode). Moving this to a server will require some technical talent that many companies don’t have.
I have used Mockable IO to provide mock API services that are server based and need to be accessed by developers outside of a corporate firewall. The free version is enough for most projects to get started.
No matter which mock server you use be prepared to take a considerable amount of time to mock up the results sets you expect the API service to provide.
via 30 Second APIs… — Danny Dainton
The Node.js Foundation just published the results of a worldwide research which was conducted to understand what Node is used for nowadays, and to identify possible improvements for our favorite open-source framework. The survey was conducted online … more
Tep, another survey. This seems to be the week for them. This is a very good read especially for those Government types who think node.js is just a distraction to real work. The infographics in this article are excellent and summarizes what I’ve told people for awhile now. Node is here to stay, it is often a better alternative to traditional development environments. Node is everywhere, maybe not to extent of Java or DotNet but its power provides it with the ability to be a tool in your solution toolkit.
Node is going to replace legacy applications or the cure all for quicker and richer solutions but, it is capable of some pretty impressive shit.
New things scare people, not that Node is that new. I’m going to date myself here. I remember when everyone was afraid of a new thing called “Structured Cobol Programming”. Think about it when was the last time you saw a “GOTO xxxx” statement anywhere?
via This is what Node.js is used for in 2017 – Survey Results — JSFeeds
Debugging – the process of finding and fixing defects in software – can be a challenging task to do in all languages. Node.js is no exception. Luckily, the tooling for finding these issues improved a lot in the past period. Let’s take a look at what options you have to find and fix bugs in…
I am at the level with Node.JS that I no longer “Suck at it” but I am still learning every time I use it. One of the areas I struggled with was debugging, which was much different and difficult than my .NET and PHP days. It seems like open source meant that you were on your own for debugging.
Special thanks to Gergely for his article on just the topic of Node.js debugging.
One of the takeaways in the article is Pino is an extremely fast Node.js logger, inspired by bunyan. In many cases, pino is over 6x faster than alternatives like bunyan or winston
I had tried Winston as it was recommended by one of my programmer gods. I was not worthy because I couldn’t understand it. I have high hopes for Pino.
via How to Debug Node.js with the Best Tools Available — RisingStack Engineering
“Backlog” is one of those SCRUMmy terms used to identify features or functions that have been dreamed up or discussed for an application. You collect these ideas into a list which is called the “Backlog”. Then this list is reviewed (Sprint Review) and the ideas are refined (Groomed) and an estimate of effort (Story Points) is assigned to it. Then folks get together and discuss which ones should be done in the next timeframe (Sprint). To collect these ideas some companies use an issue tracking system or an off the shelf ticket system (Atlassian JIRA) and others just use a spreadsheet… gasp.
Sometimes all you need is a simple web application that all the participants can use to enter any ANY of the ideas that came up. Even things like “The buttons should be colored blue.” I needed a simple project to help me learn some technologies that are new to me. Hence the “Backlogger” was born. The whiteboard above shows the original concept.
Technologies used in Backlogger
- Mongo without the headache, neDB
The design requirements were meant to be simple as possible to make this project something that could be done quickly. They also needed to be flexible to allow for better learning.
- Single Page Application
- Open Source
- No user logins, just a password, we are a big happy family
- Self-contained application, no need for outside services or servers
- Mongo database and Mongo queries
- Allow for a maintainable list of people names who contributed ideas to the backlog
- Allow for a maintainable list of functional areas to help groups the ideas
- One time entry of an idea, no editing,
- The editing of an idea will be done during the grooming
- Filters that help find ideas quickly
- Ability to backup and wipe the database (Mongo Documents)
- Simple report that can be printed directly
GeekMustHave would like to thank Phoenix Learning Labs for the resources and funding to do this project. GeekMustHave would also like to thank the MDHHS-DWIP team for the testing and feedback.
Open source, common components
What does it look like?
Backlogger is an Open Source project available on Github.
I’ve used “Backlogger” in one project so far but others who have seen it have expressed some interest in it. That’s another reason why it’s Open Source.
Depending on the feedback I might do additional updates. Maybe I need a “Backlogger” for the “Backlogger”?
In short, json-server is a Node module, running an Express server, that lets you specify a JSON file to act as a data source for your mock REST API.