FWIW I'd think the westernized version would then "retaliate" and favor western over "eastern" users.
That's NOT really creating trust...
124 karma · joined May 16, 2014
FWIW I'd think the westernized version would then "retaliate" and favor western over "eastern" users.
That's NOT really creating trust...
That's essential as you should really "own" the solution you sell and take money for, as you're responsible for what it does on your customers' hardware.
- more bugs becoming visible that were hidden within the software we use daily
- more bugs (in absolute terms) as more people create more software in a very short amount of time (regardless of their professional training)
- less bugs in existing software as the developers and dev orgs of existing projects is capable of automating bug hunting, test case creation, ... in essence: They get a multiplying effect out of AI regarding their capabilities.
In short: Actual developers with actual experience (the more, the merrier) can do better work while the barrier to enter "the market" for untrained individuals is a lot lower resulting in a huge amount of new software whose "success" is to be determined.
Writing code is not the bottleneck anymore, making decisions is. Making the right decisions needs context and thinking. A coffee break might actually help productivity. Driving a Ferrari full speed in a crowded city - only because you can - doesn't make the outcome better.
We need to learn to be more conscious about the impact our way of doing things has.
Suffice to say they need to get their own search index fully filled and stop using Bing (or whatever US-based) data. It's a process...
Kudos! The site rocks as well! I also have an api-first SaaS (see https://thelawin.dev), but it unfortunately needs a bit more explanation.
Best, Steviee
I created a little Github Issues replacement for myself that puts the issues within the repo so that the work and the todos stay in sync. https://github.com/steviee/git-issues
And I bet there's numerous other projects like that.
Hope you get your submarine, man! ;)
Love it! Merz (and our minister of commerce Reiche) is a desaster for Germany and all of Europe. Tump attacks Iran and Gas prices hit 2,12€ (and even more) per liter and still they think betting on fossil fuels from their dictatorship-friends is a good thing.
Saving Earth is just not cost-effective (at least not for the "right" people).
Especially when building new and unproven applications I'm always looking for things that trade the time I need to set tings up properly with he time I need to BUILD THE ACTUAL PRODUCT. Therefore I really like the recent changes to the Ruby on Rails ecosystem very much.
What we need is a larger user base setting everything up and discovering edge-cases and (!) writing about it (AND notifying the people around Rails). The more experience and knowledge there is, the better the tooling becomes. The happy path needs to become as broad as a road!
Like Kamal, at first only used by 36signals and now used by them and me. :D At least, of course.
Kudos!
Best, Steviee
In the end what matters is that you can produce the functions that make your product valuable to your customers. You need to Do it on a daily basis and always on time. Ruby on Rails helps you with that.
General advice: Do not choose the tech stack for generating your income by following fashion. It is a marathon and not a sprint after all.
I'm currently working in a Typescript environment that somebody choose for "reasons" (types, hiring,...) and I regret it every day. I'd go with Rails anytime.
congratulations to you and your team! One thing a developer becoming a teamlead needs to learn is letting go.
Changeing the mindest from a maker to a mentor.
Hope it helps!
Kind regards, Steviee
Slack time usually is spent chatting, working on other stuff, getting coffee, browsing the internet/reading. Most of the time it's work related so it's also useful in the end.