The Parliamentary Review reiterates Priocept's position that effective communication of complex technology subjects relies on the use of jargon-free "plain English".
Priocept have been featured in the 2018 edition of The Parliamentary Review, a series of publications which aim to share best practice among policy makers and business leaders.
This is an exciting new position where the successful applicant will have the opportunity to work on a range of Priocept projects for some well-known brands. The role would suit someone either looking to begin a career in software development or with a couple of years of industry experience.
Priocept is looking to hire a talented technologist to take a lead on various Java based development projects. They will work alongside other experienced software engineers in a supportive environment and gain exposure to a broad range of technologies spanning cloud infrastructure, DevOps and web development in addition to core Java.
Priocept is looking to recruit technical consultants and project managers that can demonstrate both consultancy skills and delivery expertise for complex internet technology projects.
Priocept is looking to recruit a bright and talented technology enthusiast to contribute to our development projects throughout the full project lifecycle. They will work alongside other experienced software engineers in a supportive environment and gain exposure to a broad range of technologies.
Priocept is looking to recruit Java software engineers that have a keen interest in CMS development, combined with expertise in developing solutions using the Magnolia CMS platform, or other similar expertise that is transferable to Magnolia such as CQ5, Hippo, Liferay or Alfresco.
Preemptible Instances on GCP differ from Spot Instances on AWS in that there is no concept of a “spot price” or bidding for the resources. This approach is much simpler than the Spot Instances concept, and can also be cheaper in certain scenarios, but comes with additional considerations which we cover in this article.
A standard pattern for software environment naming and usage, to provide clarity and consistency when planning software development infrastructure.
In this article we describe an opinionated approach to Model-View-Presenter development on Android.