As someone who got sick of old school PHP and server-side rendering, mobile development, AngularJS/Angular/TypeScript madness, backend development, pure database development and what not I can tell you one thing: Everything is in our head and it's all because of the fear of staying behind. Once you start listening to yourself and once you start focusing on solving the problems as simple as possible, you will be happy in doing any kind of work. It's OK to be aware of new technologies, but you should use only those that make you happy and that actually solve the problem in a simple way. Why should I feel guilty if I'm not using some technology? Keep in mind that many technologies, frameworks are just products and the main reason behind the hype is money. Focus on general topics like software architecture, clean code, algorithms, best practices, database design skills and make sure to isolate yourself from hype.
As much as I completely agree with your attitude, and try to live it myself, software engineers don't get to make their own tooling choices. That is the fundamental problem here.
We don't get to choose the technology(framework) that will result in the least amount of hassle and easiest to maintain software artifact. Instead, we get stuck using what someone else chose for us.
I would suggest you not to choose Blazor. It's not that Blazor is bad or that I have something against, but you don't want to limit yourself when it comes to finding a Blazor developer. You will hardly find a frontend developer who is focusing on Blazor.
Today are React, Angular, Vue or similar frameworks the best way to go, especially for a startup where you need flexibility. Keep using .NET for a backend, provide a nice API and implement frontend using already mentioned frameworks.
Finding developers with Blazor focus/experience, seems to have two sides. One is .net developers really want to work on Blazor, and other is that not many have experience. By "choose boring technology" standards, these are both red flags.
However, I wonder if it is more work to implement Vue than Blazor considering my existing stack and that much of app is already developed. Razor pages use the same syntax as Blazor.
I think everything will be better if they implement their guidelines in actual input forms to force users to provide more information and more context - not only in questions but also in answers. It's so easy right now to comment and pollute the thread and that's what they have to tackle as well. Besides that, more moderators and people reviewing what is posted can also help. Comments like "thanks" or "can you provide more context" should be on 1 to 1 basis, more like a messages.
SO is a very helpful website and companies are not even aware enough how much it helps them and how much money it saves globally.
Great idea :) My only question is how the authentication works there...? User has to be logged in on the worker phone's app in order to do something on Instagram. I mean, I don't think anyone shares his Instagram password with an 3rd party software. Or you provide the services which can be done from another(your) Instagram account - which is then signed in on all worker phones?
> I mean, I don't think anyone shares his Instagram password with an 3rd party software
You'd be surprised.
They already share the passwords with their marketing agencies, where interns basically type them in on their personal phones (in sometimes quite large companies!). My service lets all of those people use the Instagram account, but only their admin knows/sees the password. If we can keep it as secure as their own internal processes, then this is a fair-enough trade off for many companies.
There are many decisions that you can make to improve the quality of your codebase. There is no a recipe that you can follow because each application is different but there are some general things that can make your life easier.
Here are some tips that helped me a lot:
- Keep your solution and tech-stack as simple as possible
- Mark those parts that can change often and try to make them configurable (when you have it configurable you don't need to change code and re-deploy every single adjustment)
- Make sure you have a good and readable logging
- Use DI
- Separate your application core application logic from the infrastructure part (DAL, Network Communication, Log Provider, File readers/parsers and similar)
- Keep your functions/methods clean and without side effects
- Method has to return something (try to minimize the usage of "void" methods)
- Split each feature or functionality you are working on into small pieces and compose the final thing with them
- Be disciplined about your naming conventions and code style
At least in Bosnia, there are no variations of the börek. There is only one börek - with meat. Other "variations" with cheese, potato etc.. they have also a different name. Basically if you order a börek, you will get it with meat.
Yes, this is a common "fight" between people in Bosnia and neighboring countries:
In Bosnia, "börek" (or "burek", as is its local spelling) is only filled with meat, while the rest of the dishes fall under the broader category of "pitas" (or pies): sirnica (filled with cheese), krompiruša (filled with potatoes), zeljanica (filled with cabbage), jabukovača (filled with apples)...
In Serbia and Croatia, they're all "burek" with different stuffings, so burek with cheese, burek with potatoes, etc.
It's a weird hill to die on, but you will receive some weird looks if you request just "burek" in Serbia/Croatia/Montenegro, or "burek with cheese" within Bosnia.
Zeljanica is, despite its name, filled with spinach rather than cabbage. Then there's also an abomination called "pizza-burek", it's probably as bad as it sounds...
I was also impressed by Netlify. I tried multiple other solutions to host my website but Netlify was my favorite at the end. Easy to setup, free and fast. I configured my account, access to Github, deployment, custom domain and SSL in 5 minutes.
First of all, I think C# as a language and .NET (Core) as a framework were good and are still good choice. You can build whatever you want with it. I don't see too much advantage when you now pick another language for the same purpose unless you are somehow limited with C#/.NET. If you want to be more valuable on the market you should focus more on what you are able to build. It's more valuable when you say, I'm able to build a web application (classic or SPA), work on the database projects (performance, complex queries), I'm able to setup an architecture for a distributed system, I'm able to build microservice cloud hosted systems etc...
For every single thing that you are able to build, you pick a language or tool that suits you the best and just keep improving. Each language has it's pros and cons but, IMO, what matters the most is the code quality, architecture and the things I mentioned above. Better focus on those skills.
If you write nice structured, good organized PHP code (e.q), that is stable in production and which is easy to maintain then you are far better engineer than someone who is showing off with his Rust or Haskell unstructured, not consistent and in the end unstable code. Don't let the trendsetters put pressure on you.
In the end, if you are are really bored with C#, try to learn some F#. It's also .NET but it's a different type of language and if nothing happens, in the end, you will write better C# :) Personally I think that SQL is also a good investment. Most of the people avoid it, I don't know why, but there are and there will be always jobs for a good SQL developer, especially in big companies where the salaries are also higher.
Maybe you should just change the type of the software you build. If you are writing business software I completely understand you. At some point I was also considering to keep programming as a hobby and to start a new career in some other field. However, in the end I realized that I will throw away a good salary and already organized life without even having a clear alternative path. Software development is always a fun if you have a good team that loves software and management that understands the importance of software. So, my suggestion is to find a different industry for which you will write software and to find a company that takes the software development seriously. Whatever path you take, good luck :)
