I had been working as a developer for a good 12 years when I was approached by my manager, and asked if I could assume the position of team lead for a while. I was humbled to be asked - however the mere thought of performing some of the tasks required by someone in that position in that particular setting was very frightening.
Pia Solheim og Hilde Marie Flesland Torall tar en prat med Camilla Brustad-Nilsen som er digital forretningsutvikler i Storebrand
«Hvis du ikke betaler for produktet, er du produktet».
When using fully-managed Azure SQL databases, there are mainly two different cost/resource models to choose between. In my team, we have been running the Standard tier, which has a fixed amount of resources provisioned, and thus a predictable fixed cost. The alternative is the Serverless tier that scales the database on demand, and instead, you pay-per-use. One of our important production databases uses a lot of computing power while performing various tasks once every morning, and then smaller sporadic load the rest of the day and night. A good fit for the Serverless tier? Could we achieve the same performance at a reduced cost? Read on, and I will let you in on what I figured out.
As frontend developers, our focus is on the users experience in our application. How fast and efficient the application is and how smooth the functionality can be. We all might say security on our minds, but we often rely on somebody else to handle this. Luckily, modern web frameworks, like React, come with built-in security against one of the dangers of the web – Cross Site Scripting (XSS) attacks. But what does React actually defend us from and more importantly what does it not?
As developers, we usually use some sort of pipeline to build and deploy our code. Tools like Circle CI, Gitlab CI/CD and Github Actions are popular. Can your pipelines be a security vulnerability? Can you use your pipeline to create a more secure application?
Blås i dævve personas. Blås heller liv i innsiktsarbeidet, og lag historier du tror på selv. Det er først da du kommer nærmere de faktiske folka som bruker produktet ditt.
The Kotlin standard library has a lot of amazing stuff and today we will take a closer look at what let, run, also and apply is and when to use them.