iveqy

Depends on your application.

On the opposite I've seen many cases where sqlite3 scales better than postgres, depending on the scale and the application.

If you're doing horizontal scaling, sqlite3 is a very good alternative.

How did you know that the build servers only built trusted code?

If you doing it locally only, I don't see the difference from make that will just keep your old .o files.

If you using it distributed between different developer, how do you make sure the cache result is secure? A shared cache where everyone can contribute to is really hard (impossible?) to make secure. Someone could add malicious code the cache that then everyone will use.

This is great and really close to what I use myself:

while [ 1 ]; do inotifywait .{c,h} t/.{c,h}; make && make check ; done

You rarely see business requirements. You see an interpretation of them. Your job as an engineer is to understand the actual business requirements so you can question the interpretation of them and then simplify it.

With that said, many requirements are technical and then you've even bigger freedom.

Software seems like a very immature field where we can still do a lot to increase performance. I'm looking forward to the shift

The trouble is that requirements change. So you write it "the right way", then you get a minor requirement change that forces you to slightly bend the rules, which is okay. 100 requirement changes later your code is a real mess.

I was biking in the northern Sweden and stopping by a restaurant. I left my luggage on my unlocked bike outside while going in for lunch for an hour. Nothing strange about that, why would anyone steal a bike? Noone locked their bikes!

Instead of saying openess is bad, let's say what kind of society you would like to live in and then work towards it.

Personally I would rather not have a bike lock, nor door lock.

I belong to the second type. I believe it's a great asset to have in business. Most often less code means shorter development time and cheaper maintenance.

People knowing a framework will often use it for everything. Instead looking at the problem and find the easiest solution to it offers great time to marked.

I've proudly deleted more code than I've written at work.

minix also needs a mention here. Part of Intel Management Engine and close ties to linux childhood.

During the piratebay trial, one of the founders got a question about if he had met someone IRL. He replied with that they don't use that expression but AFK (away from keyboard) instead. Becuase IRL (in real life) suggests that internet is not real life, but it is.

What we do online effects our every day life even when we are offline.

I thought that was very sane thinking

isn't this something that should be done in your code editor instead? That is actually made for just these things

there's git appraise, however I find it a bit immature. I try to use it with a rebase workflow instead of a merge workflow and it completely fails with that.

Change the requirements. Understanding the requirements and adding your domain knowledge, often makes it possible to slightly change the requirements (in agreement with stakeholders) in a way that seriously reduces implementation time.

if it's for personal use and no access rights are needed, just use ssh.

If you need to add more people, but don't require access right for the git repos (i.e. everyone will be able to force push). Still use ssh, but create a git user and git-shell as the shell to improve security.

If you want to go one step up, I was looking at soft-serve, however it's too immature yet. So I added a git-shell-commands folder and added list command that will list my git repos.

It's really simple!

If you need access rights and reviews, things will be a bit more complicated. Although git-shell seems pretty easy to add some access rules to, if not gitolite is better. For browsing, cgit and gitweb should be obvious choices, however I don't really see the point for a minor site.

For code review, I'm really voting for git-appraise to take off. Once I get a coworker, that's what we will be using.

Just the latency is really important to me! I even built an ERP system that has a response time below 100 ms for all operations, it's a design goal.

My thought is that if you can see consumer changes depending on latency (for example on amazon or google) it is equally important for internal tools. Employee time is expensive.

All comments is about developer experience. What about user experience? I find many framework adding a lot of data, loading times, etc. for little gain for the user.

I used to never find my pencil and continue to have to go and fetch a new one at the office. Then I bought a 200 usd Lamy 2000 and now I always have a good pen at hands.

I used to have a pile of coffee mugs piling up at my desk at work. Then I bought an expensive designer coffee mug and only used that one, suddenly my work area is clean.

It's about knowing how you can trick yourself to without any effort increasing your well being. I've flaws, sometimes I can buy then away by tricking myself.

I guess it depends on your references. Chrome is horrible slow on my c2d. It runs fine though. Lagrange is of course much faster than chrome, but it's still noticeable slower than I expect.

It's a really bloated browser, barely working on my 11 year old core 2 duo.

However, it's way the best geminibrowser there is! It's beautiful and well built. I'm using it everyday on my macbook air m1.

This is no toy like many other gemini things. This is awesome

I've always failed to actually have a personal site. I've one for my startup https://www.dahut.tech that I'm pretty proud of, it's slim and get 100 points on pagespeed.

However I've setup gemini://iveqy.com and actually started blogging. First I wasn't really sure if it's sane, but every blog entry gets over 100 reads and I often get comments on them. That makes it fun!

What do you think is broken with git submodules?

It's a common problem with git as well. Running git in a dropbox folder is discouraged.

No it doesn't.

Write in a plain text editor, have evince open the generated document, it will reload when updated. Then use inotifywatch to generate on save, or just write a hook in your text editor that will update the pdf.

You don't need to use overleaf to get the overleaf experience...

I know many successful and high paying individuals who just doesn't care or understand technology enough to have decent hardware. Even if you buy premium hardware, it will get old and slow after a decade.

So was this advice or marketing material? ;)

Maybe both.

Nice to see that more that myself are struggling with this.

This makes me worry less about the end of Mores law. It's clear that software development still has a long way to go.

I'd a point and shoot, minolta dimage x31. I loved it! It was early to have an SD-card which meant that I could film more than 5 seconds (until RAM is full) because it was fast enough to save to the SD card while filming. It also had an internal optical focus which meant no (few) moving parts on the outside.

This was actually a hard one, i previously had a background image that I had to drop.

Landing pages are hard, specially of they should be both beautiful and good.

Very nice writing except the python part. Just 2to3 really have been a maintenance pain for me. The hardest part with script languages to actually know if somethings is wrong or not without extensive testing.

Writing something maintenance free should be done in a compiled language.