Summer is great for catching up on some reading backlog. Missed a blog post? Don’t worry! We’re here to help you out. These past months our front end engineering community has been very active in implementing web technologies across our customer base. Want to get started with the latest web technologies in your project?
This blog post is part 2 of our hackathon idea. It covers the technical setup we used to get the prototype up and running during the two-day hackathon at AE. You can read about the concept idea in part 1.
On the 4th and 5th of June, AE organized a hackathon for all interested employees. We were invited to gather a team and work out our own idea based on the theme "Think customer, explore the future". Our team: 4 developers and 1 analyst. This blog post describes our idea and how we implemented this in under 36 hours.
Making your web applications Search Engine Friendly has always been important for scoring high in search engine results. More and more of those front end applications are evolving towards SPA's (Single Page App) which are inherently difficult to crawl, thereby potentially impacting your search ranking. However, the dilemma between a focus on UX or SEO is a fallacy. In this post we’ll have a look at how you can both offer a dynamic, fast and user-friendly web application and still keep search engine crawlers happy.
Do you recognize the following situation? You are involved in a project and, based on a slide deck or analysis document, you need to decide on the way to go. After reading the content, you don’t feel like you’ve fully grasped it and you don’t feel comfortable at all to take a decision. In this article, I’d like to share 3 practical tips to increase the value of any change/requirements document, enabling faster and more confident decision taking for stakeholders.