stkni · HackerTrans

năm ngoáidiscuss

Think I'm with Larry on this one. Someone should chair the meeting and there should be some expected outcome (decision) from it within the alotted time. If we're 45 mins in and no closer to an answer it's time to assign some investigative actions and regroup? Malicious compliance in this context is good, because it creates an environment where meetings end and everyone gets to pee?

stkni

2 năm trướcdiscuss

This is seriously impressive. I asked it to create 3 different databases:

- a customer orders database with products with a timeseries of prices, and multiple fulfilments per order. - an issue tracking system with a reflexive user/manager database - a family relationship model

In each case I got it to put in sample model and then asked postgres.new to answer some questions about the data it had inserted. I thought the family model would trip it up, especially when I told it to put in cousins and uncles. But no, it was pretty bang on.

The only thing it didn't quite manage is that some of the relationships are reciprocal (i.e. my sibling also has me as a sibling).

I asked postgres.new to review the data and it fixed some, and i asked it to check again and it fixed the rest. This is a very useful tool that I can see myself using!

stkni

2 năm trướcdiscuss

I'm genuinely baffled by this, why are the tax filing options in the US so fragmented? Here in the UK there are probably some situations in which you can't use the online, government provided, free service. But I'm going to stick my neck out and say they're fairly niche.

Having lived in the US I know things get complex when you start mixing in state taxes, but this is federal taxes right? Or wrong?

stkni

3 năm trướcdiscuss

>> And then there's the competition - I early discovered that I could never outperform my competition.

100% this. I'm a bit competitive, but only a bit :). After 20 years of being a dev I realised I didn't want to compete anymore and shortly after that I quit as a dev.

I've now switched more into an analyst role and because I've been a dev i think I know what makes a good analyst because I know what I would have to know to write the code - if it were me. But here's the best part, the mark of a good developer is their attention to detail. And attention to detail is also the mark of a good analyst, but as an analyst you don't have to sacrifice yourself to the detail of tool-chains, stacks and frameworks.

Working on large scale problems as a dev, and doing it right, is slow (with a small number of devs) and chaotic with a large number. But as an analyst I can work at the speed of thought, work on many projects simultaneously, and see the fruits of my ideas take shape as the devs start to deliver them and I shepherd them into existence.

So for now I'm pretty happy, I write code in my spare time for fun and like the OP - I'm back where I need to be.

comments