likortera

12 ms·

121.
by likortera 4y ago
We're not talking here about documenting apis. We're talking about documenting an architecture, how pieces work together, what tools are available, where to put things, etc. Check the documentation of any major web framework. That
122.
by likortera 4y ago
Maybe I'm not that interested in how nice it looks and more in how many people are necessary to maintain it and provide something useful to customers at a reasonable cost for my employer.
123.
by likortera 4y ago
My day job is as a JavaScript engineer, mostly doing React and Node. Some PHP which I never used before. Last year during the pandemic I started to work on a side project, I picked Laravel because I heard a lot of good things, and having us
124.
by likortera 4y ago
Well, the usual "reasoning" is that Go is easier to maintain, faster, will require less hardware, etc... all of those things might be true. What is not told in is the other side of the story, the one where you will have to write,
125.
by likortera 4y ago
What other places do you hear/talk about technology, outside of your day job?
126.
by likortera 4y ago
Something like Laravel + alpinejs running on heroku or Google app Engine or a similar platform is what 90% of the typical crud saas webapps most of us build need. But we definitely have more fun with React SPAs and Go microservices on Kuber
127.
by likortera 4y ago
Can't agree more with you. In my more than 20 years in this industry I'm still to find one single person at work, or a single customer with JavaScript disabled. At this point if you have JavaScript disabled is your problem. It&#x2
128.
by likortera 4y ago
Don't know nowadays, but a few years back when I was still using python something that drove me nuts from pip was how bad it was at managing transitive dependencies. If package A depends on package B 1.0 and package C also depends on p
129.
by likortera 4y ago
I've been at a company that did this, they started migrating everything to Go because it was the new cool thing to do and everyone was in love with it. One year later it was a mess of network calls, no ORMs and nearly-raw queries becau
130.
by likortera 6y ago
Go is to backend what React is to Frontend and what Kubernetes is to infra. Everyone wants to have fun. And when things get complicated enough just switch jobs.
131.
by likortera 6y ago
> That's what Go is for. Go is for doing the things that Google does on servers Definitely not, unless you are google. Go is great for hardcore backend and systems programming, as a replacement for c/c++ or Java. For most compa
132.
by likortera 6y ago
The folks you're talking about are a lot more expensive (in Europe at least) than the equivalent folks for more traditional platforms. Again, and without centering ourselves in pure technical and our own careers and CVs. How does that
133.
by likortera 6y ago
> Maybe consider paying your people more Salaries are actually pretty good. Not facebook salaries, but good enough and certainly above average. The company can already get very proefficient, experienced developers in Ruby and JavaScript.
134.
by likortera 6y ago
Meanwhile te company I work for is moving away from it. We cannot find enough people with enough knowledge to be already productive in it. Not many want to learn it because it is considered pretty niche, and the ones willing to learn will n
135.
JQuery Mobile is awesome(reddit.com)
1 points by likortera 10y ago|1 comments