3,579 karma · joined October 6, 2016
The motiviation and tinkering can be similar to a side project, and results in higher quality work IMO. Obviously there are urgent tasks, but it's an ignored vector in the "weighting system" for choosing work for engineers.
If you wait to assign the task in the next sprint, the excitement for that particular task might be gone.
emotionally charged, bad faith assumptions at the smallest whiff of independent thought.
The main important factor IMO is mentorship of junior talent. (I'm speaking for technical orgs)
Viewing the organization as a living organism where an employee is a "cell", then there are material benefits in the "cellular replication" of talent and rejuvenation of the next generation.
It can definitely be true that RTO is worse for an individual engineer but better for the health of the organization long-term. Both can be true.
In my experience, remote only companies tend to prefer a higher ratio of senior employees for this reason. It's plug-an-play.
Manufacturing was always going to move to where it costs less.
It's bad for a productive american economy but it's a prisoner's dilemma so you can't blame businesses or consumers.
The government is the only party that had the power to do anything. it's 100% an economics problem.
Microsoft seems to be prioritizing "cloud" on all their developer products (rather than just windows). I don't feel disadvantaged by NOT using dotnet on windows.
That didn't bother me so much because i speak spanish and can read french. OCaml is of french origin. `string_of_int` is a bad english translation—should have been `string_from_int`.
I like F# where I can use the `int` or `string` functions:
let myString = "2024"
let myInt = int myString
let myStringAgain = string myIntI'm actually working on a IoT device where one of the main goals was selfhosting audio content for my kids. Uses AI for the user interface. Similar to Alexa but battery powered. Still in private beta (orders are closed right now) but here is the link for anyone curious. https://heycurio.com/
Interesting table here highlighting old programming languages https://en.wikipedia.org/wiki/Relational_operator#Standard_r...
In F#, “<>” is the equivalent of “!=“. Postgres also uses <> for inequality so my queries and f# code have that consistency.
Speaking of LSP, the lsp standard is developed by Microsoft so naturally any dotnet language will have good lsp support.
this forces me to optimize the f# code by thinking in terms of low-memory, mutable data structures when interfacing with external libraries.
My preferred approach would be to map my client to a "topic" and then any number of servers can subscribe to the topic. Completely decoupled, scaling up is much easier.
My second biggest issue is proto file versioning.
I'm using NATS for cross-service comms and its great. just wish it had a low-level serialization mechanism for more efficient transfer like grpc.
I’m sure that won’t be the case next year with this new announcement.
Can you explain this? Why use esp as a peripheral if you already have an ARM chip?
We were considering moving off of esp to something that would make it easier do cpu-bound AI inference on-device or to enable more advanced audio DSP algos.
The product is definitely not super appealing to me yet in the current state.
Like what? I’d like to hear what royalty free Japanese music sounds like.