data subTLDR week 34 year 2026

The developer has created a lightweight language model (LLM) from scratch, achieving impressive results with just 250M parameters and a small 60MB deployment size. The model uses a unique quantized system that enables it to run effectively even on a regular laptop CPU, without requiring a GPU. The LLM employs a long context method, compressing older tokens to 1 bit and storing them on disk, allowing it to retrieve from up to 100M tokens. While not perfect, the model demonstrates promising capabilities in language modeling and generating coherent responses, including retrieving specific information. The developer plans to refine the model for better reasoning capabilities. There is a positive sentiment toward the developer's innovative approach and potential scalability.

The new Parquet file visualization tool, Petquar, is receiving mixed reviews. Some users appreciate the concept and find it a useful addition to data engineering tools, particularly for beginners. Others, however, express concern over the aesthetics and suggest that most could code a similar tool themselves to meet their specific needs. Some users also highlighted alternatives like Jetbrains' Big Data tools and a VSCode extension that also facilitates Parquet viewing and querying. While the tool was generally received positively, there's a clear call for higher quality in freely available software.

The Reddit thread revealed mixed reactions to a machine learning project involving a Shrike Lite microcontroller and a lightweight image generation model. Some comments praised the project's innovative nature, while others offered constructive criticism. The model's limitations were noted, particularly its slow speed and resulting image noise. Users suggested that the entire operations graph could potentially be encoded onto the FPGA, and proposed the use of weight sharing to further optimize performance. Some users found navigating the creator's site difficult and asked for clearer links to the project's case study. The sentiment was generally positive, with users appreciating the project's creativity and technical challenge.

The sentiment within the discussion largely agrees with the notion that basic data discoverability issues should be addressed before implementing complex AI solutions. Participants highlighted the pressure to keep up with the latest trends and technologies, often at the cost of neglecting foundational data management. They also noted organizational resistance to investing in non-tangible improvements like better data management. Some suggested strategies include tying data management improvements to buzzword-driven initiatives (e.g., AI enablement) to gain organizational support. A few acknowledged the difficulty in estimating cost savings from these invisible improvements, likening them to insurance against potential future crises.

The Reddit community suggests that the user's SQL, Postgres, Looker, Snowflake, and dbt skills qualify them for an entry-level data analytics or analytics engineering role, but not necessarily a data engineering position. They recommend focusing on Python, data modelling, ETL pipelines, and metadata-driven frameworks for data engineering. Contributing to open-source projects, showcasing personal projects, and learning about dimensional data modeling were also advised. Some users questioned the value of SQL skills as AI can now rapidly perform the same tasks. The overall sentiment was supportive but emphasized the need for further skill development.

While the original poster sought advice on writing shorter SQL queries, the majority of responses emphasized the value of clear, understandable code over brevity. Top comments endorsed the use of longer queries with detailed comments and sensibly named columns, arguing that this approach ensures supportability by others and reduces confusion for future maintainers. Some commenters even suggested the use of temp tables for clarity, despite not being the shortest or most efficient method. The overall sentiment was that performance and documentation are more important than the length of a query. A minority of commenters asked for specific examples or challenged the assumption that longer queries are inferior.

Most commenters agree that practical application is key to understanding SQL, with many finding their skills solidified during work tasks. A deep understanding of underlying data and how tables relate is vital for mastering joins and writing effective queries. Some suggested resources for learning include used books, free online resources, and specific texts like CJ Date's An Introduction to Database Systems. A few found SQL intuitive from the start, while others noted an initial phase of confusion before things clicked. The overall sentiment suggests that persistence, practice, and real-world application are the most effective ways to master SQL.

The thread centers around a college student seeking career advice from professionals in various fields. Individuals shared their career paths and experiences, with an emphasis on data-related roles. The most upvoted comment offers a detailed roadmap for those interested in data analytics, recommending starting with Excel basics, progressing to a BI tool like Power BI or Tableau, then SQL, and finally Python. The entry barrier into data roles was noted as high due to intense competition, requiring a strong resume and proven skills. Job satisfaction varied, though many expressed contentment in their roles. Some users voiced concerns about the future of data roles due to the rise of AI. Overall, the sentiment was positive, with helpful advice and valuable insights shared.