IT and Engineering

How Lucidites Use Lucidchart: Diagrams for Engineering

Many software engineers use diagrams to architect new applications and systems and to prepare documentation for troubleshooting and training. Our engineers at Lucid Software are no different. They diagram as they work hard to make diagramming (and designing on Lucidpress) easier for you. Check out how our engineers have applied Lucidchart in various aspects of their jobs.

The software architect's secret to communicating effectively

Here at Lucid, we geek out whenever we talk to customers who use Lucidchart to make their work better. We recently had a chat with a friend of ours named Matt and are excited to share his story with you.

How to Make a Data Flow Diagram in Word

Find out how to make a data flow diagram in Microsoft Word. This step-by-step guide outlines how to manually create a DFD in Word using the shape library and with Lucidchart add-in. Templates included!

What your boss would like to know about project network diagrams

Project network diagrams allow PMs to summarize their plans in one visual that can be easily digested and understood. Learn how to make one here.

The 5 Most Popular Sessions at AWS re:Invent 2016

AWS delivered once again at its annual re:Invent conference in Las Vegas last week. Gartner estimates that the company’s market share is 10 times bigger than its 14 closest competitors combined—a fact that likely wouldn’t shock the 30,000 attendees who watched (occasionally with jaws dropping) as AWS revealed one new service after another at AWS re:Invent 2016.

Onboarding engineers with Lucidchart

With Lucidchart, onboarding engineers is painless and can have your new hires up to speed in no time. Learn how to improve your onboarding.

Which Avengers Do You Need on Your Engineering Team?

If you were forming a team within your industry, what superheroes or strengths would you need to succeed? What would make, for example, a super engineering team? With input from Lucidchart’s own product and engineering teams, we’ve put together the superheroes and traits you need in every role to ensure that you power through your next sprint.  

The fatal flaw of A/B tests: Peeking

A/B significance testing has become irresistibly simple. Plug a few numbers in an online calculator, and voilà... statistically verified results. But this on-demand verification is fatally flawed: Looking at results more than once invalidates their statistical significance.

Why Code Snobs Are Invaluable

Some argue that “code snobs” waste time on trivia. They are accused of myopia and pedantry, and their peers claim that the effort they spend in crafting every detail in their code is a bad investment. While this can occasionally be the case, I submit that their ideas and comments offer more benefit than cost in the long run.

Are You Ready to Commit? Developing a Professional Software Engineer Workflow

The importance of cross-team communication in quality assurance: A developer’s perspective

Bugs are slippery, and sometimes they make it past these increased testing measures. When they do, we encourage cross-team communication to get fixes out to our customers as quickly as possible.

How to Write an Effective Bug Report That Actually Gets Resolved (and Why Everyone Should)

One of the best ways we can support the software we love is by showing an interest in the development of the software by submitting bug reports. Take a more proactive approach than complaining or throwing your computer out the window, and actually take the time to report the bug.