@mgroves For those who want to practice their SQL skills during the advent, there's this challenge that someone from the Elixir community built (not me) - https://t.co/A4GGXLwdPL
Hey friends. I’m looking for a junior-to-mid backend engineer to join my team (which is just me) at @Veeps. It's a great team (still just me). 100% @elixirlang and LiveView, but backend heavy. DMs are open 🤓
As announced for the last few years, we are removing BinaryFormatter in .NET 9. Have you already stopped using it? If not, why? Is there any feedback that you want to share?
Software engineers need to write.
Marc Andreessen: "Few people know this or act on it"
He shared why in a recent interview with @david_perell (shared below)
What are some other benefits of writing?
"Software engineers can't do anything with 15 minutes in between meetings"
Not true. Yes deep focus work isn't possible but not everything we do requires long focus blocks.
Here are 3 types of work I save for time I have in between meetings:
Software engineering is +90% writing.
I don't mean the code:
- Design docs
- Messaging (e.g. emails, slack, etc)
- Documentation
- Sharing learnings (e.g. internal & external blogs)
- Bug reports
- Code reviews
Most don't realize that we write more for humans than machines.
@EmmaBostian A talk that covers your previous perspective on what an EM was doing, embracing the role, what are the IC skills that made you prepared for the management track and those that you miss not using everyday while being an IC
@sabine_s_ Which is a shame, given they should be covered fairly early on when learning about OCaml. Personally, I liked Michael Clarkson's ebook he made for Cornell University: "OCaml Programming: Correct + Efficient + Beautiful"
https://t.co/pojpCOAHkF
Tomorrow only, if you buy https://t.co/qgKk9gLnn1 Pro (at a 40% discount), you'll get Pro licenses to both https://t.co/LoU6y2OFa3 and https://t.co/He56i6B1wS!
It's a $2,131 value for $720!! Almost 70% off 🤯
But it's tomorrow only so do not miss it!
I'm looking for software engineers to share their stories about career growth on my newsletter (https://t.co/aolweeSTyE) with +23k readers: https://t.co/C79xb4ShZw
Why share your story?
• Reach a large, relevant audience (+23k software engineers) for your career
• Build your brand and professional footprint - online writing & LinkedIn are a kind of resume
• Get better at writing - I will work closely with you on editing until it's as good as possible
• Help other engineers at scale
What makes a good career growth story:
• Actionable Learnings - should leave reader with concrete learnings they can apply
• Quality Writing - concise & engaging
• Unique & Transparent Storytelling - helps with engagement and how helpful the content is for others
If there is someone whose story you've been curious to learn about, tag them in the comments
A really cool idea for REPL:
The 'explain' command that takes a piece of code and describes its every part in a beginner-friendly way.
I don't recall any programming language doing this.
Here's my prototype for OCaml 👇
What do you think?
I have a theory that for niche programming languages having a friendly community is more important than for mainstream languages.
Such niche languages (like OCaml, Haskell, Rust, Clojure, Scala, etc.) have fewer people working on improving the tooling, writing the documentation and reducing the number of paper cuts. Interacting with the community is often the only way to get stuff done.
Therefore, it’s crucial to be welcoming if you want people to stay. There’s not enough job opportunities yet to naturally bring more people to your community.
For example, I had been using Java for 5 years in the past. I don’t even know if the Java community exists! Never had to interact with it, everything can be found online.
@sabine_s_@davesnx@__r17x@barelyreaper@ahrefs Way better than jaming features that might look cool but don’t mesh well with existing designs/features from the lang.
I feel there’s a race nowadays for stuffing more and more in the popular langs.
Making things stable, increasing performance, squashing bugs is >>>