justinmarsan
Joined 13 years ago
Joined 13 years ago
No I feel that's how it should be everywhere.
> Nobody is making anybody do anything.
I strongly disagree with that part. A CEO as an individual is not, indeed. But capitalism and the job market in general is forcing people to work, for sure... And even though the global wealth keeps increasing, and rich people keep getting significantly richer, the situation of the poor does not improve, and sometimes social benefits are reduced, access is made more difficult... Because it's important that some people still "agree" to work low paying jobs...
Is it really a fair choice if the alternative is to lose your home or starve ? This is exactly why child labor is forbidden for example. You can tell it's morally wrong. But it's been explicitely forbidden, because it used to happen, and people who defended it were claiming that it allowed kids to help their families and so on, but it also drove wages down, increase the workers' pool so they would compete more for the job, etc...
Maybe the market feels fair to you because you have skills people compensate for, but for people working minimum wages jobs, the market isn't fair, they absolutely have to get those jobs, otherwise they're on the streets...
The actual people doing the actual work, day to day, talking to prospects, building the things... But you had the idea, so it's just natural that you get the vast majority of the reward.
Maybe that makes sense to you... And like I disagree, but that's cool... But I cannot picture myself ever becoming a billionaire... I would have shared so much with the people that contributed to make me be a 100-millionaire way too much to reach the next step... And I'm sure I'd be happy to have 100 millions, and have people happy to get great compensation to do that with me...
Still, I agree it's not stealing. But the fairness of the situation is still up for debate.
The next morning I figured the same LLM could compute that on my code, so I asked it to make an agent to do so, and report issues to me...
And then I ran that agent with next to no changes on a feature that had grew organisally over the last months, that I knew was messy and sometimes difficult to work on, despite being unable to precisely say why... And it did tell me exactly why, and proposed changes to improve stuff, and then implemented them...
Up until that point, I'd felt like the LLMs always produced bad code, that worked for a specific feature but often broke stuff or evolve poorly over time. Then I realized if you had the LLM do code improvements, it could do that fairly well too...
It's well known though that as you build muscle, your rest calorie consumption increases, so probably if you build/maintain enough muscle, then you can just outrun your intake, since you consume more without doing anything to start with...
If you compare yourself with someone that's sedentary but also not eating right, than yeah, possibly you're even with an overweight non-smoker, overweight being linked to so many diseases... But if you compare yourself to someone sedentary that eats properly, or let's say as well as you do, for the sake of good comparaison... I wouldn't be so sure... The damage you do to your lungs and heart tissues are unlikely to be offset by the little time that you spend at the gym or on your bike...
This coming from an also fairly active smoker (now vaper).
One issue I've seen since then regarding retros is that they'll fall into two extremes. The rare one is that retros are just fun recess times that nobody gets anything out of besides doing doodles and ice breakers. The other one is that teams will try and be very action oriented and find concrete solutions to concrete problems, but will not have the emotional maturity to address difficult topics, so they're either avoid them or turn into screaming matches.
You need to feel somewhat close to your coworkers to be able to bring difficult topics with the certainty that others will know you do it for the right reasons and that you're all trying to work towards the same goal of making work more effective, pleasant and satisfying. Teams that never work on the closeness of their members cannot address important issues. You need the doodles, the inside jokes, the team spirit to be able to do that.
But you also need to have a mastermind to spot issues and then figure out ways to role play and brainstorm around those in a way that feels like playing, but ends up providing the team with actionnable solutions.
At the company i've worked at, I've had to sometimes do tasks that were really not my duties (data entry, QA work) because it was the most important thing that I could do for the team. I happily did it because I felt like it really was our project, that I'd be bringing value to customers and the company in doing it, and that our product would be better with that work done by me. I'd stay late if there was a problem I could possibly assist my coworkers with, even if I stayed for nothing or could only contribute through naive questions to try and get neurons firing... But we were a close team, despite having different roles and seniority levels, and we were all very happy to do what the project needed.
In my current company the sense of ownership isn't as important, people don't know each other as well (the team also is larger and with more turnover) so it's made of smaller groups of kinda close people.
In a perfect world everyone in all teams would be a trustable high performing dev and there would be no need for any lubricant to make the machine work smoother, but the reality is that the majority of us have pet peeves, quirks and shortcomings, the group can be a good way to mitigate those, as much as processes and methodologies, but having both is what will get you the best results, and I think this is something that is overlooked by many teams.
I'd much rather use a <button> that exposes itself as such and has well known interaction functions, then create my own div and have to handle the clicks, keyboard navigation, navigation shortcuts and so on... That actually requires a lot more knowledge than HTML semantics, and unless you test frequently with expert and non-expert assistive tech users, you won't know what kind of UX issues you'll be creating for them...
My wife keeps her phone on silent but loses it multiple times a day. We use the computer to make it ring using Find my Device, but it'd be a lot easier if I could just do it from my phone, which I can if I install the app and then add her Google account to the accounts on my phone, but then I get access (and notified of) all her emails, google photos and stuff like that.
Is there an alternative ? Some way to just have both phones agree to sync somehow and then one can make the other ring, regardless of sound settings.
Also did I tell you about CSS-only triangles ?
Also I'd like to know how I'll be alerted, will I get an email for every single mention or is there the possibility to have hourly/daily/weekly digests ?
Either way I think this is a good alternative to the other services out there and I could probably see myself using that on a side-project soon as the fairly low price isn't a barrier to me at all ! $7 is like free except you get money, unlike the limited free trials that get very expensive for the lowest plan available.
Nice work, bookmarking and eager to see actual results !
It's so easy to ship a lot of code, more effort should be put into ensuring the code is correct, with self-improving feedback loops that involve developers, and dedicated tooling...
But again, a while ago, everything was about prompt engineering, and now you can express you idea vaguely and get a somewhat working result, so this likely will evolve fast as well...