A Whimsical Full-stack Browser-based Application Built using ReactJS

TeaLab

TeaLab is a whimsical full-stack browser-based application built using ReactJS, Cloudinary, CSS, PostgreSQL and Express. Users are able to create and collect teas, that makes learning about tea fun! Users will be able to save, edit and delete their tea recipes on a recipe profile page.

Dependencies

Cloudinary

reactour

react-hot-toast

react-modal

Alchemy Code Lab Bootstrap Template

Team Members

Contributing Team MembersGithubLinkedIn
Sam Melius OxfordGithubLinkedIn
Clare McDonaldGithubLinkedIn
Ari Harlem-CaballeroGithubLinkedIn
Alice HsingGithubLinkedIn
Ryan FlitcroftGithubLinkedIn

Backend API

This app runs on a PostgreSQL database using Node.js/Express.

Routes

User Routes

  • POST /api/v1/users/
  • POST /api/v1/users/session
  • GET /api/v1/users/me
  • DELETE /api/v1/users/session

Ingredient Routes

  • POST /api/v1/ingredients
  • GET /api/v1/ingredients
  • GET /api/v1/ingredients/:id
  • PATCH /api/v1/ingredients/:id
  • DELETE /api/v1/ingredients/:id

Recipe Routes

  • GET /api/v1/recipes
  • GET /api/v1/recipes/count
  • GET /api/v1/recipes/:id
  • GET /api/v1/recipes/users/:id
  • POST /api/v1/recipes
  • PATCH /api/v1/recipes/:id
  • DELETE /api/v1/recipes/:id

Author: AlchemyTeaLab
Source code: https://github.com/AlchemyTeaLab/TeaLab-back-end

#react #typescript #javascript 

What is GEEK

Buddha Community

A Whimsical Full-stack Browser-based Application Built using ReactJS
Chloe  Butler

Chloe Butler

1667425440

Pdf2gerb: Perl Script Converts PDF Files to Gerber format

pdf2gerb

Perl script converts PDF files to Gerber format

Pdf2Gerb generates Gerber 274X photoplotting and Excellon drill files from PDFs of a PCB. Up to three PDFs are used: the top copper layer, the bottom copper layer (for 2-sided PCBs), and an optional silk screen layer. The PDFs can be created directly from any PDF drawing software, or a PDF print driver can be used to capture the Print output if the drawing software does not directly support output to PDF.

The general workflow is as follows:

  1. Design the PCB using your favorite CAD or drawing software.
  2. Print the top and bottom copper and top silk screen layers to a PDF file.
  3. Run Pdf2Gerb on the PDFs to create Gerber and Excellon files.
  4. Use a Gerber viewer to double-check the output against the original PCB design.
  5. Make adjustments as needed.
  6. Submit the files to a PCB manufacturer.

Please note that Pdf2Gerb does NOT perform DRC (Design Rule Checks), as these will vary according to individual PCB manufacturer conventions and capabilities. Also note that Pdf2Gerb is not perfect, so the output files must always be checked before submitting them. As of version 1.6, Pdf2Gerb supports most PCB elements, such as round and square pads, round holes, traces, SMD pads, ground planes, no-fill areas, and panelization. However, because it interprets the graphical output of a Print function, there are limitations in what it can recognize (or there may be bugs).

See docs/Pdf2Gerb.pdf for install/setup, config, usage, and other info.


pdf2gerb_cfg.pm

#Pdf2Gerb config settings:
#Put this file in same folder/directory as pdf2gerb.pl itself (global settings),
#or copy to another folder/directory with PDFs if you want PCB-specific settings.
#There is only one user of this file, so we don't need a custom package or namespace.
#NOTE: all constants defined in here will be added to main namespace.
#package pdf2gerb_cfg;

use strict; #trap undef vars (easier debug)
use warnings; #other useful info (easier debug)


##############################################################################################
#configurable settings:
#change values here instead of in main pfg2gerb.pl file

use constant WANT_COLORS => ($^O !~ m/Win/); #ANSI colors no worky on Windows? this must be set < first DebugPrint() call

#just a little warning; set realistic expectations:
#DebugPrint("${\(CYAN)}Pdf2Gerb.pl ${\(VERSION)}, $^O O/S\n${\(YELLOW)}${\(BOLD)}${\(ITALIC)}This is EXPERIMENTAL software.  \nGerber files MAY CONTAIN ERRORS.  Please CHECK them before fabrication!${\(RESET)}", 0); #if WANT_DEBUG

use constant METRIC => FALSE; #set to TRUE for metric units (only affect final numbers in output files, not internal arithmetic)
use constant APERTURE_LIMIT => 0; #34; #max #apertures to use; generate warnings if too many apertures are used (0 to not check)
use constant DRILL_FMT => '2.4'; #'2.3'; #'2.4' is the default for PCB fab; change to '2.3' for CNC

use constant WANT_DEBUG => 0; #10; #level of debug wanted; higher == more, lower == less, 0 == none
use constant GERBER_DEBUG => 0; #level of debug to include in Gerber file; DON'T USE FOR FABRICATION
use constant WANT_STREAMS => FALSE; #TRUE; #save decompressed streams to files (for debug)
use constant WANT_ALLINPUT => FALSE; #TRUE; #save entire input stream (for debug ONLY)

#DebugPrint(sprintf("${\(CYAN)}DEBUG: stdout %d, gerber %d, want streams? %d, all input? %d, O/S: $^O, Perl: $]${\(RESET)}\n", WANT_DEBUG, GERBER_DEBUG, WANT_STREAMS, WANT_ALLINPUT), 1);
#DebugPrint(sprintf("max int = %d, min int = %d\n", MAXINT, MININT), 1); 

#define standard trace and pad sizes to reduce scaling or PDF rendering errors:
#This avoids weird aperture settings and replaces them with more standardized values.
#(I'm not sure how photoplotters handle strange sizes).
#Fewer choices here gives more accurate mapping in the final Gerber files.
#units are in inches
use constant TOOL_SIZES => #add more as desired
(
#round or square pads (> 0) and drills (< 0):
    .010, -.001,  #tiny pads for SMD; dummy drill size (too small for practical use, but needed so StandardTool will use this entry)
    .031, -.014,  #used for vias
    .041, -.020,  #smallest non-filled plated hole
    .051, -.025,
    .056, -.029,  #useful for IC pins
    .070, -.033,
    .075, -.040,  #heavier leads
#    .090, -.043,  #NOTE: 600 dpi is not high enough resolution to reliably distinguish between .043" and .046", so choose 1 of the 2 here
    .100, -.046,
    .115, -.052,
    .130, -.061,
    .140, -.067,
    .150, -.079,
    .175, -.088,
    .190, -.093,
    .200, -.100,
    .220, -.110,
    .160, -.125,  #useful for mounting holes
#some additional pad sizes without holes (repeat a previous hole size if you just want the pad size):
    .090, -.040,  #want a .090 pad option, but use dummy hole size
    .065, -.040, #.065 x .065 rect pad
    .035, -.040, #.035 x .065 rect pad
#traces:
    .001,  #too thin for real traces; use only for board outlines
    .006,  #minimum real trace width; mainly used for text
    .008,  #mainly used for mid-sized text, not traces
    .010,  #minimum recommended trace width for low-current signals
    .012,
    .015,  #moderate low-voltage current
    .020,  #heavier trace for power, ground (even if a lighter one is adequate)
    .025,
    .030,  #heavy-current traces; be careful with these ones!
    .040,
    .050,
    .060,
    .080,
    .100,
    .120,
);
#Areas larger than the values below will be filled with parallel lines:
#This cuts down on the number of aperture sizes used.
#Set to 0 to always use an aperture or drill, regardless of size.
use constant { MAX_APERTURE => max((TOOL_SIZES)) + .004, MAX_DRILL => -min((TOOL_SIZES)) + .004 }; #max aperture and drill sizes (plus a little tolerance)
#DebugPrint(sprintf("using %d standard tool sizes: %s, max aper %.3f, max drill %.3f\n", scalar((TOOL_SIZES)), join(", ", (TOOL_SIZES)), MAX_APERTURE, MAX_DRILL), 1);

#NOTE: Compare the PDF to the original CAD file to check the accuracy of the PDF rendering and parsing!
#for example, the CAD software I used generated the following circles for holes:
#CAD hole size:   parsed PDF diameter:      error:
#  .014                .016                +.002
#  .020                .02267              +.00267
#  .025                .026                +.001
#  .029                .03167              +.00267
#  .033                .036                +.003
#  .040                .04267              +.00267
#This was usually ~ .002" - .003" too big compared to the hole as displayed in the CAD software.
#To compensate for PDF rendering errors (either during CAD Print function or PDF parsing logic), adjust the values below as needed.
#units are pixels; for example, a value of 2.4 at 600 dpi = .0004 inch, 2 at 600 dpi = .0033"
use constant
{
    HOLE_ADJUST => -0.004 * 600, #-2.6, #holes seemed to be slightly oversized (by .002" - .004"), so shrink them a little
    RNDPAD_ADJUST => -0.003 * 600, #-2, #-2.4, #round pads seemed to be slightly oversized, so shrink them a little
    SQRPAD_ADJUST => +0.001 * 600, #+.5, #square pads are sometimes too small by .00067, so bump them up a little
    RECTPAD_ADJUST => 0, #(pixels) rectangular pads seem to be okay? (not tested much)
    TRACE_ADJUST => 0, #(pixels) traces seemed to be okay?
    REDUCE_TOLERANCE => .001, #(inches) allow this much variation when reducing circles and rects
};

#Also, my CAD's Print function or the PDF print driver I used was a little off for circles, so define some additional adjustment values here:
#Values are added to X/Y coordinates; units are pixels; for example, a value of 1 at 600 dpi would be ~= .002 inch
use constant
{
    CIRCLE_ADJUST_MINX => 0,
    CIRCLE_ADJUST_MINY => -0.001 * 600, #-1, #circles were a little too high, so nudge them a little lower
    CIRCLE_ADJUST_MAXX => +0.001 * 600, #+1, #circles were a little too far to the left, so nudge them a little to the right
    CIRCLE_ADJUST_MAXY => 0,
    SUBST_CIRCLE_CLIPRECT => FALSE, #generate circle and substitute for clip rects (to compensate for the way some CAD software draws circles)
    WANT_CLIPRECT => TRUE, #FALSE, #AI doesn't need clip rect at all? should be on normally?
    RECT_COMPLETION => FALSE, #TRUE, #fill in 4th side of rect when 3 sides found
};

#allow .012 clearance around pads for solder mask:
#This value effectively adjusts pad sizes in the TOOL_SIZES list above (only for solder mask layers).
use constant SOLDER_MARGIN => +.012; #units are inches

#line join/cap styles:
use constant
{
    CAP_NONE => 0, #butt (none); line is exact length
    CAP_ROUND => 1, #round cap/join; line overhangs by a semi-circle at either end
    CAP_SQUARE => 2, #square cap/join; line overhangs by a half square on either end
    CAP_OVERRIDE => FALSE, #cap style overrides drawing logic
};
    
#number of elements in each shape type:
use constant
{
    RECT_SHAPELEN => 6, #x0, y0, x1, y1, count, "rect" (start, end corners)
    LINE_SHAPELEN => 6, #x0, y0, x1, y1, count, "line" (line seg)
    CURVE_SHAPELEN => 10, #xstart, ystart, x0, y0, x1, y1, xend, yend, count, "curve" (bezier 2 points)
    CIRCLE_SHAPELEN => 5, #x, y, 5, count, "circle" (center + radius)
};
#const my %SHAPELEN =
#Readonly my %SHAPELEN =>
our %SHAPELEN =
(
    rect => RECT_SHAPELEN,
    line => LINE_SHAPELEN,
    curve => CURVE_SHAPELEN,
    circle => CIRCLE_SHAPELEN,
);

#panelization:
#This will repeat the entire body the number of times indicated along the X or Y axes (files grow accordingly).
#Display elements that overhang PCB boundary can be squashed or left as-is (typically text or other silk screen markings).
#Set "overhangs" TRUE to allow overhangs, FALSE to truncate them.
#xpad and ypad allow margins to be added around outer edge of panelized PCB.
use constant PANELIZE => {'x' => 1, 'y' => 1, 'xpad' => 0, 'ypad' => 0, 'overhangs' => TRUE}; #number of times to repeat in X and Y directions

# Set this to 1 if you need TurboCAD support.
#$turboCAD = FALSE; #is this still needed as an option?

#CIRCAD pad generation uses an appropriate aperture, then moves it (stroke) "a little" - we use this to find pads and distinguish them from PCB holes. 
use constant PAD_STROKE => 0.3; #0.0005 * 600; #units are pixels
#convert very short traces to pads or holes:
use constant TRACE_MINLEN => .001; #units are inches
#use constant ALWAYS_XY => TRUE; #FALSE; #force XY even if X or Y doesn't change; NOTE: needs to be TRUE for all pads to show in FlatCAM and ViewPlot
use constant REMOVE_POLARITY => FALSE; #TRUE; #set to remove subtractive (negative) polarity; NOTE: must be FALSE for ground planes

#PDF uses "points", each point = 1/72 inch
#combined with a PDF scale factor of .12, this gives 600 dpi resolution (1/72 * .12 = 600 dpi)
use constant INCHES_PER_POINT => 1/72; #0.0138888889; #multiply point-size by this to get inches

# The precision used when computing a bezier curve. Higher numbers are more precise but slower (and generate larger files).
#$bezierPrecision = 100;
use constant BEZIER_PRECISION => 36; #100; #use const; reduced for faster rendering (mainly used for silk screen and thermal pads)

# Ground planes and silk screen or larger copper rectangles or circles are filled line-by-line using this resolution.
use constant FILL_WIDTH => .01; #fill at most 0.01 inch at a time

# The max number of characters to read into memory
use constant MAX_BYTES => 10 * M; #bumped up to 10 MB, use const

use constant DUP_DRILL1 => TRUE; #FALSE; #kludge: ViewPlot doesn't load drill files that are too small so duplicate first tool

my $runtime = time(); #Time::HiRes::gettimeofday(); #measure my execution time

print STDERR "Loaded config settings from '${\(__FILE__)}'.\n";
1; #last value must be truthful to indicate successful load


#############################################################################################
#junk/experiment:

#use Package::Constants;
#use Exporter qw(import); #https://perldoc.perl.org/Exporter.html

#my $caller = "pdf2gerb::";

#sub cfg
#{
#    my $proto = shift;
#    my $class = ref($proto) || $proto;
#    my $settings =
#    {
#        $WANT_DEBUG => 990, #10; #level of debug wanted; higher == more, lower == less, 0 == none
#    };
#    bless($settings, $class);
#    return $settings;
#}

#use constant HELLO => "hi there2"; #"main::HELLO" => "hi there";
#use constant GOODBYE => 14; #"main::GOODBYE" => 12;

#print STDERR "read cfg file\n";

#our @EXPORT_OK = Package::Constants->list(__PACKAGE__); #https://www.perlmonks.org/?node_id=1072691; NOTE: "_OK" skips short/common names

#print STDERR scalar(@EXPORT_OK) . " consts exported:\n";
#foreach(@EXPORT_OK) { print STDERR "$_\n"; }
#my $val = main::thing("xyz");
#print STDERR "caller gave me $val\n";
#foreach my $arg (@ARGV) { print STDERR "arg $arg\n"; }

Download Details:

Author: swannman
Source Code: https://github.com/swannman/pdf2gerb

License: GPL-3.0 license

#perl 

Aria Barnes

Aria Barnes

1625490702

Is Full-Stack Developer A Vaccine For Startups?

There's a wise old saying: "Working with a full stack developer can lead to better technology solutions." And in recent years, this saying has proven to be true for many startups.

In the last few years, we have heard a lot about full-stack developers.

We know that a full-stack developer is a person who has complete knowledge of the different layers involved in application development. Whether you are dealing with the front or back end or working in the business layer, they take care of everything with ease.

But did you wonder why a full-stack developer is so important for a startup? 

This blog will answer all such queries. So let's get started.

The Demand for Full-Stack Developers

As per a development report published recently, it was seen that there had been a 206% increase in demand for full-stack developers from 2018 to 2020. This is because more companies seek multifaceted skills. 


Full-stack developers or a full-stack development company are able to take care of all the development needs of your project. So whether it's front-end or back-end development or enterprise layer development, they are competent to work on everything. You can always hire full-stack developers for your business needs.

What can a Full-Stack Developer Do?

In terms of software development, there are front-end developers and back-end developers. Front-end developers create the interface, while backend developers design the software. 

A full-stack developer can do everything. They take care of application design, server-side scripting, client-side coding, coding, administration, database creation, and any other project development needs.

The following are the responsibilities of a full stack developer that you hire:

  • Manage web development

  • Code applications and programs

  • Solve problems

  • Coordinate with other team members and developers

  • Think about testing techniques for web applications

In short, a full-stack developer has a strong understanding of the technologies that determine how a website looks, functions, and functions. The said developer must have a working knowledge of HTML, JavaScript, CSS, PHP, Angular, Ruby, MySQL, Node, MongoDB, Apache, etc. The knowledge to work with animations and design will add a bonus point to a candidate's portfolio.

Over time, the skills required for full-stack development have expanded and evolved. Long ago, the LAMP stack included Linux, Apache, MySQL, and PHP. It is more than MEAN and beyond today. 

Currently, a typical mean stack development service provides developers who can perform front-end development using JavaScript, HTML, CSS, and other JS frameworks; for the backend, they use Express and Node, and for databases, they follow MySQL and MongoDB.

Top Reasons to Hire Full-Stack Developers

  • Effective troubleshooting

When hiring a full-stack developer, companies are always looking for candidates who are capable of solving a problem. Full-stack developers are competent to handle all aspects of the project. They prove to be a practical solution for startups that are not willing to spend more money on many developers.

  • Wide range of technology skills

The main reason companies choose full-stack developers for their projects is their potential rather than their knowledge. Over time, companies teach them the skills they want them to have. In this way, in a few years, they learn different technological skills as the company expands.

  • Executive and management skills

Companies like to have people with business experience on board. A full-stack developer has the knowledge and expertise to work on the front-end, backend, and media architecture layers. This means that they are capable of performing better than an individual front-end or backend developer.

  • Economic

As full-stack developers can develop all aspects of a project, it is not necessary to form a team of experts. They will easily handle the project without help from anyone. This will save the right amount of money for the recruiting team.

  • Faster development process

Full-stack developers know different technologies, tools, and techniques. This means that when they take the project, they will be able to complete it faster. They will spend less time discussing and collaborating with the team on the project.

Benefits of Full-Stack Developers for Startups and Small Businesses

  • Established developers

Full-stack developers have enough experience to create outstanding features for the final product, which will be able to excite the market. They have the ability to build a complete product from scratch. If you want to gain some benefits from your product, you will have to collaborate with these experts. Remember that not all developers are capable of handling the project from a 360-degree perspective.

  • Versatility

A full-stack developer is able to work equally well on the front-end and the backend of a website or application. Front-end developers write code using JavaScript, HTML, and CSS, which are able to control the appearance of the solution and how it interacts with the browser and users. Backend developers write code that connects the website or application with other content management systems. A full-stack developer is capable of handling both tasks. They are focused on meeting customer expectations and finding solutions on their own.

 

  • Vast experience

Full-stack developers take on different web projects. This has helped them gain in-depth knowledge of various technologies and the experience to find quick solutions in web and application development. Such understanding and knowledge improve the performance of the project and its reception in the market.

  • The largest photograph

The main advantage of choosing a full-stack developer for your project is that they will come up with the complete structure of the project and offer their valuable input to the project as needed. Their services go beyond project development to maintain and optimize existing solutions.

  • Upgrades

Web design plays a crucial role in whether most people love or reject a website. Full-stack developers will make sure that the website is pretty user-friendly. They keep up with trends and technological innovations. To make sure their clients get the best interactive and responsive website, the developers implement intelligent features in their projects.

  • Troubleshooting issues

Full-stack developers have complete knowledge and experience of the different stages and aspects of website development. They are skilled enough to identify problems that may arise during the development of the project. They will propose long-term solutions to ensure that the website or application works optimally based on their findings.

  • All-inclusive

In addition to leading your web project and enabling enhancements to it, full-stack developers move to the level of representing your product to stakeholders or your company at conferences. They can move quickly from one operation to another with ease, streamlining the development process.

  • Economic

If you are on a tight budget but want to create a fantastic website, then you should consider hiring full developers for the job. You can even think about having a remote full-stack developer for the project. As such, a developer is capable of handling all aspects of project development; you won't have to hire different people for the job. This will save you a lot of money.

  • Delivery time

It will be easy for developers to share responsibilities among the team and coordinate with each other for better project progress. This will result in faster delivery of the project.

  • Project ownership

When you hire full-stack developers for your project, you can be sure that they will take care of everything. Such a developer will be able to develop MVP from start to finish. If you hire a full-stack developer in the middle of the project, even then, you'll find a way to join the flow seamlessly. Such a developer will work towards quality control of the design project.

 

 

Summing Up

So these were the advantages of hiring a full-stack developer. I hope you have noted the changes that a full-stack developer can bring to the table and in your company. However, working with a full-stack developer is the best way to work with a top full-stack development company in India.

It is a good idea that full-stack development companies bring to your projects are phenomenal and groundbreaking due to the expertise and experience that full-stack development companies bring to your projects.

If you have any other queries or suggestions, feel free to comment below.

Original source

#full stack developers #hire full stack developers #full stack development #mean stack development service #hire full stack developer india #hire full stack developer

Hire Full Stack Developers

If you are looking for a full-stack mobile developer for your web or mobile app development needs?

Hire Full Stack Developers to develop any type of web, mobile, or desktop applications from start-to-end. HourlyDeveloper.io full-stack programmers know their way around different tiers of software development, servers, databases, APIs, MVC, and hosting environments among others.

Contact us: https://bit.ly/2W6j57w

#hire full stack developers #full stack developers #full-stack programmers #full-stack development #full-stack

Hire Full Stack Developer India

Do you want to get a web application that can meet your business requirements successfully?

We love to work with startups and enterprises to solve their business problems using our full-stack technology competencies. Our expertise in agile and efficient use of the latest development methodologies helps us to convert your idea into a market-ready product. Hire Full Stack Developer India from HourlyDeveloper.io will help you to achieve defined goals throughout product development, testing, and deployment.

Consult with our experts: https://bit.ly/34Gqm31Full Stack Development

#hire full stack developer india #full stack developer india #full stack developer #full stack #full stack development

navin prakash

1609588950

Advantages of hiring a full stack developer

Full-stack developers can work with various software applications to design a custom code that allows them to proficiently operate the website as well as its features. They have the potential to serve the entire project, from the ideas’ design to the product’s implementation accordingly.
If you are seeking Full Stack Developer Course in Chennai and FITA Academy is the NO.1 Training institute for Full Stack Developer Training in Chennai. We are providing the best advantages of hiring a full stack developer.

  1. Expert knowledge
    Expert & professional web design services are provided by full-stack designers. To attach innovative functionality to the websites or the application that excites the business, they have the experience & qualifications. The specialist player for frontend and backend creation is deemed to be a full-stack designer. This offers the benefit of moving between all parties, client and server-side and vice versa.
    A significant advantage with full-stack developers is that they do not compromise on the success of the work and are updated with the latest technologies. And it’s not everyone’s teacup, and so it just wants to give to the right hands.
  2. Versatility
    As previously mentioned, in backend & frontend creation, full-stack programmers are qualified. Front-end developers create algorithms that monitor the interactivity and the presentation of a webpage in the application (using Javascript, HTML & CSS). For linking the website & other CMS, back-end developers build prototypes. And here comes the full stack developer, who can effectively perform both functions. They concentrate on objectives and, without relying on others, have unique solutions.
  3. Rich Experience
    As the complete stack designers are involved in the different types of Internet programs, they have expertise with in-depth information on software & web development. They will determine the needs of the project and provide solutions out of the bag. And the perspectives offered by them will be useful for the project’s success & price sensitivity. This is something you don’t expect to get from other designers.
  4. Bigger picture of design structure
    One of the key advantages of full-stack developers is that they are useful and provide their contributions as needed in the larger entire design framework. Full Stack Developer Course in Pune is very helpful for your best career in the sector. Not only are their products restricted to web growth, but they go beyond supporting and improving existing structures. They are well versed in switching sides or ending in the production of MVP and are conscious of tackling the UI architecture of the software. So, full-stack developers are all in one package.
  5. Easy up-gradation
    Full-stack developers are recognized to be up to date with the latest developments and advancements in technology. They will also do the same at jobs, allowing customers to have access to the latest up-to-date technology. 94 percent of respondents said that they liked or disliked the websites on the basis of web development, according to a recent analysis. And that they will make your website more user-friendly as the full-stack developers are informed of all the software developments and innovations. Your customers will get a professional app that is interactive and sensitive because some cool & smart features are implemented in the project by full-stack programmers.

#full stack developer #full stack developer course #full stack developer training in chennai #full stack developer course in chennai #full stack