So my best experience over the past year in the front end world (React only), has been with Vite using the react-typescript template. You get to use es modules (modern js) without any trouble and typescript just works.
For css, I usually don’t bother with any advanced framework, I commonly go with mui, but you can just do css files or css in js.
- Also experience with: Java & Python (prefer not to work with except for refactoring legacy into Node/PHP/Go/Rust), learning Rust and Go, tapped into Assembly (x86)
Hi! I am seeking an opportunity where I can challenge myself and grow as a developer. My background is in Full-stack development with DevOps, and over the past year I have enjoyed my position as a lead developer where I got to dabble into Systems Architecture, something I really enjoyed.
If you are seeking a pure manager for your next project, I am not your candidate. However, if you are looking for someone who works well in a team and is easy to integrate and onboard, I might be your candidate. I enjoy working with the team to discuss and find the best solution to a problem, and I have no problem taking initiative or working independently. If you need a proof of concept to test out new technologies for your business, I am also not afraid of working outside my standard scope, and can easily pick up and evaluate foreign stacks due to my experience in multiple languages.
If my profile interests you, feel free to reach out for a chat and a virtual coffee.
If you are looking for a developer who can work across the stack, and work together with your team to explore new opportunities, send me a message or schedule a meeting via my website!
Why me?
- You are looking for someone to create a new product or refactor an old codebase.
- You need someone with experience in developing internal architectures.
- You want someone who is not afraid to learn new skills, and who learns them fast.
- You need a person who knows how to prioritise and balance speed against quality when it matters*
Why not me?
- You are only focused on pushing new features without considering the maintainability of the codebase.
- You are not located in the EU OR are not able to provide a work visa for the UK.
- You are looking for someone to maintain an old codebase.
- You do not allow/provide your employees to develop new skills as a part of the job.
- You do not have a team of employees who love to spar ideas with each other to find new solutions.
As a devops engineer who also writes a lot of code, I started using Deno (https://deno.land) since I can write my code in JavaScript and TypeScript. I can also natively use wasm, and have an internal repo for hosting commonly used functions since Deno loads files using url imports.
Hi! I am a Full-Stack developer with the majority of my experience in web development. I am looking for opportunities to learn new skills, and where I will be entrusted with ownership over my projects. One thing I enjoy, is creating new applications (or refactoring old ones) where I can be a part of deciding and researching the best architecture for the task. Previously I have worked well with a remote team, but I have also worked on multiple projects by myself.
If you want someone who loves to learn and experimenting with different technologies to find the best suitable solution to a problem, and who is not afraid of making decisions either with a team or independently, feel free to reach out.
I was not aware of logging of this type, I am mainly familiar with Source Control. Could you explain to me the purpose of the Log file compared to Source Control? Do you usually use both?
What you are talking about is called "commit messages". Logging is used by an application that you are building to store information that is useful for helping find out what happened in error conditions.
As for your questions, I tell junior programmers to try to commit their code at least once every 20 minutes. That seems like a very short time! However, when you are first starting out, it is easy to take on pieces that are really large without realising it. This helps you keep the work small. It also helps you understand when you are in trouble. If you find that you can't commit something in 20 minutes or so, it's a good indication that you probably need some help.
When making your commit message, you should have a short message at the top explaining what you did. To understand what is good to write, imagine that you want to know, "How do I do X". Ideally you can search through the commit history for "X" and you will find a commit that does it. That's a good way to learn how to do things in the code. Now that you know what you want to look for, try to write a message that makes it easy for the "future you" to find it.
Finally, underneath the short commit message, try to write a brief description of why you made your change. If you think it is obvious, there is no reason to write anything. But I find that I write something about 2/3 of my commits. If you find that you can't think of something to say, maybe you are having difficulty understanding why you are doing it yourself! It's sometimes a good idea to ask someone "I know I have to do this, but I don't really understand why. Can you explain it to me?" Very soon, you will understand most things in the code.
There are lots of systems. Obviously the easiest way is to just write some text to a file. There are some libraries that make logging easier and give you some extra facilities (like formatting the time every time you write to the file, etc). There are also some services that allow you to manage logs for a lot of systems. Google has a service called stackdriver. You send messages to stackdriver and then you can go to the stackdriver service to see all the logs for all your systems.
Logging is a big topic and there are as many ways to do it as there are programmers. Some people like to log a lot of stuff (for example, every time you enter and exit a function, some people will write an entry to the log! That way they can see how the program is running. Personally, I hate that :-) ). Some people like to write only error to the log.
For css, I usually don’t bother with any advanced framework, I commonly go with mui, but you can just do css files or css in js.