It masks the complexity of your statement. I know in ruby we had the same issues with the “try()” method. Our rule was, do or do not, there is no try. :)
For software engineers we ask to bring a piece of code with them that they wrote. It can be anything. At the interview they first show what it does, and then we go through the code together. We ask some questions about why they implemented it a certain way. When doing that you can already see how people think and if they wrote it theirselves. It’s pretty interesting also to see what keeps other people busy. It removes a part of anxiety because they have written it themselves.
I am working as a java developer now for about 3 years. Before I worked 5 years with rails. You are completely right, a spring boot application with Lombok doesn’t come near a rails application. Also what people tend to oversee is that the recompilation step really takes a lot of time.
When I was younger I had similar experiences with customers who ghosted when their needs to be paid. The lesson I learned is to make sure you keep control over your code / env until the customer has paid. I implemented some mechanism in my sites that when they ghosted me, I just did a special api call which cleared the database and showed in big letters that this website was stolen. Suddenly there is contact again.
Ever looked at Azure Event hubs? We’re usung this as a Kafka alternative because it’s way cheaper actually (for xx million number of messages with a throughput of 4 MBs per second its 75 €) then setting up a full Kafka and keeping it running? Or do you see disadvantages on that technology? I’m not trolling or so, just curious.
Belgian here. Day rates of 400+ euro are the normal rate over here for java and php developers (even to the lower side) for freelancers. But I should mention that you lose about 55% on taxes of it.
I read the article, and it indeed addresses the issues that I'm currently facing. Although that the comments also mention about QA testers without development experience, which can be a good thing. How to fit these people into scrum?
What about error representation? Most of the time I find that actually representing errors is the hard part of creating a REST api.
You usually want some representation of each field, plus maybe a generic one. I always have troubles with this. Is there a standard or a proper way to define/do this? I would be very interested.
The reason I use the web interface and not the app are following:
- you can't disable notifications
- you can't secure your app (aka Pin protection or a password)
- huge battery drain as it is constantly connected to the internet.
The web app is easy. You log in and you check your messages. An alternative for android that I have found for Android is called fast Facebook. It shows a web view of the chat and ignores the market:// redirects. Which is already better.