Programming thread

  • 🇵🇦 Nuestro primer dominio localizado está en español en kiwifarms.pa. Our first localized domain is on Spanish on kiwifarms.pa.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Is this how it feels to work in the industry? Someone with little to no knowledge in a subject throws buzzwords at you, you have no idea what they're saying, you try to figure it out, they hit you with the fluoride stare, the conversation ends and you're not sure if they left satisfied or not, and suddenly you're being asked to join a random Teams call.
Usually if your boss is non technical they get scared and go away relatively quickly once you get into details, I havent found any so far that differ much in that regard
 
My friends joked that she was an undercover mossad agent. I am supporting canalCrab's theory. Big gov is afraid of perl coming back due to one autistic student so they're trying to send me into yet another acute psychosis episode!
You joke but autism has become a national security threat in recent years.
 
Ever since I learned how to write the Sieve of Erathosthenes, I’ve wanted to write a recursive version of it. Looks I got close to it.
Código:
(defun count-up (x)
    "function to count up from 2 to x"
    (labels ((inner-count (y z a) ;;local function to help counting up
                          (cond ((> z y) (reverse a))
                              (t
                               (inner-count y (+ 1 z) (cons z a))))))
(inner-count x 2 nil)))
    
;;applicative function to remove non-primes from the list
(defun filter-comps (x y)
    (remove-if #'(lambda(z) (and (>= z (* x x))(zerop (mod z x)))) y))

;;the final recursive function
(defun find-primes (x)
    (labels ((inner-prime (y z)
                          (cond ((null y) z)
                              (t
                               (inner-prime (cdr y) (filter-comps (car y) z))))))
            (let ((nums (count-up x)))
                    (inner-prime nums nums))))
Null please add Lisp to the code block languages. I will give all my life’s savings to the nation of Israel if you do.

On another note, almost done with Common Lisp: A Gentle Introduction to Symbolic Programming and I’ll need another book to get better at Lisp. Any suggestions?
 
Ever since I learned how to write the Sieve of Erathosthenes, I’ve wanted to write a recursive version of it. Looks I got close to it.
I wouldn't mind writing a version for comparison, if it would be wanted. Just let me know.
I’ll need another book to get better at Lisp. Any suggestions?
I enjoyed Let Over Lambda well enough, but it's more of an advanced text. I didn't particularly enjoy Practical Common Lisp, but plenty of other people have, and it's available to read for free on the WWW.

Hell, why not read John McCarthy's original Lisp paper? I've read it, and it's a fun read. It's always good to look at how something started out, I think.
 

Archivos adjuntos

My friends joked that she was an undercover mossad agent. I am supporting canalCrab's theory. Big gov is afraid of perl coming back due to one autistic student so they're trying to send me into yet another acute psychosis episode!
Wait til you start writing Scheme, then you'll have half of Cointelpro on your ass lickety split!
 
https://youtube.com/watch?v=uH0SxYdsjv4
Guess I should start learning more about Protobuf.
The results aren't all that surprising to me. I really like gRPC for micro-services, but it is overkill in a lot regular applications.

I was a little surprised by the REST memory usage though. I wonder if that is an artifact of how the JSON is parsed in whatever language/library they used. If I recall correctly, with gRPC, your parsing logic is compiled so that'd explain it's efficiency.

No surprise regarding graphql, it's basically a hacky solution to the client not knowing what they want.
 
I was a little surprised by the REST memory usage though. I wonder if that is an artifact of how the JSON is parsed in whatever language/library they used.
I thought REST was intended to be used without json for the most part?

To me it seems more that whatever people call rest is just RPC's
 
Última edición:
I was a little surprised by the REST memory usage though. I wonder if that is an artifact of how the JSON is parsed in whatever language/library they used. If I recall correctly, with gRPC, your parsing logic is compiled so that'd explain it's efficiency.
Go & C# both use reflection when it unmarshals/deserialises JSON. So that typically has a performance cost.
No surprise regarding graphql, it's basically a hacky solution to the client not knowing what they want.
I had to deal with a GraphQL API, and I found it a PITA. It's one of those things that feels over and under-engineered at the same time.
 
You joke but autism has become a national security threat in recent years.
Haha has it really? I've removed myself from the news and conspiracy related discussions to focus on school so I've been completely out of the loop. Also; what is Lisp used for and why do you like it (out of curiosity)? I think we have one course here that uses it, but that is not in my degree plan. My peers don't seem to enjoy it much, but what do they know! They just complain about all the parenthesis.
I'm unsure what is popular in the Lisp world so my apologies if you have already read these books, but here's some recommended by that professor: Essentials of Programming Languages & Scheme and the Art of Programming. I read that Scheme and Lisp are in the same family, so I hope those still work.
Wait til you start writing Scheme, then you'll have half of Cointelpro on your ass lickety split!
LOL
My heart belongs to bash! I respect the Scheme community though. I get the feeling we are different sides of the same autistic coin.
 
JSON is a terrible data format
>no streaming in the core spec (the grammar requires you to have the full corpus, you have to wait)
>plain text for some reason, muh human readability
>plain text means every number takes a full byte per character
>parsing and unparsing per boundary
>keys get repeated in large object collections, further bloating it

There are exabytes of this shit being passed around every day, the economic impact of json parsing and unparsing is measurable.
The format fails in almost every meaningful test you could apply to serialization

I IMPLORE you, if you can make a dataset just be CSV, please do so. CSV by contrast is the exact opposite of JSON in terms of several of these line items, and it's really trivial to handle and generate.
You can stream out CSV without even using a library very easily even in C.
 
JSON is a terrible data format
>no streaming in the core spec (the grammar requires you to have the full corpus, you have to wait)
>plain text for some reason, muh human readability
>plain text means every number takes a full byte per character
>parsing and unparsing per boundary
>keys get repeated in large object collections, further bloating it

There are exabytes of this shit being passed around every day, the economic impact of json parsing and unparsing is measurable.
The format fails in almost every meaningful test you could apply to serialization

I IMPLORE you, if you can make a dataset just be CSV, please do so. CSV by contrast is the exact opposite of JSON in terms of several of these line items, and it's really trivial to handle and generate.
You can stream out CSV without even using a library very easily even in C.
Don't forget unspecified semantics for numbers, with major variance between implementations. If you want a fully safe implementation, you basically need to write your own JSON number type.
 
>plain text means every number takes a full byte per character
For a little bit of pushback, this is less relevant to web JSON as these values all compress very nicely and transparent gzip compression is about as stable and ubiquitous in web contexts as anything. It's 2026, we rarely need to worry about byte costs any more. The integer 69 is probably being stored in 64 bits in memory anyhow.
 
Is this how it feels to work in the industry? Someone with little to no knowledge in a subject throws buzzwords at you, you have no idea what they're saying, you try to figure it out, they hit you with the fluoride stare, the conversation ends and you're not sure if they left satisfied or not, and suddenly you're being asked to join a random Teams call.
Yes. When someone calls you a "coding wizard" it is not a metaphor. The people you interact with day-in-day-out believe, with all their hearts and lack of soul, that computer code is actual magic. Lean into it, smile, and collect the checks, because they hate understanding. Challenge this and they'll realize they hate you too.

If you're really lucky the "requirements" (one babbling session over Zoom) won't be filtered through some brownoid or Californian.
 
Atrás
Top Abajo