Fingers crossed everything is fixed soon.
3,394 karma · joined April 6, 2014
Fingers crossed everything is fixed soon.
I'm not sure this gives the right impression. Yes rename/squash/interactive rebase if necessary to tidy, however I still believe you should strive to create clear, separate commits as you go.
If you have to regularly make major changes to history before review, I could be a sign that your process/approach is disorganised.
I think we'll look back in 10 years and wonder why antitrust regulators did nothing, but it may be too late by then.
Most journalists and lawyers (although not all) believe that Wikileaks' activity is journalistic, and therefore that Assange can't be prosecuted for this activity. So the US is trying to charge him for other things, e.g. for helping others hack.
Whether other states have been involved in leaking info to Wikileaks... who knows? It's likely, because, well, why wouldn't they? However no one has suggested the info released by Wikileaks is false.
As far as money, I believe most of the Wikileaks funds have come from public donations and often their legal advice is paid for by friends or pro bono. So I don't think there's anything nefarious going on there.
What has been clear is that the US will go to extreme lengths to get him into a US jail, from discussions about rendition, assassination, and faking evidence (e.g. with a key witness in this trial), to significant political pressure on allies and other states to cooperate with them on this. He is an 'enemy of the state' in their eyes.
Lots of indies post there.
It's very hard to know the exact circumstances from one side of the story, but I agree wholeheartedly with voicing opinions when important, even if difficult or 'not your place'.
And of course, it's usually a sign something has gone wrong with people management if someone is very surprised when they're fired.
The problem is that Discord is increasingly being adopted by communities where voice isn't used and where ephemeral chat isn't helpful. E.g. All these crypto discord communities where it's impossible to find out what's going on unless you check the channel 24/7. A traditional forum would work much better for most of these cases.
The fact that Discord are trying to grow aggressively pre-IPO isn't helping.
The problem instead seems to be a systemic one. i.e. What kinds of posts does the platform incentivise and promote as a whole? However, changing the system would require significant product updates and harm the bottom line, as it would likely result in lower engagement.
We're also in this weird position where politicians seem to want to hold platforms accountable for content which is legal, but objectionable. This is also exacerbated by employee activists wanting to do the same.
It makes reading easier and writing faster. And no more time wasted on pointless formatting debates.
And as an iPhone user, the notch really isn't a big deal. In fact it's a positive because you get more usuable screen space.
Yes they're expensive, but, for something we use every day for 8hours+, it seems worth it.
If the rumours are true, the new M1X MacBook Pros being announced this Monday look perfect:
- high performance + battery life
- exceptional build quality
- great screen, sound, and webcam
- decent port selection
In my last role I ended up in a fantastic place where the teams under me could operate fairly autonomously and were happy. My only recurring meetings were:
- 1-1s fortnightly and only with senior members
- My 1-1 with my boss, again fortnightly
- Senior leadership team, once a week
I kept 1-1s to 30mins unless someone had an important issue, in which case I was completely flexible.
Most of my time went on planning/strategy, customer research, and acting as an ad-hoc coach for the teams beneath me.
The key things I found were:
- many meetings can be replaced by an update email
- decisions often work better through docs + feedback than big meetings
- you don't need frequent contact with the team if the goals and constraints are communicated very clearly
I realise none of this is groundbreaking. But it seems quite rare, and also hard to achieve in practice.
If you care about climate change, this doesn't feel like a particularly high leverage area to focus on.
Personally, I wouldn't waste my money on this stuff, but I don't get the anger. Perhaps people feel upset that others are making significant money from this and it doesn't feel 'fair'?
Their productivity was also significantly more consistent across a range of areas and task complexity, compared with other devs who would slow if working in an unfamiliar area or on a more complex task.
Finally, good (and bad) decision making compounds with software. The right high level approach can pay easily pay of 10x over time just as a bad approach will result in buggy, bad performing software, and multiple rewrites.
In short, this article does not match my experience.
Is there evidence that's it's hard for devs to get a job in general? E.g. The average hiring times for software devs (on popular platforms) in London was on the order of a couple of weeks.
I know from personal experience that junior devs from bootcamps were getting snapped up quickly - source, I worked for 3 years in the recruitment industry and also hired many devs in that time.
Doesn't seem to be a problem in general?
If this work was important, then why wait on another team who give you a "no telling when" reponse? Get the team together, and assign someone to do it same week. Don't do half-assed follow ups then complain when the dashboard team (which has already shown you it's not their priority) doesn't do anything about it.
If it isn't important, then go focus on the important stuff.
I think there are some potential performance benefits of liveview (less sent over the wire and less work done server side) however I prefer to optimise for simplicity and fewer bugs.
Edit. Caveat this with the fact that I haven't used Livewire in anger.
Fronted mostly static with Stimulus + Hotwire for a few dynamic parts.
Images via S3 + Imgix.
Metabase (also on Heroku) for analytics.
Trying to keep it as simple as possible. Not quite successful yet, but pleased with the tech stack so far.