I'm a product engineer with 10+ years experience working at the intersection of design, engineering, and product. Comfortable owning products end-to-end. Have worked at companies like Uber and Volvo Cars, as well as smaller-startups where I wore many hats (tech and projects wise). Most comfortable in start-up environment, or mid-size companies. I have been working remotely for startups for the last 6 years. I can bring your project from 0 to 1, or contribute to an existing team.
Open to full-time, part-time or independent contractor (freelance) positions.
Technologies: JavaScript/TypeScript, React/Next.js, Node.js, Solidity, GraphQL, Docker, and a little bit of everything else...
Email: hi@krl.is
I'm a full-stack software engineer who enjoys building useful, well-crafted products. I have a diverse set of skills and can effectively prototype and/or develop full-fledged web apps. I also dabble in the Web3 space and can write secure smart contracts or develop dApps. I've have worked at small start-ups, as well as big companies, doing what needs to be done to deliver great results.
Do you know any good repos I could look at to see how actually practical front-end applications look like? Of course, keeping in mind it does all you'd expect a typical web app to do like CRUD, etc. I feel like I'm deep in the rabbit hole of Next.js + Apollo GraphQL but am interested to simplify whenever possible.
I've been doing web dev for almost 10 years and I've been extremely impressed with Next recently; I think it's the most "practical" framework out there right now assuming you're not wanting to go 100% client-side or 100% static-rendered (you can do each of those on their own very easily without it). The way it lets you mix both, as well as server-rendered where needed, is a game-changer.
I'm more ambivalent on Apollo/GraphQL, but I know some people have been happy with the decision to use it
One of the things I did, was draft a complete design of the project structure in advance of actually writing any code. This included only the essential features with no additional bells/whistles in order to prevent feature creep.
By the time my two team members formally joined, the above design was already split up in manageable chunks of tasks which could be worked on in parallel.
In addition to the above, we decided not to decouple the frontend and backend, but instead used Livewire in conjunction with Laravel & Alpine. This, coupled with Tailwind's UI components (tailwindui.com), helped us spend very little time on the frontend aside from a few specific aspects.
Education is long overdue for disruption, so whatever moves the needle even a little is huge in my eyes. And it's the first Lithuanian start-up that I know of to be a part of YC, congrats, this is a great win!
As I recently realized, it’s been 10 years since the first time I got paid for programming work. Decided to jot down some thoughts and share, hope there is something useful for everyone :)
I’m ashamed to say that was me at some point. On top of that, those articles did nothing to further my career. All that mattered so far is my past experience, projects and how well I can (leet)code. Now if I start blogging again, it will have to be purely out of intellectual curiosity.
I think this is the same situation a lot of people find themselves in. I would say I'm the same. The further along I get in my career the more I find I'm interested in learning or exploring for my own good or interests, rather than some fake sense of credibility I got in the past.
Also me, but I did have one (on tolerance analysis) that helped my career.
It made rounds in the professional circles I traveled in and established myself as, while not necessarily a leader, someone at least very fluent in a particular process.
This was also in 2010 though, so the social landscape Was quite different
I confirm this doesn't do anything for your career, or at least not as much as just focusing that time on actual, paid work. I find that in my career my resume and experience that's on it as opposed to any side-projects or attempts at writing.
Yes, however on helping the career I think the writing is like a nice little detail on the resume, a way to make it standout a bit more, I also found that in a recent interview for a project an article I had just written on SVG was naturally relevant. As a general rule talking about little articles you've written isn't going to naturally happen in the interview because the interview process is focused on past work and horrible trick questions.
It has also been somewhat useful in projects where a concern with documentation has been expressed because the writing is a better example of my ability to document things than having worked on a lot of projects where you may be able to go see what we shipped but not be able to see anything of the documentation.
I think of the writing as the equivalent of a side project:
* it allows me to focus on something I want to learn
* it helps to make what I learn stick in my head
* it gives me a deadline and people who will send me emails to say how's it going with that
* it works as documentation for what I've learned
* it gives me a trivial amount of money for having taken the time to learn something. Basically the last article I wrote is paying for an annual Dropbox account, and a couple days worth of food for my family. It was way too much work for that to be worthwhile, but I did learn some things that will help with later stuff.
Can attest, once racked up $10k AWS bill due to a silly mistake, got it nulled. That was a great lesson about how fast things can go wrong with pay-as-you-go pricing if not monitored.
It's embarrassing to write that now but I accidentally left private key for EC2 instance publicly available on GitHub. And I think what happened is that a bot scraped that key and used my resources to mine Bitcoin.
This seems quite common. I have heard several stories to this effect. Faulty firewall settings or keys committed to the repo seem to be the common two.
Open to full-time, part-time or independent contractor (freelance) positions.