134 karma · joined April 20, 2021
Maybe look at Ireland or Portugal as examples of republics where the president keeps the constitutional safeguards (dissolving parliament, vetoing laws, and what not), and you'll see that they are not exactly polarizing figures. Instead, the prime ministers are, as they should (they head partisan politics).
[1] "LLVM: A Compilation Framework for Lifelong Program Analysis & Transformation", Lattner and Adve. https://llvm.org/pubs/2004-01-30-CGO-LLVM.pdf
[2] “MLIR: Scaling Compiler Infrastructure for Domain Specific Computation”, Lattner et al. https://ieeexplore.ieee.org/document/9370308
The other stuff I don’t really care. I have 0 stuff on the desktop and use Super + typing the name of the app to open anything.
I would use a gnome distro if fractional scaling worked decently, but sadly it doesn’t, at least for VSCode and IntelliJ. So WSL it is.
I would use: - temperatures around 15 degrees, so a place that went from lows of 5 in the winter to highs of 25 in the summer - rarely overcast. Growing up in Porto I don’t really have a problem with sunny days or days where it is actually raining. The bane of my existence are the misty, damp, sprinkly, overcast days - no snow
It’s a shame that I have to go to Berlin to get a good start on my career, otherwise I’d love to stay here
This is my first blog post ever. It's about using receivers in inline functions to simplify builder patterns. If you have any suggestions about improvements/general critiques, feel free to comment here, message me or open up an issue on GitHub!
I (as a uni. student, so take it with a grain of salt) am involved in managing several large projects - overseeing 4 teams of around 10 people each. We decided to use Discord as the university did not want to pay Slack workspace licenses and it has been a frustrating experience to say the least.
Comparing to several experiences I have had with similar-sized teams and even a larger, albeit still small-ish, organization, there are many complaints to be had:
- No threads. This one is Discord's Achille's heel when compared to Slack. If you have even two or three simultaneous conversations around the same topic, you either a) are unable to understand what's going on past a certain point or b) need to take the conversation somewhere private, essentially losing one of the main components of the experience.
- No archiving channels. Seriously. I have categories in my Discord servers to archive stuff, and it just means that there is a dump of channels clobbering the interface for day-to-day operation. The Slack model where they are tucked away in a closet is much better.
- Integrations. Discord bots are cool for music but everything productive, from /gcal to Doodle/GitHub/Trello/Google Drive integration is better on Slack.
One thing I think is overrated is the search. Discord's sucks, and while Slack search works reasonably well, I do find it hard to remember relevant information to put in the search prompt. Essentially I think that you still need an external place to store persistent documentation and more durable information, be it VCS issues, wikis (Notion has been a product I started using recently and seems pretty cool), but even there threads help write the docs.
Where Slack falters is not-text. As ludicrous as this sounds, I have seen cases of teams using Slack for written communication and falling into Discord for voice channels and transient chat. I think this can be made better with good integration with some communication suite: Zoom? Google Meet? Anyhow, this is where MS Teams comes and eats their lunch. Worse at everything than everyone else, but at least it does it all.