I don’t like that approach, because people who work like that commit all kind of crap to repo or cry that GIT ate their homework…
Then we have line ending conflicts, file format conflict UTF8-BOM mixes with just UTF8 it makes more work for everyone like crappy PRs. Because of people for who those are things that „don’t matter in grand scheme of things”.
Hey not every rebase has conflicts. I definitely rebase when there are no conflicts, then merge.
When there are conflicts I merge „theirs” into my branch to resolve those so I keep mental model for this side and don’t have to switch. Then rebase then open PR.
I do the following to keep my sanity when doing something like rebasing a feature branch onto latest origin/master:
* First and most important: turn on rerere.
* Second: merge and resolve all conflicts, commit.
* Third: rebase.
The second step might look redundant, but thanks to rerere git remembers the merge conflict resolution. That makes step 3 have fewer conflicts; and step 2 tends to be easier on me, because we are only reconciling the final outcomes.
(Well, I'm lying: the above is what I used to do. Nowadays I let Claude handle that, and only intervene when it gets too complicated for the bot.)
I don't know, I think it's pretty embarrassing that Teams is an electron (or whatever) app. The plot on native has been lost so badly that even the fucking company that makes the OS doesn't want to deal with it.
Electron is the worst thing that happened to quality software. I spoke to two HR guys last year at the company I'm working at and they told me they ditch every single resume mentioning "web technologies" in them. Funny part is when they also told me these "bad" resumes are for the vast majority H1B wannabees.
Second. I wouldn't say we ditch resumes on that basis, but ultimately, we're a native outfit only. You can be the best damn app developer on Earth but if all you've ever used is Electron, well, I can't use you.
Say what you will about Apple, they at least still think it’s important to support and do native development, especially for their OS. Microsoft might as well have bought webOS as their new Windows replacement and admitted they’ve given up on native apps.
Do original Macintosh binaries still run on the latest macOS? I haven't looked much at the situation on that side but I believe Apple has no equivalent to the Win32 API.
NPM it's the bigger turd happened ever, slow and bloated. And JS today amounts the biggest enforced propietary loading method of existence in almost every web page.
Clown shit. “We’re made our own OS a nightmare to build on so we’re gonna use JavaScript powered pseudo-VMs and make everything take 2 gigs of ram minimum”
Author here. Deeply interested but not an expert by any means happy to have saved anyone a few tokens. I have done my best to fact check the content and the people on r/lisp have contributed a ton of corrections that I incorporated into revised edits. Always welcome constructive inputs if you have spotted any mistakes let me know.
Hi well you see it doesn’t matter how many times you will repeat „I am not an expert I did it for myself and just sharing in case someone else would be interested”.
Assholes will come out of woodwork claiming only experts are allowed to post anything online.
My point is, stop being apologetic as it only eats your energy and DGAF about such comments as the top one I replied to.
Thank you! Point taken and appreciated. Time is better spent on producing better materials. I have made a short version of the post as the primary article being too long was a valid criticism.
Have been there, we got pushback from users and we had to back off with releases. Users hunted product owner with pitchforks and torches.
As dev team we were able to crank the speed even more and silly product people thought they are doing something good by demanding even more from us. But that was one of the instances where users were helpful :).
People use dozens of apps every day to do their work. Just think about how are you going to make time to give feedback to each of each.
> Just think about how are you going to make time to give feedback to each of each.
That's pretty much solved by the size of the audiences. You won't give feedback on 12 apps, but 11 other people will probably do so on 11 different apps.
Of course, the issue with my domain is that there's plenty of feedback, and product owners just dismiss it. Burn down your entire portfolio to get that boosted shareholder value for the next earnings report.
And how do you solve that when you are one of those 11 apps when no one wants to talk to you because they have their work to do? Where you don’t have power to say that kind of thing.
Well by asking repeatedly of course but you just piss people off.
Have you ever given feedback to Atlassian, Google, Microsoft?
„I was able to vibecode those 5 apps I always wanted but never had time to code them myself … it is so different now because — I don’t have time to use them”.
That is wrong - the limit isn't time. The limit is you need to create a good ui so you don't need time. time is the limit for a fun game (see other comnents on how hard this is).
However an app needs to be a good enough ui that it does something for you and often they don't. Paper todo lists still beat all the todo apps people try to make because the ui works for paper. Paper has large limits and so it seems there must be an app out there that is better - but so far everyone has failed to create it.
SaaS companies/devs are in trouble - but for slightly different reason. That was the case already for something like 10 years.
Earlier if you had developers and no domain knowledge you were able to land a contract building application for a company and maybe spin it off to get more customers in that niche.
If you got lucky and you landed law firm and made case management for them you probably had nice little niche.
But as it turns out lawyers can also use JIRA, Trello, Basecamp or whatever and they really don't need Facebook for lawyers so those gigs dried up.
Main point is, software development alone is not going to bring as much money as it did earlier. You will have to have backing of domain experts to get the business going to offer something special in your SaaS. Like possibility to actually have call with those domain experts or their oversight on whatever it is you are doing but you not having budget or enough work to hire domain expert full time.
Then we have line ending conflicts, file format conflict UTF8-BOM mixes with just UTF8 it makes more work for everyone like crappy PRs. Because of people for who those are things that „don’t matter in grand scheme of things”.
reply